Remote Annex 2000 Hardware Installation Guide Part No. 166-024-150 August 1996 Rev.
Copyright © 1996 Bay Networks, Inc. All rights reserved. Printed in the USA. August 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 4-port and ISDN support. Added new illustrations. C Removed ISDN information; the Remote Annex 2000 does not support ISDN. Chapter 3: Added notes to boot command; also added information regarding status codes during a boot sequence. C1 Format change.
Revision Level History iv Remote Annex 2000 Hardware Installation Guide
Contents Preface About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Printing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 config. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 console-baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 1-1. The Remote Annex 2000 as a Remote Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Figure 1-2. RA 2000 as a Dial-up Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Figure 1-3. RA 2000 as a Terminal, Printer, and Communications Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Figure 1-4. The Remote Annex 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures x Remote Annex 2000 Hardware Installation Guide
Tables Table 1-1. Front Panel System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-1. Remote Annex 2000 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-1. Recommended Cable Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1. ROM Monitor Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables xii Remote Annex 2000 Hardware Installation Guide
Preface T his guide describes how to install a Remote Annex 2000 on a local area network (LAN). See the Annex Quick Start or the Remote Annex Software Installation Notes that come with your Remote Annex 2000 for a description of the software installation. See the Remote Annex Administrator’s Guide for UNIX for configuration information.
Preface Appendix B Cables and Connectors This appendix describes the wiring for Remote Annex 2000 cables. Appendix C Warranty and Technical Support Information This appendix provides warranty and technical support information. Printing Conventions This manual uses the following printing conventions: Convention: Represents: special type In examples, special type indicates system output. special type Bold special type indicates user input.
Preface Convention: Represents: | In command syntax, this character separates the different options available for a parameter. Notes provide important information. Warnings inform you about conditions that can have adverse effects on processing. Cautions notify you about dangerous conditions. Related Documents Each Remote Annex hardware platform ships with the appropriate hardware guide. The remaining documentation is included with the software.
Preface xvi Remote Annex 2000 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 2000 Hardware Installation Guide
Chapter 1 Introduction T he Remote Annex 2000 is a multi-purpose network server. The Remote Annex is used for: ❑ Remote Network Access. ❑ Dial-up Routing. ❑ Terminal, Printing, and Communications Access. Remote Network Access The Remote Annex 2000 is a multi-protocol, remote access server that provides remote network access to the following networks: ❑ Novell Netware. ❑ TCP/IP. ❑ AppleTalk. Figure 1-1 illustrates the Remote Annex 2000 as a remote access server.
Chapter 1 Introduction Dial-up Routing The Remote Annex 2000 provides dial-up routing support for UNIX and Novell networks. Using a Remote Annex 2000, 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 illustrates the Remote Annex 2000 as a dial-up router.
Chapter 1 Introduction Terminal, Printer, and Communications Access The Remote Annex 2000 provides terminal, printer, and communications access to users on a local area network. Figure 1-3 illustrates the Remote Annex 2000 as a terminal, printer, and communications server. DEC IBM UNIX Corporate LAN Ethernet Remote Annex 2000 Remote Terminal Personal Computer Terminal Plotter Laser Printer Figure 1-3.
Chapter 1 Introduction Remote Annex 2000 Description The Remote Annex 2000 connects from 1 to 16 asynchronous serial devices to host computers on a local area network (LAN). Figure 1-4 illustrates a Remote Annex 2000. STATUS POWER UNIT NET ATTN LOAD ACTIVE 1 2 3 4 5 6 7 8 TEST Figure 1-4. The Remote Annex 2000 The Remote Annex 2000 complies with the Ethernet Revision 2.0 or the IEEE 802.
Chapter 1 Introduction ROM Monitor commands are issued from a console terminal connected to the console port on the Remote Annex 2000’s rear panel. Using the ROM Monitor commands (see Chapter 3), you can: ❑ Modify and display a set of configuration parameters stored in EEPROM memory. ❑ Execute interactive diagnostic tests. ❑ Receive statistics on both the hardware configuration and the network. ❑ Boot the Remote Annex 2000 manually.
Chapter 1 Introduction Watchdog Timer The Remote Annex 2000 has a watchdog timer that its software resets at regular intervals. The watchdog timer reboots the Remote Annex 2000 in the unlikely event of an internal software error. All Remote Annex 2000 support full modem control (five control lines) on all ports. Front Panel The Remote Annex 2000 front panel consists of: ❑ Six system LEDs. ❑ A test LED. ❑ A test button. ❑ Eight status LEDs.
Chapter 1 Introduction Front Panel Components System LEDs There are six system LEDs located on the front panel of the Remote Annex 2000. The LEDs turn on or off to reflect the Remote Annex 2000’s status. Table 1-1 describes the LEDs. Table 1-1. Front Panel System LEDs 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 Introduction Status LEDs The eight status LEDs, numbered one through eight, display serial port activity during normal operations. When the Remote Annex 2000 encounters a problem or an internal error condition, these LEDs display error information. Technical support personnel can use this information to diagnose problems.
Chapter 1 Introduction 8-Port Remote Annex 2000 The Remote Annex 2000 is available with 8 asynchronous ports. Figure 1-7 illustrates the rear panel of an 8-port unit. Plate for 10Base2 or 10BaseT Ethernet (Optional) 1 2 Console (Port 1) 3 4 5 6 RJ45 Port Connectors 7 8 10Base5 Ethernet Connector AC Line Socket Power Switch Figure 1-7.
Chapter 1 Introduction 16-Port Remote Annex 2000 The Remote Annex 2000 is available with 16 asynchronous ports. Figure 1-8 illustrates the rear panel of a 16-port unit. Plate for 10Base2 or 10BaseT Ethernet (Optional) 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 Console (Port 1) RJ45 Port Connectors 10Base5 Ethernet Connector AC Line Socket Power Switch Figure 1-8.
Chapter 1 Introduction Console Port (Port 1) The console port (Port 1) provides access to the ROM Monitor commands when the Remote Annex 2000 is in test mode. RJ45 Port Connectors The RJ45 Port Connectors connect from 1 to 16 asynchronous serial devices to the Remote Annex 2000. Network Interface Connectors The Remote Annex 2000 has the following network interface ports for connecting to a LAN: ❑ 10Base2 Ethernet port with a BNC connector (optional).
Chapter 1 Introduction 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. AC Line Socket The AC Line Socket supplies power to the Remote Annex 2000 through the AC power cord. The AC power cord is plugged into the AC Line Socket.
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: 114,000 hrs. calculated @ 25°C (Mil Std 217). ❑ Rear clearance requirement (for connectors and cables): 6 in. (15 cm).
Chapter 2 Installing the Remote Annex 2000 T his chapter contains a description of how to install your Remote Annex 2000 on your Ethernet network. Installing the Remote Annex 2000 consists of: ❑ Connecting a LAN Using Ethernet. ❑ Connecting a Console Terminal. ❑ Connecting Serial Devices. ❑ Powering Up and Testing the Remote Annex 2000. ❑ Installing the Software and Loading the Operational Image. ❑ Auto-initializing the ROMs. ❑ Self-booting the Remote Annex 2000.
Chapter 2 Installing the Remote Annex 2000 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. ❑ An RJ45 cable (for a SLIP connection). ❑ A PC on the network (Novell boot). Connecting devices to the Remote Annex 2000 requires: ❑ One RJ45 cable for each serial connection.
Chapter 2 Installing the Remote Annex 2000 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 2000 is powered off before disconnecting or connecting the Ethernet cabling. The following subsections contain a description of how to connect your Remote Annex 2000 to: ❑ Thin Ethernet (10Base2). ❑ Thick Ethernet (10Base5). ❑ Twisted Pair (10BaseT).
Chapter 2 Installing the Remote Annex 2000 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 to Thick Ethernet (10Base5) or equivalent transceiver cable, you must have already installed a 10Base5 Ethernet network cable.
Chapter 2 3 Installing the Remote Annex 2000 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 a Twisted Pair (10BaseT) Ethernet cable to the Remote Annex 2000 (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 2000.
Chapter 2 Installing the Remote Annex 2000 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. Figure 2-4. Connecting Twisted Pair Ethernet Cable Do not confuse this connector with the console port RJ-45 connector (Port 1). Connecting a Console Terminal A console terminal is used to access the ROM Monitor and boot the Remote Annex 2000 for the first time.
Chapter 2 1 Installing the Remote Annex 2000 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. Connecting the RJ-45 Cable to the DB-25 Drop Adapter 2 Plug the RJ-45 connector into the console port (Port 1), located on the back panel of the Remote Annex 2000 (Figure 2-6). When the connector clicks into place, the connection is secure.
Chapter 2 Installing the Remote Annex 2000 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. The ROM Monitor assumes that this terminal is CRT-based and displays the backspace (BS) character accordingly. See Chapter 3 for information on invoking the ROM monitor. Connecting Serial Devices The Remote Annex 2000 provides 4, 8, or 16 asynchronous RJ45 serial ports, depending on the device configuration.
Chapter 2 Installing the Remote Annex 2000 Serial port line speed determines the maximum cable length between a device and the Remote Annex 2000: the slower the speed, the greater the distance. Table 2-1 lists recommended cable lengths according to line speed The Remote Annex 2000 can incur damage if the cables are hit by lightning. Table 2-1.
Chapter 2 Installing the Remote Annex 2000 . Figure 2-8. Connecting the Power Cord The Remote Annex 2000 now runs its ROM-resident power-up diagnostics. The LEDs light and then turn off, except for the Power and some status LEDs. 2 Set the Remote Annex 2000 to Test Mode. Pressing the Test button within 3 seconds of powering up puts the Remote Annex 2000 into test mode.
Chapter 2 Installing the Remote Annex 2000 Press the Test button located on the Remote Annex 2000 front panel. The Test LED lights when the unit enters Test Mode (see Figure 2-9). STATUS POWER UNIT NET ATTN LOAD ACTIVE 1 2 3 4 5 6 7 8 TEST Test Button Figure 2-9. Setting the Remote Annex 2000 to Test Mode Next, the Remote Annex 2000 runs diagnostic tests, causing the Active LED to flash; the status LEDs display the test number progression.
Chapter 2 Installing the Remote Annex 2000 3 Verify the Remote Annex 2000’s hardware configuration. At the monitor prompt on the console, type config and press Return .
Chapter 2 Installing the Remote Annex 2000 Installing the Operational Software and Loading the Image Use this section if you have successfully connected the Remote Annex 2000 to your LAN. This section describes: ❑ How to install the Remote Annex 2000’s operational software and image on a device that resides on a network accessible to the Remote Annex 2000. ❑ How to download the operational image from the network device to the Remote Annex 2000.
Chapter 2 Installing the Remote Annex 2000 4 Display or print the README.TXT file for updated information about the current version of Annex Manager for DOS software. 5 Type INSTALL and press Enter . A list of your PC’s available drives appears. 6 Select a network drive that is accessible to all users on the network and press Enter . 7 Enter the name of the directory where you want to copy the files or select the default \PUBLIC directory and press Enter .
Chapter 2 12 Installing the Remote Annex 2000 Choose the server that contains the operational code that will be downloaded to the Annex(es) and select OK. A message appears when the installation is complete. If any errors occur during the process, an error message window appears. 13 Now you can run the Annex Manager, which configures the Annex(es) and security. Refer to the Annex Manager for DOS Administrator’s Guide for the PC for information about Annex Manager.
Chapter 2 Installing the Remote Annex 2000 3 4 If you are booting the Remote Annex 2000 using a Serial Line Internet Protocol (SLIP) network interface, you must: ❑ Use the slip command to modify the port parameters for the SLIP network interface (see slip on page 3-30). ❑ Use the sequence command to list the SLIP network interface in the load/dump interface list (see sequence on page 3-28). Execute the boot command (see boot on page 3-8).
Chapter 2 Installing the Remote Annex 2000 Installing the Operational Software and Image on a VAX VMS Load Host Prerequisites The following should be in place before you install the software and image on your load host. ❑ Your load host must be running VMS 5.5 (or higher). ❑ Your load host must be running DECnet VAX™. ❑ The Ethernet controller must be on the same Ethernet as the Annex. ❑ The CMKRNL and SYSPRIV privileges must be enabled.
Chapter 2 Installing the Remote Annex 2000 3 Enter yes and continue the installation. 4 Enter yes if you have backed up your system disk. 5 Enter the device on which your distribution medium is loaded. 6 Enter * for the products to be processed. 7 Press 8 Enter yes if you have mounted the software medium on the appropriate device. Return to indicate none for installation options.
Chapter 2 Installing the Remote Annex 2000 Configuring NCP for Downloading The operational image now resides in the directory to which the logical MOM$LOAD points. You must now enable downline loading of the image on the appropriate circuit using NCP.
Chapter 2 Installing the Remote Annex 2000 To enable your VAX VMS load host to accept crash dumps: 1 Assign a DECnet node number to your Remote Annex 2000. 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 2.69 NAME BINGO DUMP FILE\ DKA200: [ZETKIN.REMOTEANNEX_CRASH]BINGO.
Chapter 2 Installing the Remote Annex 2000 Auto-initializing the ROMs The Remote Annex 2000 is distributed without an IP address or preferred load host (UNIX/IP, IPX, or MOP) defined in ROM. When the device is booted, the Remote Annex 2000 attempts to autoinitialize its ROMs using BOOTP (bootstrap protocol) and RARP (Reverse Address Resolution Protocol). The Remote Annex 2000 supports the BOOTP and RARP protocols.
Chapter 2 Installing the Remote Annex 2000 BOOTP For a successful BOOTP retrieval, a bootpd must be running on a host on the same network as the Remote Annex 2000 and must have the appropriate information in the bootptab file. The Remote Annex 2000’s BOOTP implementation adheres to rfc951, rfc1048, and rfc1084. A sample bootptab file entry used to initialize the Remote Annex 2000 named terminator looks like this: remoteannexdefault:\ :sm=255.255.255.0:gw=132.245.22.
Chapter 2 Installing the Remote Annex 2000 When the Remote Annex 2000 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 2000 in this case) in whatever format the client requests; the Remote Annex 2000 (client) always requests the decimal dot notation format (e.g., 99.130.83.99).
Chapter 2 Installing the Remote Annex 2000 The host serving the Remote Annex 2000 its boot information must be running on the same network as the Remote Annex 2000 because the Remote Annex 2000 only broadcasts BOOTP and RARP queries. If BOOTP and RARP fail, the Remote Annex 2000 transmits an IPX Advertisement Request for Service and a MOP Multicast boot request.
Chapter 3 ROM Monitor Commands T his chapter describes the ROM Monitor commands. Access these commands through a terminal connected to the console port (Port 1) when the Remote Annex 2000 is in test mode. Pressing the Test button within 3 seconds of powering up puts the Remote Annex 2000 into test mode. To enter test mode when the unit 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/ Abbreviation 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 version. console-baud Changes the console port’s baud rate. Configuring the console port for remote maintenance.
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.
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 2000 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 2000 from a UNIX load host. If you do not define an IP address for the Remote Annex, it will attempt to learn the address using BOOTP or RARP. If you do not define a subnet mask, the Remote Annex 2000 uses the generic mask for the specified IP address.
Chapter 3 ROM Monitor Commands boot The boot command requests the loading of appropriate Remote Annex 2000 operating software from the preferred load 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 2000 begins to boot, it displays the load server host’s IP 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 on page 4-12).
Chapter 3 ROM Monitor Commands The boot command display (using bfs) looks like this: monitor:: boot Enter boot file name[(ip) “oper.56.enet”,\ (mop) “OPER_56_ENET.SYS”]:: Requesting default boot file “OPER_56_ENET.SYS” for MOP/VMS\ loads and “oper.56.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 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.56.
Chapter 3 ROM Monitor Commands Only use the boot -l command when reloading your Flash memory (e.g., when upgrading to a new version of software). Make sure that you have a properly configured load host available or you will 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 Remote Annex 2000’s total number of ports, total amount of memory, the ID number, the serial number, the major and minor hardware revision numbers, and the ROM software revision number. 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 2000 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 2000 ROMs: 1 2 3 From a site local to the Remote Annex 2000: ❑ Set the Remote Annex 2000 into test mode so the monitor prompt appears on the console. ❑ Set the modem into auto-answer mode. From the Remote Annex 2000 console port: ❑ At the monitor prompt, enter console-baud. ❑ At the Select baud rate prompt, enter the appropriate baud rate or enter auto. ❑ Connect the modem to the Remote Annex 2000’s console port.
Chapter 3 ROM Monitor Commands erase The erase command erases the contents of non-volatile memory, including the Remote Annex 2000’s IP address. This command also restores the parameters to their factory defaults. The syntax is: erase If the self-boot option is installed, the erase command prompts for which non-volatile memory to erase: EEPROM or FLASH.
Chapter 3 ROM Monitor Commands help Entering help, or ?, displays brief descriptions of the Remote Annex 2000 ROM Monitor commands.
Chapter 3 ROM Monitor Commands image The image command sets and displays the name of the image file containing the Remote Annex 2000’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.56.enet. The image command display looks like this: monitor:: image Enter Image name: [(ip)"oper.56.enet", \ (mop) "OPER_56_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 2000’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 []:: saturn 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 2000’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 The Ethernet transceiver loopback test sends a short packet from the Remote Annex 2000 through the transceiver to test the network’s integrity.
Chapter 3 ROM Monitor Commands Failing this test indicates that either the Remote Annex 2000, 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 2000 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 loopback plug to test both the data lines and the control lines (the accessory kit provides a loopback plug). Connect this plug to the connector on the back of the Remote Annex 2000 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-64.
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 2000 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 2000 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: sl12,net The Remote Annex 2000 can slip boot over any port except Port 1.
Chapter 3 ROM Monitor Commands slip The slip command defines a serial port as a Serial Line Internet Protocol (SLIP) interface. This command defines a number of port parameters. The command syntax is: slip [–d] [port] The slip 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. After entering the command, you are prompted for each parameter.
Chapter 3 ROM Monitor Commands The slip –d command displays all the current settings. The slip –d command display looks like this: monitor:: slip –d Local endpoint address: 192.9.200.214 Subnet mask: default 255.0.0.0 Remote endpoint address: 192.9.200.0 Remote load/dump host address: 192.9.200.
Chapter 3 ROM Monitor Commands Table 3-2. The slip Command Prompts (continued) 3-32 Prompt Description Enter remote endpoint address Specifies the IP address of the remote end of the SLIP interface. Enter remote load/ dump host address Specifies the IP address of the remote host to which load and dump requests are sent. This address is required only if the remote host is a gateway and not the load host. By default, this is the same as the remote end-point address.
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 his chapter describes power-up and booting, troubleshooting during booting, and the file created from a Remote Annex 2000 dump. System LEDs The Remote Annex 2000’s front panel has six system LEDs, a Test LED, and eight 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 problems that occur.
Chapter 4 Troubleshooting Procedures Power-up and Boot Procedures The Remote Annex 2000 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 button on the front panel within 3 seconds of powering-up or a system reset puts the Remote Annex 2000 into test mode. When the Remote Annex 2000 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 sequences during error-free power-up in normal mode. The following subsections describe these states. Table 4-1.
Chapter 4 Troubleshooting Procedures Activity N2: Testing the Hardware During the power-up sequence, the Remote Annex 2000 runs a series of self-test diagnostics. These tests verify internal hardware functions. The Power LED lights for a few seconds, then Unit and Active LEDs flash during the power-up self-tests. After the self-tests complete, only the Unit and Power LEDs remain on.
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 2000 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).
Chapter 4 Troubleshooting Procedures Test Mode Diagnostics Test Mode Pressing the Test button within 3 seconds of either cycling on power or resetting the unit via the Test button puts the Remote Annex 2000 into test mode. Test Mode Error-free Sequences 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 2000 is in normal mode; pressing the Test button readies it 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 2000 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 an Remote Annex 2000 hardware problem requiring service. The status LEDs flash the specific error number. 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 is either connected to an Ethernet transceiver or has a loopback plug installed.
Chapter 4 Troubleshooting Procedures If the Remote Annex 2000 still is not booted, you must pinpoint the problem. The boot error report can help in this process. The Remote Annex 2000 generates and displays a boot error report only if it has opened the boot file and an error occurs during the boot process. Generally, two problems cause boot failures: the Remote Annex 2000 is not configured properly, or the load server host is not responding.
Chapter 4 Troubleshooting Procedures Boot Error Report If an error occurs, a boot error report is generated only if the Remote Annex 2000 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 2000 sensed a hardware error during message transmission or reception. This error indicates a fault with the Remote Annex 2000, 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 2000 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 2000 is configured to boot from a specified host, but the host would not transmit its Ethernet address to the Remote Annex 2000. Possibly, the Remote Annex 2000 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 2000, obtain the following information using the slip command: ❑ Whether the port is configured as a SLIP interface. ❑ The default IP address for the SLIP network interface. ❑ The default IP address for the remote end of the SLIP connection. ❑ The default IP address for the load/dump host (this must be specified if the remote end is a gateway and not a load host).
Chapter 4 Troubleshooting Procedures Load Server Host Not Responding The Remote Annex 2000 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 2000. ❑ 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 Troubleshooting Procedures In test mode, both the Remote Annex 2000 and erpcd on the load server host display boot progress reports. The Remote Annex 2000 displays its reports on the console; erpcd displays its reports on the UNIX terminal that invokes test mode.
Chapter 4 Troubleshooting Procedures ❑ All Remote Annex 2000 software is installed properly on the host (see the software installation notes that accompany your software release). ❑ The erpcd daemon or tftp server, which loads the Remote Annex 2000’s operational code, is running. 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_56_ENET.SYS is in the directory MOM$LOAD and the file protection allows reading.
Chapter 4 Troubleshooting Procedures Remote Annex 2000 Dumps The Remote Annex 2000 dumps its memory image to a host running load server software when certain software or hardware events occur. Table 4-8 illustrates the state of the front-panel LEDs during a dump. Dump files are generated for use by technical support personnel only. Events that trigger Remote Annex 2000 dumps are: ❑ Non-recoverable hardware or software errors occur. ❑ Software fails to reset the Remote Annex 2000’s watchdog timer.
Chapter 4 Troubleshooting Procedures The Remote Annex 2000 sends a dump file to a preferred load dump host. If you do not define this host by specifying an address, the Remote Annex 2000 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 2000 RAM memory and hardware state. The amount of space required for the dump file varies according to the port configuration. The ROM Monitor config command displays the amount of memory for the Remote Annex 2000. 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 Pin/Signal Allocations T his appendix identifies the signals and the associated pins used by the following Remote Annex 2000 ports: ❑ Serial Port (Port 1 is Console Port). ❑ 10Base2 Ethernet Port. ❑ 10Base5 Ethernet Port. ❑ 10BaseT Ethernet Port. Serial Port Figure A-1 illustrates a serial port receptacle. Table A-1 lists the receptacle’s pin/signal allocations. 1 8 Figure A-1.
Appendix A Port Pin/Signal Allocations Table A-1. Serial Port Pin/Signal Allocations Pin Number Signal 1 RTS 2 DTR 3 TXD 4 DCD 5 RXD 6 GND 7 DSR 8 CTS 10Base2 Ethernet Port Figure A-2 illustrates a 10Base2 BNC Ethernet connector. Coaxial Center Conductor Coaxial Shield Figure A-2.
Appendix A Port Pin/Signal Allocations 10Base5 Ethernet Port Figure A-3 illustrates a 10Base5 Ethernet transceiver port connector. Table A-2 lists the connector’s pin/signal allocations. 8 1 15 9 Figure A-3. 10Base5 Ethernet Port Connector Table A-2.
Appendix A Port Pin/Signal Allocations 10BaseT Ethernet Port Figure A-4 illustrates a 10BaseT RJ45 Ethernet port receptacle. Table A-3 lists the connector’s pin/signal allocations. 1 8 Figure A-4. 10BaseT RJ45 Ethernet Port Receptacle Table A-3.
Appendix B Cables and Connectors T his appendix describes the wiring for the following cables and connectors: ❑ Serial Port Cables. ❑ Loopback Connectors. The Remote Annex 2000 accessory kit includes the loopback connectors; it does not supply the serial port cables. Serial Port Cables The Remote Annex 2000 is a DTE system that conforms to an 8-wire USOC wiring standard.
Appendix B Cables and Connectors Remote Annex 2000 25-way Female DB25 5 RXD 2 TXD 3 TXD 3 RXD 8 CTS 4 RTS 1 RTS 5 CTS 2 DTR 6 DSR 8 DCD 7 DSR 20 DTR 4 DCD 6 GND 7 GND Figure B-1. DTE Crossover Terminal Cable Remote Annex 2000 25-way Male DB25 3 TXD 2 TXD 5 RXD 3 RXD 1 RTS 4 RTS 8 CTS 5 CTS 7 DSR 6 DSR 4 DCD 8 DCD 2 DTR 20 DTR 6 GND 7 GND Figure B-2.
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 LED that confirms the presence of the +12-volt transceiver drive voltage. Table B-1 shows this connector’s pins/signal allocations.
Appendix B Serial Port Loopback Connector Cables and Connectors The 8-pin RJ45 loopback plug loops the following signals: Transmit and Receive; DTR and CTS; and RTS, DCD, and DSR. Table B-3 shows this connector’s pins and signals. Table B-3.
Appendix C T Warranty and Technical Support Information his appendix describes: ❑ Contacting Technical Support. ❑ Customer Assistance Programs. ❑ What to Do if the Remote Annex 2000 Fails. ❑ Remote Annex 2000 Dumps. ❑ Repair Information Request Form. Contacting Technical Support If your Remote Annex 2000 fails, or develops problems, contact your reseller to determine if the problem is hardware- or software-related.
Appendix C Warranty and Technical Support Information You can also contact us via the Internet’s electronic services: ❑ Electronic Mail In Burlington, MA: support@xylogics.com In the UK: int-support@xylint.co.uk ❑ World Wide Web http://www.xylogics.com ❑ Bulletin Board Service (BBS) The BBS telephone number is (617) 273-1499. Use the modem settings: 14400, 8, 1, N. Or, you can ftp files from the BBS at bbs.xylogics.com.
Appendix C Warranty and Technical Support Information What to Do if the Remote Annex 2000 Fails ❑ If the problem is hardware-related, arrange for repair or replacement. ❑ If the Remote Annex 2000 is covered under the original warranty, contact the place of purchase to arrange for repair or replacement. ❑ If the Remote Annex 2000 is covered under a Xylogics Hardware Maintenance Agreement, contact Xylogics Customer Returns at (617) 272-8140, x 307, for a Return Authorization (RA) number.
Appendix C Warranty and Technical Support Information Terms and Conditions of the Warranty WARRANTY: The Seller warrants products of its manufacture to be free from defects in workmanship and material (except in those cases where the materials are supplied by the Buyer) under normal and proper use and service for as long as you own your Remote Annex (not transferable).
Appendix C Warranty and Technical Support Information Warranty does not cover the parts or labor associated with repairs made in the field. THE FOREGOING CONSTITUTES THE SELLER’S SOLE LIABILITY AND THE BUYER’S SOLE REMEDY WITH RESPECT TO PRODUCTS SOLD BY THE SELLER, EXCEPT AS THUS PROVIDED. THE SELLER DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Appendix C Warranty and Technical Support Information Remote Annex 2000 Dumps In the unlikely event that the Remote Annex 2000 generates a dump, you can send the file to Xylogics for evaluation, either by Internet/ ftp or by sending it on tape. To ftp a dump via Internet, use anonymous ftp to xylogics.com and perform the following steps: ❑ Use cd to change to the /annex/incoming directory. ❑ Use mkdir to create a directory, using your site as the directory name.
Appendix C Warranty and Technical Support Information Repair Information Request Form Annex model: _________________________________________________________ Unit’s serial number (located on the bottom of the box): _________________________________________________________ Using either the CLI stats command or the ROM Monitor config command, obtain: Number of ports: _________________________________________________________ Memory size: _________________________________________________________ Software revis
Appendix C Warranty and Technical Support Information Using the ROM Monitor addr command, obtain the following Annex addresses: IP address: _________________________________________________________ Preferred load host: _________________________________________________________ Subnet mask: _________________________________________________________ Broadcast address: _________________________________________________________ Image name: _________________________________________________________ LAN interface:
Appendix C Can the unit currently boot? Warranty and Technical Support Information Y N Load host hardware platform: _________________________________________________________ Load host operating system: _________________________________________________________ Has the unit booted successfully from this load host and operating system? Y N If booting the unit for the first time, did you first run the ROM Monitor erase command? Y N Which front panel system indicators were on at the time of failure? _______
Appendix C Warranty and Technical Support Information Additional information (continued): C-14 Remote Annex 2000 Hardware Installation Guide
Index Numerics 10Base2 Ethernet transceiver port A-2 10Base5 Ethernet transceiver port A-3 A Accepting crash dumps 2-19 addr command 3-5 examples 3-6, 3-7 Assigning a DECnet node number 2-20 Available disk space checking for 2-17 B Bay Networks CompuServe forum xx Customer Service FTP xx home page on World Wide Web xix InfoFACTS service xxi support programs xviii Support Source CD xx Technical Response Center xvii, xxii technical support xvii boot command 3-8 examples 3-12 boot error report 4-12 boot fail
Index Thick 2-4 Thin 2-3 transceiver loopback test 3-22 Twisted Pair 2-5 Ethernet address displaying 3-5 during power-up 2-12 Ethernet connections 2-2 setting addresses 3-5 Internet address setting 3-7 IP encapsulation setting 3-7 ipx -d command 3-19 L Flash boot 2-24 front panel 1-6 description of 1-6 lat_key command 3-20 example 3-20 Link indicator 2-6 load/dump gateway setting 3-7 G M getting help from a Bay Networks Technical Response Center xxii from the Support Source CD xx through CompuServe
Index option_key -d command 3-24 P physical characteristics description of 1-12 ping command 3-25 examples 3-25 port pin/signal allocations A-1 ports command 3-26 power select switch 1-12 power supply 1-12 power switch description of 1-11 power-up applying power 2-9 failures during 2-11 in normal mode 4-2 in test mode 4-7 instructions 2-9 running self-tests 2-11 self-testing procedures during 2-9 sequence 4-2 setting to test mode 2-11 preferred load host setting 3-7 printing conventions xiv R RARP 2-21 r
Index SYSPRIV 2-17 system description of 1-4 System manager account logging onto 2-17 T test Ethernet transceiver loopback 3-22 printer port 3-26 serial line ports 3-26 test mode entering 4-7 entering during power-up 2-11 error indicator states 4-9 error-free indicator states 4-7 error-free power-up sequence 4-7 power-up and booting sequence 4-7 Test switch 1-7 description of 1-7 TFTP 3-10 Thick Ethernet 2-4 Thin Ethernet 2-3 troubleshooting during power-up and booting 4-2 Twisted Pair Ethernet 2-5 U UNI
