Remote Annex 4000 Hardware Installation Guide Part No. 166-024-151 March 1996 Rev.
Copyright © 1996 Bay Networks, Inc. All rights reserved. Printed in the USA. March 1996. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document.
Revision Level History Revision Description A Initial release. B Added new rear panel, ISDN support, new illustrations. C Removed ISDN information; ISDN is not supported in RA 4000. Updated operational image file name (oper.46.enet). Chapter 3: Added information regarding error codes that reflect an Ethernet problem during the boot sequence.
Revision Level History iv Remote Annex 4000 Hardware Installation Guide
Contents Preface About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Printing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Invoking the Console Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32 Chapter 3 ROM Monitor Commands Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 addr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Disassembly Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assembly Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents viii Remote Annex 4000 Hardware Installation Guide
Figures Figure 1-1. The Remote Annex 4000 as a Remote Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Figure 1-2. The Remote Annex 4000 as a Dial-up Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Figure 1-3. Remote Annex 4000 as a Terminal, Printer, and Communications Server. . . . . . . . . . . . . . . . . . 1-3 Figure 1-4. Remote Annex 4000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures x Remote Annex 4000 Hardware Installation Guide
Tables Table 1-1. Remote Annex 4000 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-2. Front Panel System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-1. Remote Annex 4000 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-2. Recommended Cable Lengths . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables xii Remote Annex 4000 Hardware Installation Guide
Preface T his guide describes how to install a Remote Annex 4000 Series on a local area network (LAN). See the software installation notes that come with your Remote Annex 4000 for a description of the software installation. See the Remote Annex Administrator’s Guide for UNIX for configuration information.
Preface Appendix A Port Pins and Signals This appendix details the connectors located on the rear panel of the Remote Annex 4000. Appendix B Cables and Connectors This appendix contains a description of the wiring for Remote Annex 4000 cables. Appendix C Port Upgrade Instructions This appendix contains port upgrade instructions. Appendix D Warranty and Technical Support Information This appendix contains warranty and technical support information.
Preface Convention: Represents: [] In command dialogue, square brackets indicate default values. Pressing Return selects this value. Square brackets appearing in command syntax indicate optional arguments. {} In command syntax, braces indicate that one, and only one, of the enclosed value must be entered. | In command syntax, this character separates the different options available for a parameter. Notes give you important information.
Preface xvi Remote Annex 4000 Hardware Installation Guide
Technical Support and Online Services T o ensure comprehensive network support to our customers and partners worldwide, Bay Networks Customer Service has Technical Response Centers in key locations around the globe: ❑ Billerica, Massachusetts ❑ Santa Clara, California ❑ Sydney, Australia ❑ Tokyo, Japan ❑ Valbonne, France The Technical Response Centers are connected via a redundant Frame Relay Network to a Common Problem Resolution system, enabling them to transmit and share information, and to p
Technical Support and Online Services Customers can also purchase direct support from Bay Networks through a variety of service programs. As part of our PhonePlus™ program, Bay Networks Service sets the industry standard, with 24-hour, 7-days-a-week telephone support available worldwide at no extra cost.
Technical Support and Online Services Bay Networks Information Services Bay Networks Information Services provide up-to-date support information as a first-line resource for network administration, expansion, and maintenance. This information is available from a variety of sources. World Wide Web The Bay Networks Customer Support Web Server offers a diverse library of technical documents, software agents, and other important technical information to Bay Networks customers and partners.
Technical Support and Online Services Customer Service FTP Accessible via URL ftp://support.baynetworks.com (134.177.3.26), this site combines and organizes support files and documentation from across the Bay Networks product suite, including switching products from our Centillion™ and Xylogics® business units. Central management and sponsorship of this FTP site lets you quickly locate information on any of your Bay Networks products.
Technical Support and Online Services The message section is monitored by Bay Networks engineers, who provide assistance wherever possible. Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software. To take advantage of CompuServe’s recently enhanced menu options, the Bay Networks Forum has been re-engineered to allow links to our Web sites and FTP sites.
Technical Support and Online Services How to Get Help Use the following numbers to reach your Bay Networks Technical Response Center: xxii Technical Response Center Telephone Number Fax Number Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France (33) 92-968-968 (33) 92-966-998 Sydney, Australia (612) 9927-8800 (612) 9927-8811 Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173 Remote Annex 4000 Hardware Installation Guide
Chapter 1 Introduction T he Remote Annex 4000 is a multi-purpose network server. The Remote Annex 4000 is used for: ❑ Remote Network Access. ❑ Dial-up Routing. ❑ Terminal, Printer, and Communications Access. Remote Network Access The Remote Annex 4000 is a multi-protocol, remote access server that provides remote network access to the following networks: ❑ Novell Netware. ❑ TCP/IP. ❑ AppleTalk. Figure 1-1 shows how the Remote Annex 4000 is used for remote access.
Chapter 1 Introduction Dial-up Routing The Remote Annex 4000 provides dial-up routing support for UNIX and Novell networks. Using a Remote Annex 4000, network administrators can connect two or more local area networks (LANs) over a wide area network (WAN) using a standard telephone line. Figure 1-2 shows how the Remote Annex 4000 is used for dial-up routing.
Chapter 1 Introduction Terminal, Printer, and Communications Access The Remote Annex 4000 provides terminal, printer, and communications access to users on a local area network. Figure 1-3 shows how the Remote Annex 4000 is used as a terminal and communications server. DEC IBM UNIX Corporate LAN Ethernet Remote Annex 4000 Remote Terminal Personal Computer Terminal Plotter Laser Printer Figure 1-3.
Chapter 1 Introduction Remote Annex 4000 Description The Remote Annex 4000 contains two or three 32-bit processors, a main logic board (MLB), and one or two Serial Line Controllers (SLCs). Figure 1-4 illustrates a Remote Annex 4000. STATUS POWER UNIT NET ATTN LOAD ACTIVE 1 2 3 4 5 6 7 8 TEST Figure 1-4. Remote Annex 4000 Series The Remote Annex 4000 complies with the Ethernet Revision 2.0 or the IEEE 802.
Chapter 1 Memory Introduction The MLB can be configured with 1 to 8 megabytes of on-board memory. One megabyte is permanent with two slots for either 1- or 4-megabyte SIMMs. The Remote Annex 4000 supports a total of 8 megabytes of memory. By default, the Remote Annex 4000 comes with 3 megabytes of memory on the MLB and 1.5 megabytes of memory on the SLC. Flash Memory The MLB supports 2 megabytes of optional flash memory.
Chapter 1 Introduction Asynchronous SLC The Remote Annex 4000 can be purchased with asynchronous SLCs. The SLC types available are: ❑ 18-port SLC ❑ 36-port SLC Figure 1-6 illustrates a 72-port Remote Annex 4000 that contains two 36-port asynchronous SLCs. The Remote Annex 4000 has its dress panel cover removed to expose the connectors. Each PBX connector supports six serial ports. Appendix B describes the Remote Annex 4000’s asynchronous serial device cable (fan-out cable). Figure 1-5.
Chapter 1 Introduction Asynchronous Ports Each asynchronous port has seven active pins, plus ground, to provide the following standard RS232 asynchronous signals for modem and flow control: ❑ Transmit Data (TxD, transmitted). ❑ Receive Data (RxD, received). ❑ Data Terminal Ready (DTR, transmitted). ❑ Clear To Send (CTS, received). ❑ Data Set Ready (DSR, received). ❑ Request to Send (RTS, transmitted). ❑ Carrier Detect (DCD, received).
Chapter 1 Introduction Using the ROM Monitor commands (see Chapter 3), you can: ❑ Modify and display a set of configuration parameters stored in EEPROM. ❑ Execute interactive diagnostic tests. ❑ Receive information and statistics for the hardware configuration and the network. ❑ Boot the Remote Annex 4000 manually. Once the Remote Annex 4000 has obtained a boot image and is booted, the console leaves the ROM monitor and displays the console monitor.
Chapter 1 Introduction Front Panel The Remote Annex 4000’s front panel consists of: ❑ Six system LEDs. ❑ One test LED. ❑ One test button. ❑ Eight status LEDs. Figure 1-6 illustrates the Remote Annex 4000’s front panel. Table 1-2 describes the panel’s system LEDs. STATUS POWER UNIT NET ATTN LOAD ACTIVE 1 2 3 4 5 6 7 8 TEST System LEDs Test LED Test Button Status LEDs Figure 1-6.
Chapter 1 Introduction Front Panel Components System LEDs There are six System LEDs on the front of the Remote Annex 4000. The LEDs turn on or off to describe the Remote Annex 4000’s state. Table 1-2 describes the LEDs. Table 1-2. Front Panel System LEDs Test LED 1-10 LED Definition POWER On when the unit is receiving AC power and the internal DC power supply is working properly. UNIT On after the unit successfully passes its self-test.
Chapter 1 Test Button Introduction The Test Button allows you to change the operational mode of the Remote Annex 4000 from normal to test. It also functions as a Reset button (see following Note). The Remote Annex 4000 automatically powers up in normal mode. To enter test mode, press the Test button within 30 seconds of powering-up or resetting the unit. When the Test LED lights, the Remote Annex 4000 is in test mode. Holding the Test button for longer than three seconds resets the unit.
Chapter 1 Introduction Power Switch Dress Panel Cover Console Port Printer Port Thick Ethernet (10Base5) Twisted Pair Ethernet Fan (10BaseT) Power Select AC Line Socket Thin Ethernet (10Base 2) Diagnostic Jumper Mode Jumper Figure 1-7. Remote Annex 4000 Rear Panel Rear Panel Components Console Port The Remote Annex 4000 has a separate console port with an 8-pin, RJ-45 connector for attaching the console.
Chapter 1 Mode Jumper Introduction The Mode Jumper is used to configure the Remote Annex 4000 properly to ensure compatibility with the operational image. The Mode Jumper setting is checked by the PROMs only at power-up or reset time. The jumper must be installed when running images prior to Release 9.3. When running Release 9.3 or newer images, this jumper should be removed.
Chapter 1 Introduction Power Switch The Power Switch disconnects AC power without disconnecting the Remote Annex 4000 from the power source. Power Select Switch The Power Select Switch selects the operational voltage range. The Remote Annex 2000 automatically selects the operational voltage range. The 110V position allows operation in the 90 to 130 VAC range; the 220V position allows operation in the 180 to 260 VAC range.
Chapter 1 ❑ ❑ Introduction Environment: ❑ Operating temperature: 0° to 50°C. ❑ Non-operating temperature: -25° to 65°C. ❑ Operating humidity: 5% to 95% relative humidity, non-condensing. ❑ Non-operating humidity: 5% to 95% relative humidity, non-condensing. ❑ Operating shock: 10G peak 1/2 sine wave, 11 ms duration. ❑ Operating vibration: random vibration 1.2 *10-3 G2/Hz, 12 to 198 Hz. ❑ Audible noise: A-Weighted Sound Pressure level less than 36 dB @ 1 meter from all 6 surfaces.
Chapter 1 Introduction ❑ MTBF: 68,000 hrs (72 ports), calculated @ 25°C (Mil Std 217). ❑ Rear clearance requirement (for connectors and cables): 6 in. (15 cm).
Chapter 2 Installing the Remote Annex 4000 T his chapter contains a description of how to install your Remote Annex 4000 hardware on your Ethernet network. Installing the Remote Annex 4000 consists of: ❑ Connecting a LAN. ❑ Connecting a Console Terminal. ❑ Connecting Serial Devices. ❑ Connecting a Parallel Printer. ❑ Powering Up and Testing the Remote Annex 4000. ❑ Installing the Software and Loading the Operational Image. ❑ Auto-initializing the ROMs. ❑ Self-booting the Remote Annex 4000.
Chapter 2 Installing the Remote Annex 4000 Connecting the Remote Annex to a LAN requires the following equipment: ❑ The appropriate network cable (e.g., Ethernet transceiver cable) for connecting to a LAN or an Ethernet loopback connector. ❑ The console port cable (supplied with software) and a console terminal. ❑ A PC on the network (Novell boot). Connecting devices to the Remote Annex 4000 requires: ❑ Remote Annex 4000 fan-out cables for asynchronous communications.
Chapter 2 Installing the Remote Annex 4000 Each connection type requires a different connection procedure described in the following sections. Connect only one type of Ethernet cabling at one time. Make sure the Remote Annex 4000 is powered off before disconnecting or connecting the Ethernet cabling. The following subsections contain a description of how to connect your Remote Annex 4000 to: ❑ Thin Ethernet (10Base2). ❑ Thick Ethernet (10Base5). ❑ Twisted Pair (10BaseT).
Chapter 2 Installing the Remote Annex 4000 3 Twist the sleeve on the T-connector clockwise to lock the connection in place. Figure 2-2. Connecting Thin Ethernet Cable Connecting Thick Ethernet (10Base5) Cable To connect Thick Ethernet (10Base5) or equivalent transceiver cable, you must have already installed a 10Base5 Ethernet network cable.
Chapter 2 3 Installing the Remote Annex 4000 Push the slide mechanism to the left to secure the connection. Figure 2-3. Connecting Thick Ethernet Cable Connecting Twisted Pair Ethernet (10BaseT) Cable Follow the steps in this section to connect Twisted Pair (10BaseT) Ethernet cable to the Remote Annex 4000 (see Figure 2-4): 1 Insert the RJ-45 connector located on the Twisted Pair Ethernet cable into the 10BaseT connector on the rear panel of the Remote Annex.
Chapter 2 Installing the Remote Annex 4000 3 Verify that the Link Indicator is green. The green link indicator LED next to the 10BaseT connector goes on when power is applied and an active 10BaseT network segment is plugged in. Do not confuse this connector with the console port RJ-45 connector. Figure 2-4.
Chapter 2 Installing the Remote Annex 4000 Connecting a Console Terminal A console terminal is used to access the ROM Monitor and boot the Remote Annex 4000 for the first time. Follow the steps in this section to connect a console terminal to the console port located on the rear panel of the Remote Annex 4000. 1 Connect the Console Terminal’s I/O connector to the RJ-45 cable (the accessory kit includes a cable) using a Telco RJ wire to a DB-25 DTE drop adapter (see Figure 2-5). Figure 2-5.
Chapter 2 Installing the Remote Annex 4000 2 Plug the RJ-45 connector into the console port located on the back panel of the Remote Annex 4000 (Figure 2-6). When the connector clicks into place, the connection is secure. Appendix A describes the console port’s signal/pin allocation. Figure 2-6. Connecting to a Console Terminal 3 Turn on the Console Terminal and set the terminal to 9600 baud, eight data bits, no parity, one stop bit, and XON/XOFF flow control.
Chapter 2 Installing the Remote Annex 4000 After the Remote Annex 4000 boots, you can invoke a console monitor by pressing Return . At the console monitor prompt, entering help displays the available options. See Chapter 3 for information on the ROM Monitor commands. Connecting Serial Devices The Remote Annex 4000 provides three to twelve 50-pin PBX connectors (depending on the port configuration) for attaching 1 to 72 devices using Remote Annex 4000 asynchronous (fan-out) cables.
Chapter 2 Installing the Remote Annex 4000 2 Loosen the screws that secure the cable retainer and slide the cable retainer back to allow room for the cable (see Figure 2-8). Cable Retainer Figure 2-8. Moving the Cable Retainer to Make Room for the Cable 3 Attach the PBX end of the fan-out cable to the PBX connector (see Figure 2-9). PBX End of Cable Figure 2-9.
Chapter 2 4 Installing the Remote Annex 4000 Tighten the screw on the PBX end of the cable (see Figure 2-10). PBX Screw Figure 2-10. Securing the PBX Cable 5 Slide the cable retainer forward, making sure that the lip of the retainer secures the connector (see Figure 2-11). 6 Tighten the screws that secure the cable retainer. Cable Retainer Screw Figure 2-11.
Chapter 2 Installing the Remote Annex 4000 7 Slide the dress panel cover back to its original position by sliding it toward the front of the Remote Annex 4000 (see Figure 2-12). Dress Panel Cover Figure 2-12. Securing the Dress Panel Cover If the cables are shielded (metal), the cable retainers may obstruct the PBX end, preventing you from securing the dress panel cover. You may need to remove the cable retainers. 8 Connect the Remote Annex 4000 fan-out cables to your serial devices.
Chapter 2 Installing the Remote Annex 4000 Remote Annex 4000 Serial Cables The Remote Annex 4000 asynchronous serial interfaces conform to RS232 specifications. However, it is possible to exceed the specifications’ cable limits given good quality cables that are run in an electrically quiet environment. Xylogics only guarantees operation with the cable lengths recommended below (see Table 2-2). The Remote Annex 4000 can incur damage if the cables are hit by lightning. Table 2-2.
Chapter 2 Installing the Remote Annex 4000 Connecting a Parallel Printer The Remote Annex 4000 supports parallel printer interface cables from Dataproducts and Centronics. Connect the Remote Annex 4000 to your parallel printer as follows: 1 Connect one end of the Dataproducts or Centronics parallel printer cable to the Remote Annex 4000’s 25-pin printer port (see Figure 2-13). Figure 2-13.
Chapter 2 Installing the Remote Annex 4000 Powering Up and Testing the Remote Annex 4000 Power-up and test your Remote Annex 4000 as follows: 1 Verify the Remote Annex 4000’s operational power range. Check that the power select switch is set to the 110V position for operation in the 90 to 130 VAC range, or to the 220V position for operation in the 180 to 260 VAC range (see Figure 2-14). Power Select Switch Figure 2-14.
Chapter 2 Installing the Remote Annex 4000 2 Apply power. Connect the female end of the power cord to the AC line socket. Connect the male end to an active AC line outlet (see Figure 215). Turn the Power switch on. Figure 2-15. Connecting the Power Cord The Remote Annex 4000 now runs its ROM-resident power-up diagnostics. The LEDs light and then turn off, except for the Power and some status LEDs.
Chapter 2 3 Installing the Remote Annex 4000 Set the Remote Annex 4000 to Test Mode. Pressing the Test button within 3 seconds of powering up puts the Remote Annex 4000 into test mode. To enter test mode when the Annex is already running, hold down the Test button until the Power LED blinks rapidly, then release the Test button and press it again within 3 seconds. This second method resets the Remote Annex, so warn users before you do it.
Chapter 2 Installing the Remote Annex 4000 If the Unit, Net, and Attn LEDs do not light within one minute, one of the following failures has occurred: ❑ Remote Annex 4000 hardware failure: Unit and Attn LEDs flash. Contact technical support. ❑ Network or network interface failure: Net and Active LEDs flash; error message displays on the console. If a network or network interface failure occurs, typing q accesses the ROM Monitor prompt. Check the network connection (also, see net on page 3-22).
Chapter 2 5 Installing the Remote Annex 4000 Record the Remote Annex 4000’s Ethernet address for future reference. At the monitor prompt, type addr -d and press display looks like this: Return . The screen monitor:: addr -d Ethernet address (hex): 00-80-2D-00-18-B6 Internet address: Subnet mask: 255.255.0.0 Broadcast address: 0.0.0.0 Preferred Load Host address: Preferred Dump Host address: 0.0.0.0 Load/Dump Gateway address: 0.0.0.
Chapter 2 Installing the Remote Annex 4000 This section contains the following subsections: ❑ Installing to and Loading from a Novell Server. ❑ Installing to and Loading from a UNIX Host. ❑ Installing to and Loading from a VAX VMS Host. Installing to and Loading from a Novell Server This section contains a description of what you need to do to install the Remote Annex 4000’s operational software and image to a Novell Server.
Chapter 2 9 Installing the Remote Annex 4000 Run the Annex Installation Utility. At the prompt, start the Annex Installation Utility by typing: AMINSTAL Enter A window appears with selections for installing or upgrading the software. 10 Select Install and press Enter . The Annex Installation utility automatically lists any uninstalled Annexes in the Uninstalled Annexes window. 11 Use the arrow keys or the mouse to highlight the Annex(es) to be installed and select OK.
Chapter 2 Installing the Remote Annex 4000 Installing to and Loading from a UNIX Host This section contains a description of what you need to do to install the Remote Annex 4000’s operational software and image to a UNIX host (see the Remote Annex Administrator’s Guide for UNIX for additional information). Proceed as follows: 1 Install the image on a UNIX host. The software installation notes describe how to do that. If you have a BOOTP server, boot the Remote Annex 4000.
Chapter 2 Installing the Remote Annex 4000 Installing to and Loading from a VAX VMS Host This section contains a description of what you need to do to install the Remote Annex 4000’s operational software and image on a VAX VMS Load Host. Refer to the Annex Interface for VMS Environments Administrator’s Guide and the Annex Interface for VMS Environments User’s Guide for additional information. This product cannot be installed on an AXP system.
Chapter 2 Installing the Remote Annex 4000 ❑ The load host has at least 4000 blocks of available disk space (on any disk), and up to an additional 17,000 blocks available (depending on the amount of memory installed in the Annex) if dumps are to be supported. In a VMS environment, dumps do not overwrite each other, as VMS allows multiple versions of the same file. Therefore, up to 17,000 blocks of memory must be available for each Remote Annex 4000 dump.
Chapter 2 Installing the Remote Annex 4000 The Remote Annex parameter disabled_modules disables specified software modules and frees memory space for use by the system. The default Remote Annex setting for disabled_modules includes vci which disables the Remote Annex interface for VMS environments along with the following commands: backwards, change, clear, crash, define, disconnect, forward, list, logout, resume, set, and show.
Chapter 2 Installing the Remote Annex 4000 1 To find the appropriate circuit, type the following command: $MCR NCP SHOW KNOWN CIRCUITS The system responds: Known Circuit Volatile Summary as of 25-May-1993 Circuit State Loopback Adjacent Name Routing Node SVA-0 on 2 Go back into NCP and enable that circuit to honor service requests by issuing the following NCP commands: $MCR $MCR $MCR $MCR NCP NCP NCP NCP SET SET DEF SET CIRCUIT CIRCUIT CIRCUIT CIRCUIT SVA-0 SVA-0 SVA-0 SVA-0 STATE OFF SERVICE EN
Chapter 2 Installing the Remote Annex 4000 To enable your VAX VMS load host to accept crash dumps: 1 Assign a DECnet node number to your Remote Annex. You can pick any node number or name as long as it does not conflict with any node or address already defined within NCP. For example: $MCR NCP SET NODE 2.69 NAME BINGO 2 Assign a directory and file to receive the crash dump. For example: $MCR NCP SET NODE BINGO DUMP FILE\ DKA200:[ZETKIN.ANNEX_CRASH]BINGO.
Chapter 2 Installing the Remote Annex 4000 You can rename Remote Annex operational images, but they must remain in MOM$LOAD. If you do change the operational image name from OPER_46_ENET.SYS to some other name, the new file name plus the extension can be no longer than 16 characters total. This is due to a MOP restriction of 16 characters in passing the load file name field.
Chapter 2 Installing the Remote Annex 4000 If all requests fail, the Remote Annex 4000 will return to the ROM monitor (if in Test mode) or continue the auto-initializing procedure indefinately (if in normal mode). BOOTP For a successful BOOTP retrieval, a bootpd must be running on a host on the same network as the Remote Annex 4000 and must have the appropriate information in the bootptab file. The Remote Annex 4000’s BOOTP implementation adheres to rfc951, rfc1048, and rfc1084.
Chapter 2 Installing the Remote Annex 4000 When the Remote Annex 4000 receives a BOOTP response with the sm, gw, and ip set, it sets the respective parameters: subnet_mask, load_dump_gateway, and inet_addr. The Vendor Magic Cookie must be set to auto. This indicates that bootpd should respond to the client (Remote Annex 4000 in this case) with whatever format the client requests; the Remote Annex 4000 (client) always makes requests in the decimal dot notation format (e.g., 99.130.83.99).
Chapter 2 Installing the Remote Annex 4000 If BOOTP and RARP fail, the Remote Annex 2000 transmits an IPX Advertisement Request for Service and a MOP Multicast boot request. If all requests fail, the Remote Annex 4000 returns to the ROM monitor (if in Test mode) or continues the auto-initializing procedure indefinitely (if in normal mode). Self-booting the Remote Annex 4000 If you purchased a Remote Annex 4000 with Flash ROM, your device already contains an operational image.
Chapter 2 Installing the Remote Annex 4000 Invoking the Console Monitor After the image boots, you can invoke a Console Monitor by pressing Return on the console. At the Console Monitor prompt, entering help or ? displays the available options: 2-32 ❑ dump (from the Remote Annex to the host and reboots). ❑ help or ? (displays the available options). ❑ info (displays configuration information for the Remote Annex). ❑ leds (displays the current front panel LED status).
Chapter 2 Installing the Remote Annex 4000 Remote Annex 4000 Hardware Installation Guide 2-33
Chapter 2 2-34 Installing the Remote Annex 4000 Remote Annex 4000 Hardware Installation Guide
Chapter 3 ROM Monitor Commands T his chapter describes the ROM Monitor commands. Access these commands through a terminal connected to the console port when the Remote Annex 4000 is intest mode. Pressing the Test button within 3 seconds of powering up puts the Remote Annex 4000 into test mode. To enter test mode when the Annex is already running, hold down the Test button until the Power LED blinks rapidly, then release the Test button and press it again within 3 seconds.
Chapter 3 ROM Monitor Commands ROM Monitor commands generally provide data about a subset of current configuration (EEPROM) parameters. When appropriate, they also display a prompt that allows the operator to change those parameters. Default or current values for parameters are displayed in brackets. For example: Enter broadcast address [132.245.6.255]: At the prompt, enter a different value, or press displayed value unchanged.
Chapter 3 ROM Monitor Commands Table 3-1. ROM Monitor Commands (continued) Command Description Use boot [-l] [] Erases the existing Flash memory and copies a new image to Flash. Upgrading or replacing the Flash image. config Displays the current hardware configuration and revision levels. Identifying your hardware, memory, and ROM versions. console-baud Changes the console port’s baud rate. Configuring the console port for remote maintenance. erase Erases non-volatile memory.
Chapter 3 ROM Monitor Commands Table 3-1. ROM Monitor Commands (continued) 3-4 Command Description Use mop [-d] Displays and sets EEPROM values relevant to VAX/VMS network addressing, including the MOP load/dump address. Loading software from a DEC VMS host. net Executes an Ethernet transceiver loopback test. Checking your Ethernet connection. option_key [-d] Sets or displays the option key. Checking your option key setting. ping Sends ICMP ECHO_REQUEST datagram to a host or gateway.
Chapter 3 ROM Monitor Commands addr The addr command displays and sets several Remote Annex 2000 operating parameters (EEPROM values) relevant to IP network addressing: ❑ Internet address. ❑ Subnet mask. ❑ Broadcast address. ❑ Preferred Load Host address. ❑ Preferred Dump Host address. ❑ Load/Dump Gateway address. ❑ Type of IP Packet encapsulation. ❑ Load Broadcast The addr -d command displays the unit’s ROM-resident Ethernet address in hexadecimal notation.
Chapter 3 ROM Monitor Commands The addr command display looks like this: monitor:: addr Enter Internet address []:: 192.9.200.214 Internet address: 192.9.200.214 Enter Subnet mask [255.255.0.0]:: Enter Broadcast address [0.0.0.0]:: 192.9.200.0 Broadcast address: 192.9.200.0 Enter Preferred Load Host address []:: 192.9.200.88 Preferred Load Host address: 192.9.200.88 Enter Preferred Dump Host address [0.0.0.0]:: 192.9.200.88 Preferred Dump Host address: 192.9.200.
Chapter 3 ROM Monitor Commands The Remote Annex 4000 must have an Internet (IP) address in its memory before it can load its operational image across the Ethernet via the IP protocol. Therefore, you must enter the IP address before booting the Remote Annex 4000 from a UNIX load host. If you do not define a subnet mask, the Remote Annex 4000 uses the generic mask for the specified IP address. The Remote Annex 4000 tries to boot from a preferred UNIX load host.
Chapter 3 ROM Monitor Commands boot The boot command requests the loading of appropriate Remote Annex 4000 operating software from a cooperating host. The command syntax is: boot [–lv | filename] The boot –l command is supported only if the self-boot option (Flash) is installed. Typing the letter q or Control -C interrupts the boot. If you try to boot with a non-existent image file name, the Annex will hang as it searches for the image. You must press the Reset button to recover.
Chapter 3 ROM Monitor Commands When the Remote Annex 4000 begins to boot, it displays the load server host’s Internet address. If the unit does not boot successfully after several attempts, it displays a boot attempt failed message; if the unit has opened the boot file and an error occurs during the boot process, it displays a boot error report on the console and returns to the ROM Monitor. The boot error report can help determine the cause of the boot failure (see Boot Error Report in Chapter 4).
Chapter 3 ROM Monitor Commands The boot command display (using bfs) looks like this: monitor:: boot Enter boot file name[(ip) “oper.46.enet”,\ (mop) “OPER_46_ENET.SYS”]:: Requesting default boot file “OPER_46_ENET.SYS” for MOP/VM loads and “oper.46.enet” for all other protocols. Unanswered requests shown as ‘?’,transmission errors as ‘* Requesting boot from 192.9.200.88 via Ethernet... Booting BFS file using open delay of 8 Booting BFS file from 192.9.200.88 Header received OK.
Chapter 3 ROM Monitor Commands The boot –l command downloads and saves the operational image to non-volatile memory, erases the existing Flash memory, copies the new image from non-volatile memory to Flash memory, and then executes the image. The boot –l command is supported only if the self-boot option (Flash) is installed. After executing a boot –l, the ls command may not show the newly-loaded image. The boot –l command display looks like this: monitor:: boot –l Enter boot file name [(ip) “oper.46.
Chapter 3 ROM Monitor Commands Use boot –l only when reloading your Flash memory. Typically, you reload your Flash memory when you are upgrading to a new version of software. Make sure that you have a properly configured load host available or you will erase erase your image from Flash and will not be able to load a new one. The boot –v command displays the boot in verbose mode. This output includes the turnaround time in milliseconds for each request.
Chapter 3 ROM Monitor Commands config The config command displays the current configuration information and revision levels. For each serial line controller (SLC), config displays the port configuration as the number of PBX Champ connectors, the range of port numbers for each champ, and the amount of memory on the SLC. The config command display contains information describing whether or not Flash ROM is installed.
Chapter 3 ROM Monitor Commands console-baud The console-baud command changes the console port’s baud rate. Thus, the console port can interface with any modem to which it is connected. When the baud rate is entered as auto, the Remote Annex 4000 detects the baud rate of the incoming line and adjusts its baud rate accordingly. This command provides support for remote troubleshooting.
Chapter 3 ROM Monitor Commands To provide remote access to the Remote Annex 4000 ROMs: 1 2 3 From a site local to the Remote Annex 4000: ❑ Put the Remote Annex in test mode so the monitor prompt appears on the console. ❑ Set the modem to auto-answer mode. From the Remote Annex 4000 console port: ❑ At the monitor prompt, enter console-baud. ❑ At the Select Baud Rate prompt, enter the appropriate baud rate or auto. ❑ Connect the modem to the Remote Annex’s console port.
Chapter 3 ROM Monitor Commands erase The erase command erases the contents of non-volatile memory, including the Remote Annex 4000’s Internet address. This command also restores the parameters to their factory defaults. The command syntax is: erase If the self-boot option is installed, the erase command prompts for the non-volatile memory to erase: EEPROM or FLASH.
Chapter 3 ROM Monitor Commands If the self-boot option is not installed, the command display looks like this: monitor:: erase Erase all non-volatile EEPROM memory? (y/n) [n]:: y Erasing <65504 or 8160 bytes> of non-volatile memory. Please wait... 16K->|Data 0xff ................................................. 16K->|Data 0x0 .................................................
Chapter 3 ROM Monitor Commands image The image command sets and displays the name of the image file containing the Remote Annex 4000’s software. The syntax is: image [–d | filename] The filename argument permits up to 100 characters. To return the image name to its default, enter a pair of double-quote characters (""). The default image name is oper.46.enet. The image command display looks like this: monitor:: image Enter Image name: [(ip)"oper.46.enet", \ (mop) "OPER_46_ENET.
Chapter 3 ROM Monitor Commands ipx The ipx command sets several parameters associated with IPX booting and dumping. This is useful when loading the Remote Annex 4000’s operational image from a Novell file server. The syntax is: ipx [–d] The ipx command display looks like this: monitor:: ipx Enter IPX file server name []:: mars Enter Frame type, 0=802.3 1=Ethernet II 2=802.2 3=SNAP\ [802.
Chapter 3 ROM Monitor Commands lat_key The lat_key command allows you to set the LAT key from the ROM monitor. The lat_key is optional and may be purchased separately.
Chapter 3 ROM Monitor Commands mop The mop command sets the MOP load/dump address. This is useful when the loading the Remote Annex 4000’s operational image from a VAX VMS load host.
Chapter 3 ROM Monitor Commands net The net command executes an Ethernet transceiver loopback test on the local area network. The command syntax is: net The net command display looks like this: monitor:: net Network test – PASSED This transceiver loopback test sends out a short test packet from the Remote Annex 4000 through the transceiver to test the integrity of the network.
Chapter 3 ROM Monitor Commands Failing this test indicates that either the Remote Annex 4000, its transceiver cable, its transceiver, or the Ethernet, is bad. Isolate the failure by using this test and the Ethernet loopback connector. Any of the following conditions can cause these test failures: 1 The Remote Annex 4000 has faulty Ethernet port electronics. To test for this condition, connect the Ethernet loopback connector directly into the network connector. Run the net test again.
Chapter 3 ROM Monitor Commands option_key The option_key command loads an option key from the ROM monitor.
Chapter 3 ROM Monitor Commands ping The ping command sends an Internet Control Message Protocol (ICMP) mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (pings) have an IP and ICMP header, followed by a structured time value and an arbitrary number of pad bytes that fill out the packet.
Chapter 3 ROM Monitor Commands ports The ports command tests serial line ports, exercising both the data lines and the control lines for each serial port specified. The syntax for this command is: ports [–d] Each serial port to be tested must be looped-back with a PBX loopback plug to test both the data lines and the control lines (the accessory kit provides a PBX loopback plug). Attach this plug to the PBX connector on the rear panel of the Remote Annex 4000 that corresponds to the port to be tested.
Chapter 3 ROM Monitor Commands You may enter a list of ports to test, separated by spaces or commas. You may also enter ranges of ports, such as 1-72.
Chapter 3 ROM Monitor Commands Pressing Return after the prompt Selection (Return to exit) returns you to the monitor prompt. If you enter the ports –d command, only the data lines are tested. The outgoing control lines are asserted during this test. monitor:: ports –d Individual Port Tests (Data Lines) Some important notes: - All Serial Ports (1-72) which are to be tested require a loopback plug in order to pass the Data Line loopback tests. WARNING.
Chapter 3 ROM Monitor Commands sequence The sequence command edits the load/dump interface list. This list determines the order of the network interfaces, and either the local area network (LAN) or the SLIP interface the Remote Annex 4000 will use for loading and dumping. The default, net, uses the LAN interface. The list can contain up to four interfaces. If the Remote Annex 4000 fails to boot using the first interface, it will try the next, and then the next interface, and then repeat the sequence.
Chapter 3 ROM Monitor Commands The sequence –d command displays the current load/dump interface list. You cannot specify both the –d argument and the interface list with the same command. The command display looks like this: monitor:: sequence –d Interface sequence: sl2,net Entering a number for a port that has not been properly configured for SLIP causes the Port nn is not configured for SL/IP message to display, where nn is the port number.
Chapter 3 ROM Monitor Commands slip The slip command defines a serial port as a Serial Line Internet Protocol (SLIP) interface. The command automatically sets the number of data bits to 8 for all SLIP interfaces. The number of data bits does not include the start, stop, or parity bits. Table 3-2 lists the information for which the slip command prompts. The syntax is: slip [–d] [port] The slip –d command displays all of the current settings.
Chapter 3 ROM Monitor Commands Table 3-2. The slip Command Prompts 3-32 Prompt Description Allow SLIP on this port Modifies the port’s mode. A y response changes the port to a SLIP interface. An n response changes the port’s mode to CLI. The port is not available as a SLIP interface and the SLIP parameters are ignored. The default is n. Enter local endpoint address Specifies the Remote Annex 4000 Internet address for this SLIP interface.
Chapter 3 ROM Monitor Commands stats The stats command displays current network statistics gathered by the ROM. Use stats along with the boot command to help isolate problems. Table 3-3 describes the network statistics displayed by the stats command.
Chapter 3 ROM Monitor Commands Table 3-3. Network Statistics (continued) 3-34 Statistic Description Bus Wait Drops The number of packets dropped due to waiting too long for a bus to become available. Bad Types/ Lengths The number of unknown packet types if Ethernet IP encapsulation is being used. The number of packets with illegal lengths if IEEE 802.2/802.3 IP encapsulation is being used. Frames Sent The number of frames sent.
Chapter 4 Troubleshooting Procedures T he Remote Annex 4000’s front panel has six system LEDs, a Test LED, and status LEDs. The system LEDs are labeled Power, Unit, Net, Attn, Load, and Active. The status LEDs are numbered one through eight. The system LEDs provide information about normal operations and about problems that occur. Use these LEDs and the ROM Monitor commands to diagnose problems. The status LEDs display port activity during normal operations; each LED supports nine ports.
Chapter 4 Troubleshooting Procedures Power-up and Boot Procedures The Remote Annex 4000 has two modes of operation: normal and test. Normal mode is the standard operational mode. Test mode provides access to the ROM Monitor commands. Pressing the Test switch on the front panel, within 30 seconds of either powering-up or a system reset, puts the Remote Annex 4000 into test mode. When the Remote Annex 4000 is in test mode, the Test button’s LED lights.
Chapter 4 Troubleshooting Procedures Normal Mode Error-free Sequences Table 4-1 summarizes the LED display states during error-free powerup in normal mode. The following subsections describe these states. Table 4-1.
Chapter 4 Troubleshooting Procedures Activity N1: Testing LEDs All front panel LEDs light for a few seconds, then all but the Power LED turn off, confirming that all LEDs are operational. Activity N2: Testing the Hardware During the power-up sequence, the Remote Annex 4000 runs a series of self-test diagnostics. These diagnostics test internal hardware functions. The Power LED lights for a few seconds, then the Unit and Active LEDs flash during the power-up self-tests.
Chapter 4 Troubleshooting Procedures Normal Mode Error Sequences Table 4-2 shows the state of the LEDs when an error occurs at given stages of the start-up process. For example, if the Remote Annex 4000 fails during the testing hardware state (N2), the error condition is hardware failure NE2. A description of possible causes and solutions for each error condition follows Table 4-2. Table 4-2.
Chapter 4 Troubleshooting Procedures Activity NE3: Network Test Failure The Ethernet interface did not pass a simple transceiver loopback test. First, verify that the Ethernet port either is connected to an Ethernet transceiver or has a loopback plug installed. If the test still fails, enter test mode (see net on page 3-22 for more details). Activity NE4: No IP Address or Gateway Some of the boot information required in EEPROM is missing.
Chapter 4 Troubleshooting Procedures Test Mode Diagnostics Test Mode Pressing the Test switch within 3 seconds of either cycling on power or resetting the unit via the Test switch puts the Remote Annex 4000 into test mode. Test Mode Error-free Sequence Table 4-3 summarizes the LED sequences that display in test mode during an error-free start-up. A description of each sequence follows Table 4-3. Table 4-3.
Chapter 4 Troubleshooting Procedures Activity T1: Testing LEDs All front panel LEDs light for a few seconds, then all but the Power LED turn off. This sequence confirms that all LEDs are operational. At this point, the Remote Annex 4000 is in normal mode. Press the Test switch to set the Remote Annex 4000 for the next activity.
Chapter 4 Troubleshooting Procedures Test Mode Error Sequences Table 4-4 describes the state of the LEDs if errors occur at different stages of the start-up process. For example, if the Remote Annex 4000 fails while testing the hardware (state T2), the error condition is hardware failure TE2. A description of each error condition follows Table 4-4. Table 4-4.
Chapter 4 Troubleshooting Procedures Activity TE2: Hardware Failure The ROM diagnostics detected a Remote Annex 4000 hardware problem requiring service. Call technical support. Activity TE3: Network Test Failure The Ethernet interface did not pass a simple transceiver loopback test. First, verify that the Ethernet port either is connected to an Ethernet transceiver or has a loopback plug installed. If the test still fails, type q on the console to access the ROM Monitor prompt.
Chapter 4 Troubleshooting Procedures Boot Failures The procedures for troubleshooting a power-up failure established that: ❑ The hardware is functional. ❑ The Ethernet interface is functional. ❑ The Remote Annex 4000 can communicate with the Ethernet. If the Remote Annex 4000 still is not booted, you must pinpoint the problem. The boot error report can help in this process.
Chapter 4 Troubleshooting Procedures Boot Error Report If an error occurs, a boot error report is generated only if the Remote Annex 4000 has opened the boot file. The report is displayed using the following format: BOOT ERROR REPORT (for BFS files only) Boot attempt from host nn.nn.nn.
Chapter 4 Troubleshooting Procedures Table 4-5. Errors from Last ERPC Layer Invocation Error Description H/W errors The Remote Annex 4000 sensed a hardware error during message transmission or reception. This error indicates a fault with the Remote Annex 4000, the transceiver cable, or the transceiver. Use the net command to isolate the problem (see net on page 3-22). Msgs from wrong host The Remote Annex 4000 received a message from an incorrect host.
Chapter 4 Troubleshooting Procedures Table 4-7. Errors from Last Open Request Error Description ARP errors Address Resolution Protocol (ARP) errors indicate that the Remote Annex 4000 is configured to boot from a specified host, but the host would not transmit its Ethernet address to the Remote Annex 4000. Possibly, the Remote Annex 4000 configuration includes the wrong IP encapsulation. ERPC layer errors See Table 4-5.
Chapter 4 Troubleshooting Procedures Unless otherwise stated, if you are using a SLIP interface to boot the Remote Annex 4000, obtain the following information using the slip command: ❑ Whether the port is configured as a SLIP interface. ❑ The default Internet address for the SLIP network interface. ❑ The default Internet address for the remote end of the SLIP connection.
Chapter 4 Troubleshooting Procedures Load Server Host Not Responding The Remote Annex 4000 can boot from one of six types of hosts acting as a load server host: ❑ Novell Server. ❑ A UNIX host on the local area network. ❑ A UNIX host at the end of a SLIP interface. ❑ Another Remote Annex 4000. ❑ A VAX VMS load server host. ❑ Any host (UNIX or non-UNIX) using tftp. The following subsections discuss troubleshooting for some of these load server hosts.
Chapter 4 1 Troubleshooting Procedures To place erpcd on the load server host into test mode, kill the erpcd program (requires superuser privileges) and restart it using the –D option: # /etc/erpcd –D5 2 To place the Remote Annex 4000 into test mode, hold down the Test button until the Power LED blinks rapidly, then release the Test button and press it again within 3 seconds. (This resets the Annex, so warn users before you do it.
Chapter 4 Troubleshooting Procedures A PC host running the UNIX operating system has both the erpcd and slipd daemons (provided with the distribution and installed in /etc) running in the background on the PC.
Chapter 4 Troubleshooting Procedures VAX VMS Load Host on the LAN If the installation was successful and the NCP CIRCUIT SERVICE is enabled, but the Remote Annex still fails to boot, performing the following steps may locate your problem: 1 Make sure that the file OPER_46_ENET.SYS is in the directory MOM$LOAD and the file protection allows reading.
Chapter 4 Troubleshooting Procedures Remote Annex 4000 Dumps The Remote Annex 4000 dumps its memory image to a host running load server software when certain software or hardware events occur. Table 4-8 shows the LED states during a dump. Dump files are generated for use by technical support personnel only. Events that trigger Remote Annex 4000 dumps are: ❑ Non-recoverable hardware or software errors. ❑ Software fails to reset the Remote Annex 4000’s watchdog timer.
Chapter 4 Troubleshooting Procedures The Remote Annex 4000 sends a dump file to a preferred load dump host. If you do not define this host by specifying an address, the Remote Annex 4000 broadcasts a request and dumps to the first host that responds. The Remote Annex sends a dump to the /usr/spool/erpcd/bfs directory on the dump host. The /usr/spool/erpcd/bfs directory is a default pathname and can be changed.
Chapter 4 Troubleshooting Procedures Each dump file contains a complete image of the Remote Annex 4000 RAM memory and hardware state. The amount of space required for a dump file varies according to the port configuration. The ROM Monitor config command displays the amount of memory for the Remote Annex 4000. Table 4-9 shows sample dump file names. All pathnames are relative to the file /usr/spool/erpcd/bfs. Table 4-9.
Appendix A Port Pins and Signals T his appendix identifies the signals and the associated pins used by the following Remote Annex 4000 ports: ❑ Console Port. ❑ 10Base2 Ethernet Port. ❑ 10Base5 Ethernet Port. ❑ 10BaseT Ethernet Port. ❑ Serial Port. ❑ Parallel Printer Port. Console Port Figure A-1 illustrates the RJ45 console port. Table A-1 lists the RJ45 console port pin/signal allocations. 1 8 Figure A-1.
Appendix A Port Pins and Signals Table A-1. RJ45 Console Port Pin/Signal Allocations Pin Number Signal 1 Reserved 2 DTR 3 TXD 4 DCD 5 RXD 6 GND 7 Reserved 8 Reserved 10Base2 Ethernet Port Figure A-2 illustrates a 10Base2 BNC Ethernet port. Coaxial Center Conductor Coaxial Shield Figure A-2.
Appendix A Port Pins and Signals 10Base5 Ethernet Port Figure A-3 illustrates a 10Base5 Ethernet transceiver port. Table A-2 lists the connector’s pin/signal allocations. 8 1 15 9 Figure A-3. 10Base5 Ethernet Port Table A-2.
Appendix A Port Pins and Signals 10BaseT Ethernet Port Figure A-4 illustrates a 10BaseT RJ45 Ethernet port receptacle. Table A-3 lists the receptacle’s pin/signal allocations. 1 8 Figure A-4. 10BaseT RJ45 Ethernet Port Table A-3.
Appendix A Port Pins and Signals Serial Port Figure A-5 illustrates a serial port connector. Table A-4 lists the connector’s pin/signal allocations. 50 25 26 1 Figure A-5.
Appendix A Port Pins and Signals Table A-4.
Appendix A Port Pins and Signals Parallel Printer Port Figure A-6 illustrates a parallel printer port. Table A-5 lists the port’s pin/signal allocations. The Remote Annex 4000 does not use a standard Dataproducts interface. 13 1 25 14 Figure A-6.
Appendix A Port Pins and Signals Table A-5. Parallel Printer Port Pin/Signal Allocations A-8 Pin Centronics Signal Dataproducts Signal 1 Data Strobe (low true) Data Strobe (high true) 2 Data 1 Data 1 3 Data 2 Data 2 4 Data 3 Data 3 5 Data 4 Data 4 6 Data 5 Data 5 7 Data 6 Data 6 8 Data 7 Data 7 9 Data 8 Data 8 10 Acknlg (low true) NC 11 Busy Demand 12 PE VFU Verify 13 SLCT On-line 14 NC Paper Inst.
Appendix B Cables and Connectors T his appendix describes the wiring for the following cables and connectors: ❑ Serial Port Cables. ❑ Printer Cables. ❑ Loopback Connectors. The accessory kit includes the loopback connectors; it does not supply the serial port and printer cables. Serial Port Cables The Remote Annex 4000 is a DTE system that conforms to a 6-channel, 8-wire USOC wiring standard. Fan-out Cable The 50-pin PBX Champ connector (male 90o) fans out to six individual ports.
Appendix B Cables and Connectors This cable can be purchased as a shielded or unshielded cable. Shielded Cables ❑ Shielded cables are required to conform to VDE-B EMI limits. Shielded cables convert 6-port Remote Annex 4000 Champs to six DB25 RS232 connectors. The connectors can be male or female and are available from Xylogics. Unshielded Cable ❑ Unshielded cables are available as off-the-shelf parts through a distributor. These cables convert the 50-pin PBX Champ connector to six RJ45 plugs.
Appendix B Cables and Connectors Table B-1.
Appendix B Cables and Connectors Table B-1.
Appendix B Cables and Connectors Wiring for the PBX to DB25 Modem Cable Connections Table B-2 shows the wiring for the PBX to male DB25 modem (DCE) connectors. Table B-2.
Appendix B Cables and Connectors Table B-2.
Appendix B Cables and Connectors Serial Cable Wiring Diagrams Figure B-2, Figure B-3, and Figure B-4 illustrate the pin numbers and signal directions for the standard Remote Annex 4000 fan-out and console cable’s 25-way connectors. Remote Annex 4000 25-way Female DB25 RXD TXD TXD RXD CTS RTS RTS CTS DTR DSR DCD DSR DTR DCD GND GND Figure B-2.
Appendix B Cables and Connectors Remote Annex 4000 25-way Male DB25 TXD TXD RXD RXD RTS RTS CTS CTS DSR DSR DCD DCD DTR DTR GND GND Figure B-3. DCE Straight-Through Modem Cable Remote Annex 4000 25-way Male DB25 DSR DTR DCD TXD RXD DCD DTR RXD TXD GND GND RTS CTS Figure B-4.
Appendix B Cables and Connectors Printer Cables Centronics Printer Cable The Remote Annex 4000 uses a standard Centronics interface. Table B-3 shows the cable connections. Table B-3.
Appendix B Cables and Connectors Dataproducts Printer Cable The Remote Annex 4000 does not use a standard Dataproducts interface. Table B-4 shows this custom cable’s connections. Table B-4.
Appendix B Cables and Connectors Loopback Connectors 10Base2 Ethernet Loopback Connector The 10Base2 loopback connector is a 22-Ohm BNC terminator plug. The connector comprises a 22-Ohm resistor connected between the BNC plug’s center coaxial line and shield. 10Base5 Ethernet Loopback Connector The 15-pin male Ethernet 10Base5 loopback connector is equipped with an LEDthat confirms the presence of the +12-volt transceiver drive voltage. Table B-5 shows this connector’s pin/signal allocations.
Appendix B Cables and Connectors PBX Loopback Connector The 50-pin male (90°) PBX loopback connector loops the following signals: Transmit and Receive; RTS and CTS; and DTR, DCD, and DSR. Table B-7 shows the PBX loopback connector’s pin/signal allocations. Table B-7.
Appendix C Port Upgrade Instructions T he Remote Annex 4000 port upgrade kit allows you to upgrade the number of ports by adding or swapping a Serial Line Controller (SLC). These installation instructions provide the following: ❑ Contents of the Kit. ❑ Disassembly Instructions. ❑ Installation Instructions. ❑ Assembly Instructions. ❑ Power-up and Test. Contents of the Kit The Remote Annex 4000 port upgrade kit contains: ❑ One serial line controller.
Appendix C Port Upgrade Instructions Disassembly Instructions Static electricity can damage contents; open only at a static-free station. The following instructions describe disassembling the Remote Annex 4000; these instructions assume that you are facing the unit’s rear panel. Figure C-1 illustrates the instructions. These instructions assume that the Remote Annex 4000 has only one SLC and that you are adding a second SLC for the port upgrade. 1 Unplug the unit. 2 Disconnect all the cables.
Appendix C 4 Port Upgrade Instructions Remove the ten pan-head Phillips screws and two cable retainers (see Figure C-2). Screws (10 Places) Figure C-2. Removing the Screws from the Cover 5 Lift the cover vertically (see Figure C-3). Figure C-3.
Appendix C Port Upgrade Instructions 6 Remove the four pan-head Phillips screws and the dummy plate (see Figure C-4). Screws (4 Places) Dummy Plate Figure C-4. Removing the Dummy Plate Installation Instructions The following instructions describe how to install an additional asynchronous SLC. Observe handling precautions: electrostatic-sensitive devices. 1 Lower the SLC onto the MLB; keep the SLC horizontal (see Figure C-5). Align the SLC with the MLB to avoid bending the pins during installation.
Appendix C Port Upgrade Instructions SLC SLC Connectors SLC MLB Figure C-5. Lowering the SLC onto the MLB 2 Carefully press the SLC connectors into place. Make sure the connectors are seated properly (see Figure C-6). SLC SLC Connectors SLC MLB Figure C-6.
Appendix C Port Upgrade Instructions 3 Secure the SLC to the rear panel using two pan-head Phillips screws (see Figure C-7). Screws (2 Places) Figure C-7. Securing the SLC to the Rear Panel 4 Secure the SLC to the MLB using four pan-head Phillips screws and two flat washers (see Figure C-8). High voltage: do not open or remove the power supply shield. The power supply is not userserviceable. Screws (4 Places) Figure C-8.
Appendix C Port Upgrade Instructions Assembly Instructions The following instructions describe reassembling the Remote Annex. 1 Lower the Remote Annex 4000’s cover onto the unit (see Figure C-9). Figure C-9.
Appendix C Port Upgrade Instructions 2 Secure the cover and cable retainers using ten screws (see Figure C-10). Do not over-tighten these screws (beyond 10 inlbs. of torque). Figure C-10. Securing the Cover Power-up and Test The following instructions describe the power-up and test sequence. 1 C-8 Reconnect all the cables, including: ❑ The transceiver cable. ❑ Existing cables for the serial devices. ❑ The parallel printer cable. ❑ The console terminal cable. ❑ The power cord.
Appendix C 2 Port Upgrade Instructions Set the Remote Annex 4000 to test mode by pressing the Test switch on the front panel (see Figure C-11). The Test LED should light. To access test mode, press the Test switch within 3 seconds of either powering-up or resetting the unit via the Test switch. STATUS POWER UNIT NET ATTN LOAD ACTIVE 1 2 3 4 5 6 7 8 TEST Test Button Figure C-11.
Appendix C Port Upgrade Instructions 4 Attach a PBX loopback plug to the PBX connectors for the new ports (see Figure C-12). The accessory kit provides PBX loopback plugs. PBX Loopback Plug Figure C-12. Attaching a PBX Loopback Plug to the PBX Connectors 5 Issue the ports command and enter the number of ports to be tested as a range at the prompt requesting the port list.
Index Numerics 10Base5 Ethernet Transceiver Port Connector A-3 broadcast address setting 3-7 A C AC line socket 1-14 Accepting crash dumps 2-26 addr command 3-5 examples 3-6 addr -d command 3-5 Assigning a DECnet node number 2-27 asynchronous ports 1-7 autosense Ethernet connector 1-4 Available disk space, checking for 2-24 Cables maximum lengths 2-13 Centronics printer cable wiring B-9 CMKRNL 2-23 communications access review 1-3 CompuServe Bay Networks forum on xx config command 3-3, 3-13 example 3-1
Index E I EMI requirements 1-15 environmental requirements 1-15 erase command 3-3, 3-16 Ethernet 10Base2 A-2 10Base2 BNC Connector A-2 10Base2 connector 1-13 10Base2 loopback connector wiring B-11 10Base5 A-3 10Base5 connector 1-13, A-3 10Base5 loopback connector wiring B-11 10Base5 port pin/signal allocation A-3 10BaseT 2-5, A-4 10BaseT connector 1-13 10BaseT loopback connector wiring B-11 10BaseT port pin/signal allocations A-4 10BaseT RJ45 connector A-4 Thick 2-4, A-3 Thin 2-3, A-2 transceiver loopbac
Index network connecting to Remote Annex 2-2 Network Interface Connectors 1-13 network interface connectors description of 1-13 normal mode error-free sequence 4-3 power-up and booting sequence 4-2 power-up error states 4-5 Novell boot 2-20 O OPER_46_ENET.
Index description of 1-5 serial line controller asynchronous 1-6 18-port 1-6 36-port 1-6 types 1-5 Serial Line Controllers 1-5 serial port A-5 cable wiring B-1 cable wiring diagrams B-7 setting boot sequence 3-29 broadcast address 3-7 Internet address 3-7 IP encapsulation 3-7 load/dump gateway address 3-7 preferred load host address 3-7 SLIP parameters 3-31 subnet mask 3-7 shielded cable source B-2 wiring B-2 size 1-14 SLC 1-4 SLC types 1-5 SLIP parameters 3-32 slip command 3-4, 3-31 example 3-31 software
