Page 1 Remote Annex 2000 Hardware Installation Guide Part No. 166-024-150 Rev. C1 August 1996...
Page 2 The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.
Page 3 Revision Description Initial release. Added 4-port and ISDN support. Added new illustrations. 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.
Page 4 Revision Level History Remote Annex 2000 Hardware Installation Guide...
Page 5: Table Of Contents
Powering-up and Testing the Remote Annex 2000 ........
Page 6 Correcting Remote Annex 2000 Parameters ........
Page 7 Figure 2-6. Connecting a Console Terminal ........... 2-7 Figure 2-7. Connecting the Serial Port Cable to the Remote Annex 2000......2-8 Figure 2-8.
Page 8 Figures Remote Annex 2000 Hardware Installation Guide...
Page 9 Table 2-1. Remote Annex 2000 Conﬁguration Options ........
Page 10 Tables Remote Annex 2000 Hardware Installation Guide...
Page 11: Preface
Preface 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.
Page 12: Printing Conventions
In command dialogue, square brackets indicate default values. Pressing selects this Return 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. Remote Annex 2000 Hardware Installation Guide...
Page 13: Related Documents
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. Remote Annex 2000 Hardware Installation Guide...
Page 14 Preface Remote Annex 2000 Hardware Installation Guide...
Page 15: Bay Networks Customer Service
Web, CompuServe, Support Source CD, Customer Support FTP, and InfoFACTS document fax service. Bay Networks Customer Service If you purchased your Bay Networks product from a distributor or authorized reseller, contact that distributor’s or reseller’s technical support staff for assistance with installation, conﬁguration, troubleshooting, or integration issues.
Page 16 -- within approximately 4 hours. To purchase any of the Bay Networks support programs, or if you have questions on program features, use the following numbers: Region...
Page 17: Bay Networks Information Services
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.
Page 18: Customer Service Ftp
® Central management and sponsorship of this FTP site lets you quickly locate information on any of your Bay Networks products. Support Source CD This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine.
Page 19: Infofacts
This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. The system responds to a fax from the caller or to a third party within minutes of being accessed.
Page 20: How To Get Help
Technical Support and Online Services How to Get Help Use the following numbers to reach your Bay Networks Technical Response Center: Technical Response Telephone Number Fax Number Center Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France...
Page 21: Chapter 1 Introduction
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.
Page 22: Dial-Up Routing
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.
Page 23: Terminal, Printer, And Communications Access
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. UNIX Corporate LAN Ethernet...
Page 24: Remote Annex 2000 Description
10Base5 (Thick), or 10BaseT (twisted pair) as the physical medium. Memory The Remote Annex 2000 is a powerful 32-bit device that comes with an Intel 80486 SXLC2 clock-doubled processor. The Remote Annex 2000 read-only memory (ROM) contains ﬁrmware for performing power-up self-tests and loading operational code.
Page 25 Boot the Remote Annex 2000 manually. Once the Remote Annex 2000 has obtained a boot image and is booted, the console leaves the ROM monitor and displays the console monitor. Refer to the Remote Annex Administrator’s Guide for UNIX for information on the console monitor.
Page 26: Front Panel
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 (ﬁve control lines) on all ports.
Page 27: Front Panel Components
Flashing when the unit is transmitting data to, and receiving Active data from, the network; ﬂashing during diagnostics. Test LED The Test LED lights when the Remote Annex 2000 is in test mode. Test Button button allows you to change the operational mode of the Test Remote Annex 2000 from Normal to Test.
Page 28: Rear Panels
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.
Page 29: 8-Port Remote Annex 2000
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) Console RJ45 Port 10Base5 AC Line...
Page 30: 16-Port Remote Annex 2000
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) Console RJ45 Port 10Base5 AC Line...
Page 31 The RJ45 Port Connectors connect from 1 to 16 asynchronous serial Connectors devices to the Remote Annex 2000. Network Interface The Remote Annex 2000 has the following network interface ports for Connectors connecting to a LAN: 10Base2 Ethernet port with a BNC connector (optional).
Page 32: Physical Characteristics
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.
Page 33 UL1950, CSA C22.2 No. 950, and EN60950. Meets EMI requirements of FCC Class A and EN55022 Class A with shielded and unshielded cables. Meets EMI requirements of EN55022 Class B with shielded cables. Meets EMC requirements of EN50082-1. Remote Annex 2000 Hardware Installation Guide 1-13...
Page 34 Chapter 1 Introduction MTBF: 114,000 hrs. calculated @ 25°C (Mil Std 217). Rear clearance requirement (for connectors and cables): 6 in. (15 cm). 1-14 Remote Annex 2000 Hardware Installation Guide...
Page 35: Chapter 2 Installing The Remote Annex 2000
Installing the Software and Loading the Operational Image. Auto-initializing the ROMs. Self-booting the Remote Annex 2000. Before you Begin The Remote Annex 2000’s software and operational image can be installed on four different devices. Table 2-1 outlines the different conﬁgurations the Remote Annex 2000 supports.
Page 36: Connecting A Lan Using Ethernet
Connecting devices to the Remote Annex 2000 requires: One RJ45 cable for each serial connection. Connecting a LAN Using Ethernet The Remote Annex 2000 supports three types of Ethernet connections: Thin Ethernet, Thick Ethernet, or Twisted Pair (see Figure 2-1).
Page 37: Connecting Thin Ethernet (10Base2) Cable
Verify that both sides of the T-connector are connected to the Thin Ethernet cable. If the Remote Annex 2000 is the last device on the Thin Ethernet cable, make sure that one side of the T-connector is connected to the cable and the other side is connected to a network terminator.
Page 38: Connecting Thick Ethernet (10Base5) 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. Follow these steps to connect the Remote Annex 2000 to a Thick Ethernet cable (see Figure...
Page 39: Connecting Twisted Pair Ethernet (10Baset) Cable
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): 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.
Page 40: Connecting A Console Terminal
Connecting a Console Terminal A console terminal is used to access the ROM Monitor and boot the Remote Annex 2000 for the ﬁrst time. Follow the steps in this section to connect a console terminal to the console port (Port 1) located on the rear panel of the Remote Annex 2000.
Page 41: Figure 2-5. Connecting The Rj-45 Cable To The Db-25 Drop Adapter
2-5). Figure 2-5. Connecting the RJ-45 Cable to the DB-25 Drop Adapter 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.
Page 42: Connecting Serial Devices
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. To attach the serial port cables: Insert the RJ45 end of the cable into one of the serial ports located on the Remote Annex 2000’s rear panel (see...
Page 43: Powering-Up And Testing The Remote Annex 2000
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...
Page 44: Figure 2-8. Connecting The Power Cord
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. Set the Remote Annex 2000 to Test Mode.
Page 45: Figure 2-9. Setting The Remote Annex 2000 To Test Mode
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. If the diagnostics complete successfully, the Unit, Net, and Attn LEDs light, and the ROM Monitor prompt appears on the console terminal (attached to Port 1).
Page 46 EEPROM Size: 32736 Installed Alternate Interface: ThinNet ASYNC Config Number of Ports: 16 Max Port Speed: 115.2 Kbps Record the Remote Annex 2000’s Ethernet address for future reference. At the monitor prompt type addr –d and press . The screen Return...
Page 47: Installing The Operational Software And Loading The Image
Installing to and Loading from a Novell Server This section contains a description of what you need to do to install the Remote Annex 2000’s operational software and image on a Novell Server. Proceed as follows: Log into your Novell server as SUPERVISOR or equivalent.
Page 48 Manager for DOS Administrator’s Guide for the PC for a list and description of the Administrator’s ﬁles. Power up or reset the Remote Annex 2000. Do not enter test mode. Run the Annex Installation Utility. At the prompt, start the Annex...
Page 49: Installing To And Loading From A Unix Host
Administrator’s Guide for the PC for information about Annex Manager. If a Remote Annex 2000 boots from a Novell server, the Remote Annex is available for IPX dial-in and dial-out only. Other Remote Annex 2000 features such as PPP, SLIP, ARAP, and CLI are not supported.
Page 50: Installing To And Loading From A Vax Vms Load Host
Chapter 2 Installing the Remote Annex 2000 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).
Page 51 To stop the installation at any time, press -Y (^Y). CTRL Log into the system manager account. Enter @SYS$UPDATE:VMSINSTAL to start VMINSTAL. VMINSTAL lists any active processes and asks if you want to continue. Remote Annex 2000 Hardware Installation Guide 2-17...
Page 52 Booting the Remote Annex 2000 from a VAX VMS load host automatically enables vci. The following message appears in the syslog ﬁle: MOP Booting, vci enabled. On subsequent boots (regardless of the type of load host;...
Page 53 Remote Annex’s Ethernet address before you can execute these commands. The show server command displays the Remote Annex’s Ethernet address. See the Annex Interface for VMS Environments Administrator’s Guide for more information about this command. Remote Annex 2000 Hardware Installation Guide 2-19...
Page 54 Installing the Remote Annex 2000 To enable your VAX VMS load host to accept crash dumps: Assign a DECnet node number to your Remote Annex 2000. You can pick any node number or name as long as it does not conﬂict with any node or address already deﬁned within NCP .
Page 55: Auto-Initializing The Roms
Under this condition, the Remote Annex 2000 ﬁrst tries to get boot information via BOOTP or RARP. If BOOTP and RARP fail, the Remote Annex 2000 attempts to load an image by transmitting an IPX advertisement request for service and a MOP multicast boot request.
Page 56: Bootp
For a successful retrieval, a bootpd must be running on a host BOOTP on the same network as the Remote Annex 2000 and must have the appropriate information in the bootptab file. The Remote Annex 2000’s implementation adheres to rfc951, rfc1048, and rfc1084.
Page 57: Rarp
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).
Page 58: Self-Booting The Remote Annex 2000
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 2000 returns to the ROM monitor (if in Test mode) or continues the auto-initializing procedure indeﬁnately (if in normal mode).
Page 59: Chapter 3 Rom Monitor Commands
Remote Annex 2000 is in test mode. Pressing the button within 3 seconds of powering up Test puts the Remote Annex 2000 into test mode. To enter test mode when the unit is already running, hold down the button Test...
Page 60: Command Descriptions
IP network parameters. addressing, including the unit’s IP address. boot [-v] [<ﬁle>] Manually boots and Changing the address of loads the unit’s the boot image. operating code. (continued on next page) Remote Annex 2000 Hardware Installation Guide...
Page 61 Displays and sets Changing Novell/IPX EEPROM values conﬁguration parameters. relevant to Novell/IPX network addressing, including the IPX load/dump ﬁle server. lat_key [-d] Sets the LAT key. Connecting to a DEC VMS host. (continued on next page) Remote Annex 2000 Hardware Installation Guide...
Page 62 Deﬁnes a serial port as Checking or a Serial Line Internet changing a serial Protocol (SLIP) port’s settings. network interface. stats [-slip] Displays current Checking the network statistics network resources. gathered by the ROM. Remote Annex 2000 Hardware Installation Guide...
Page 63: Addr
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.
Page 64 Ethernet address (hex): 00-80-2D-00-18-B6 Internet address: 192.9.200.214 Subnet mask: 255.255.0.0 Broadcast address: 192.9.200.0 Preferred Load Host address: 192.9.200.88 Preferred Dump Host address: 192.9.200.88 Load/Dump Gateway address: 192.9.200.10 Type of IP packet encapsulation: <ethernet> Load Broadcast: Y Remote Annex 2000 Hardware Installation Guide...
Page 65 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 deﬁne an IP address for the Remote Annex, it will attempt to learn the address using BOOTP or RARP.
Page 66: Boot
Reset A successful boot disables the Console and the ROM monitor. The boot command accepts a file name for the Remote Annex 2000’s image. If the file name is not specified, boot displays the default file name and prompts for one. If you do not provide a file name, or have not defined one for the Remote Annex 2000, boot requests the default file oper.56.enet.
Page 67 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...
Page 68 ....EOF The next example shows a boot using tftp. The Remote Annex 2000 always tries to open a file using bfs first. If unsuccessful, the Remote Annex uses tftp to open the file.
Page 69 ....EOF Saving image into storage device ... Erasing device |----------------------------| ......Erase completed Storing image ..... Storage completed Beginning execution of image... Annex Command Line Interpreter * Copyright 1993, 1995\ Xylogics, Inc. Remote Annex 2000 Hardware Installation Guide 3-11...
Page 70 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 6 EOF Ethernet Statistics Frames Received: 1031 Frames Sent: 1031 CRC Errors: Carrier Sense Losses: Alignment Errors: Clear to Send Losses: Resource Drops: Collisions Detected: Bus Wait Drops: Excessive Collision Losses: Bad Types/Lengths: 3-12 Remote Annex 2000 Hardware Installation Guide...
Page 71: Config
Chapter 3 ROM Monitor Commands conﬁg The conﬁg 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 conﬁg command display contains information describing whether or not Flash ROM is installed.
Page 72: Console-Baud
To return to the “monitor::” prompt strike the “carriage return <CR>” key. [Baudrate Range: 50–9600 BAUD] Select Baudrate []: This command has no effect on the port’s baud rate after the Remote Annex 2000 is booted. 3-14 Remote Annex 2000 Hardware Installation Guide...
Page 73 To provide remote access to the Remote Annex 2000 ROMs: 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.
Page 74: Erase
If the self-boot option is installed, the erase command prompts for which non-volatile memory to erase: EEPROM or FLASH. Entering 1 at the prompt causes the Remote Annex 2000 to erase the EEPROM memory (configuration information); entering 2 at the prompt causes the Remote Annex 2000 to erase the Flash memory (self-boot image).
Page 75: Help
Chapter 3 ROM Monitor Commands help Entering help, or ?, displays brief descriptions of the Remote Annex 2000 ROM Monitor commands. Remote Annex 2000 Hardware Installation Guide 3-17...
Page 76: Image
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 | ﬁlename] The filename argument permits up to 100 characters. To return the image name to its default, enter a pair of double-quote characters ("").
Page 77: Ipx
The command display looks like this: monitor:: ipx –d IPX preferred load file server: “saturn” IPX frame type: "802.3" IPX dump user name: “HOBBES” IPX dump password: <SET> IPX dump path name: “SYS:\user\hobbes\” Remote Annex 2000 Hardware Installation Guide 3-19...
Page 78: Lat_Key
[–d ] The lat_key command display looks like this: monitor:: lat_key Enter LAT KEY [<uninitialized>]:: The lat_key –d command displays the current LAT key setting: monitor:: lat_key –d Enter LAT KEY [<uninitialized>]:: 3-20 Remote Annex 2000 Hardware Installation Guide...
Page 79: Mop
Chapter 3 ROM Monitor Commands 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. The command syntax is: mop [–d] The mop command display looks like this: monitor:: mop Enter preferred MOP load/dump address [<uninitialized>]::...
Page 80: Net
The Ethernet transceiver loopback test causes the Net LED to turn off. If the unit passes this test, the Net LED turns on and the console displays Passed. If the Remote Annex 2000 fails, the Net LED remains off, and the console displays an error message.
Page 81 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: The Remote Annex 2000 has faulty Ethernet port electronics.
Page 82: Option_Key
The command syntax is: option_key [–d ] The option_key command display looks like this: monitor:: option_key Enter option_key [<uninitialized>]:: The option_key –d command displays the current settings: monitor:: option_key –d option_key: <uninitialized> 3-24 Remote Annex 2000 Hardware Installation Guide...
Page 83: Ping
IP address required, ie: ping 132.245.33.69\ [data bytes] [npackets] To exit out of ping either wait for npackets to be transmitted or, at any point, type q. The ping statistics display upon exit. Remote Annex 2000 Hardware Installation Guide 3-25...
Page 84: Ports
(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.
Page 85 - The Printer Port does not require a loopback plug. ARNING 1) Async Serial Ports 2) Printer Port Selection (Return to exit):: Remote Annex 2000 Hardware Installation Guide 3-27...
Page 86: 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.
Page 87 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. Remote Annex 2000 Hardware Installation Guide 3-29...
Page 88: Slip
Remote load/dump host address: 192.9.200.88 Should this interface be used for memory dumps? (y/n) [y]:: Enter the baud rate [9600]::38400 Enter the number of stop bits (1,1.5,2) [1]:: Enter the parity (none,even,odd) [none]:: 3-30 Remote Annex 2000 Hardware Installation Guide...
Page 89: Table 3-2. The Slip Command Prompts
SLIP interface and the SLIP parameters are ignored. The default is n. Enter local endpoint Speciﬁes the Remote Annex 2000 IP address for address this SLIP interface. The Remote Annex 2000 boots over the SLIP interface only if this address is set.
Page 90 By default, this is the same as the remote end-point address. Should this interface Enables the Remote Annex 2000 to use a SLIP be used for memory interface for memory dumps. The default is y.
Page 91: Stats
The number of packets dropped because the ROM code could not buffer them quickly enough. The ROM code cannot always handle back-to-back incoming packets. The Remote Annex 2000 accepts the first response it receives and drops all others. Dropped packets are normal.
Page 92 Clear to Send signal – usually the result of excessive traffic. Collisions Detected The number of times the Remote Annex 2000 had to retry transmissions automatically – usually the result of normal Ethernet traffic. These retries do not cause the boot command to display ‘‘*.”...
Page 93: Chapter 4 Troubleshooting Procedures
Chapter 4 Troubleshooting Procedures his chapter describes power-up and booting, troubleshooting during booting, and the ﬁle 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.
Page 94: Power-Up And Boot Procedures
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 button Test on the front panel within 3 seconds of powering-up or a system reset puts the Remote Annex 2000 into test mode.
Page 95: Table 4-1. Normal Mode Error-Free Led States
Off. Flashing irregularly. Flashing regularly (about 1Hz). Activity N1: Testing All front panel LEDs light for a few seconds, then all but the Power LEDs LED turn off, confirming that all LEDs are operational. Remote Annex 2000 Hardware Installation Guide...
Page 96 After passing this test, the Net LED flashes and remains on. Activity N4: Looking The Load LED flashes while the Remote Annex 2000 waits for a load for the Boot File server host to respond to its load request.
Page 97: Table 4-2. Normal Mode Error Led States
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...
Page 98 Supplying the wrong name to any of the boot commands (na boot, dumpboot, or the superuser CLI boot). If you are uncertain as to why the Remote Annex 2000 booted the wrong image, enter test mode and issue an image –d command. This command shows which host file the Remote Annex is trying to load.
Page 99: Test Mode Diagnostics
T3: Testing network T4: At monitor prompt T5: Looking for boot ﬁle T6: Loading code using the boot command T7: Running operational code Key: On continuously. Off. Flashing irregularly. Flashing regularly (about 1Hz). Remote Annex 2000 Hardware Installation Guide...
Page 100 All front panel LEDs light for a few seconds, then all but the Power LEDs LED turn off. This sequence confirms that all LEDs are operational. At this point, the Remote Annex 2000 is in normal mode; pressing the button readies it for the next activity. Test...
Page 101: Table 4-4. Test Mode Error Led States
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.
Page 102: Boot Failures
Network Test was access the ROM Monitor prompt. Aborted or the net Command Failed Activity TE7: Booted The Remote Annex 2000 has just loaded an inappropriate image. Clear Wrong Image this error by pressing the button. The Remote Annex 2000 Reset...
Page 103 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 ﬁle and an error occurs during the boot process.
Page 104: Boot Error Report
TFTP error reporting complies with the standard, predeﬁned TFTP error codes. The Remote Annex 2000 generates a boot error report for the IP address from which it tried, and failed, to boot. The error count pinpoints the error that caused the boot failure. For...
Page 105: 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 on page 3-22).
Page 106: Correcting Remote Annex 2000 Parameters
The following parameters must accurately reﬂect both the Remote Annex 2000 and the network environment in which it operates. Verify the Remote Annex 2000’s IP address using the addr command. If your network configuration does not support the factory defaults, verify the following parameters using the addr command: The broadcast address.
Page 107 Remote Annex 2000 cannot boot. Correct the name using the image command. If the address for the preferred load server host is incorrect, the boot takes longer, since the Remote Annex 2000 has to broadcast for a host. Correct the load host’s address using the addr command.
Page 108: Load Server Host Not Responding
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.
Page 109 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.
Page 110 The Remote Annex Administrator’s Guide for UNIX provides more information on these commands. A Remote Annex 2000 that has been reconfigured as a load server host, but not rebooted, cannot boot another Remote Annex 2000 on the network. Rebooting the Remote Annex 2000 load server host ensures that the parameters are set.
Page 111 %%%%%%%% opcom 23-DEC-1994 08:03:50.55 %%%%%%%% Message from user DECNET DECnet event 0.3, automatic line service From node 1.69 (BINGO), 23-DEC-1994 08.03.50.52 Circuit SVA-0, Load, Successful, Node =2.69 (BART) File = MOM$SYSTEM_SOFTID:OPER_56_ENET.SYS, Operating System Ethernet address = 00-80-2D-00-1A-DE Remote Annex 2000 Hardware Installation Guide 4-19...
Page 112: Remote Annex 2000 Dumps
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.
Page 113 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.
Page 114: Table 4-9. Dump File Naming Conventions
Chapter 4 Troubleshooting Procedures Each dump ﬁle 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.
Page 115: Appendix A Port Pin/Signal Allocations
Appendix A Port Pin/Signal Allocations his appendix identiﬁes 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.
Page 116: 10Base2 Ethernet Port
Port Pin/Signal Allocations Table A-1. Serial Port Pin/Signal Allocations Pin Number Signal 10Base2 Ethernet Port Figure A-2 illustrates a 10Base2 BNC Ethernet connector. Coaxial Center Conductor Coaxial Shield Figure A-2. 10Base2 BNC Ethernet Connector Remote Annex 2000 Hardware Installation Guide...
Page 117: 10Base5 Ethernet Port
Table A-2. 10Base5 Ethernet Port Pin/Signal Allocations Pin Number Signal Chassis ground Collision + Transmit + Receive + Ground (for transceiver power) 7–8 Collision – Transmit – Receive – + 12 volts (for transceiver power) 14–15 Remote Annex 2000 Hardware Installation Guide...
Page 118: 10Baset Ethernet Port
10BaseT RJ45 Ethernet port receptacle. Table lists the connector’s pin/signal allocations. Figure A-4. 10BaseT RJ45 Ethernet Port Receptacle Table A-3. 10BaseT Ethernet Port Pin/Signal Allocations RJ45 Pin Signal TXD + TXD – RXD + RXD – Remote Annex 2000 Hardware Installation Guide...
Page 119: Appendix B Cables And 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. Serial Cable Wiring Diagrams...
Page 120: Figure B-1. Dte Crossover Terminal Cable
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. DCE Straight-Through Modem Cable Remote Annex 2000 Hardware Installation Guide...
Page 121: Loopback Connectors
Table B-2 shows this connector’s pins and Connector signals. Table B-2. 10BaseT Ethernet Loopback Connector Wiring Pin Number Signal Connects to Pin Number Signal Transmit + Receive + Transmit – Receive – Remote Annex 2000 Hardware Installation Guide...
Page 122 Receive; DTR and CTS; and RTS, DCD, and DSR. Table B-3 shows Connector this connector’s pins and signals. Table B-3. Serial Port Loopback Connector Wiring Pin Number Signal Connects to Pin Number Signal 4, 7 DCD, DSR Remote Annex 2000 Hardware Installation Guide...
Page 123: Appendix C Warranty And Technical Support Information
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. If you recently purchased your Remote Annex 2000 you may be eligible for our 30 Day Free Support Program.
Page 124: Customer Assistance Programs
Premium Customer Assistance. Prioritized Support Response. Express Hardware Replacement. Automatic Software Updates. Multiple-site Software Redistribution License. On-site Support and Consulting. University Support Program. Contact your reseller for information on selecting and purchasing a support plan. Remote Annex 2000 Hardware Installation Guide...
Page 125: What To Do If The Remote Annex 2000 Fails
Xylogics’ Sales Support at (617) 272-8140. If for some reason the Remote Annex 2000 is not covered under any warranty or agreement, contact Xylogics Customer Returns at (617) 272-8140, extension 307, for a Return Authorization (RA) number.
Page 126: Terms And Conditions Of The Warranty
Section 2-715 of the Uniform Commercial Code. The Buyer waives the Beneﬁt of any rule that disclaimer of warranty shall be construed against the Seller, and agrees that such disclaimers herein shall be construed liberally in favor of the Seller. Remote Annex 2000 Hardware Installation Guide...
Page 127 The Seller’s liability, if any, with respect to any claim arising from the Agreement, shall be limited to repair or replacement as provided in the Warranty. Remote Annex 2000 Hardware Installation Guide...
Page 128: Remote Annex 2000 Dumps
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.
Page 129: Repair Information Request Form
Using either the CLI stats command or the ROM Monitor conﬁg command, obtain: Number of ports: _________________________________________________________ Memory size: _________________________________________________________ Software revision: _________________________________________________________ ROM Monitor Revision: _________________________________________________________ Hardware revision: _________________________________________________________ MLB Serial number: _________________________________________________________ Remote Annex 2000 Hardware Installation Guide C-11...
Page 130 Ethernet ThinNet Twisted Pair Type of IP encapsulation: Ethernet IEEE802 Problem description (indicate commands issued, error messages received, source of errors, etc.):_____________________________________________________ _________________________________________________________ _________________________________________________________ Network environment (e.g., Ethernet backbone, multiport, other hosts):___________________________________________________ _________________________________________________________ C-12 Remote Annex 2000 Hardware Installation Guide...
Page 131 Which front panel status indicators were on or ﬂashing at the time of failure? _________________________________________________________ _________________________________________________________ Did the unit pass the Ethernet loopback test? Y If problems are port-related, what were the results of the ports command? _________________________________________________________ _________________________________________________________ _________________________________________________________ _________________________________________________________ Additional information: Remote Annex 2000 Hardware Installation Guide C-13...
Page 132 Appendix C Warranty and Technical Support Information Additional information (continued): C-14 Remote Annex 2000 Hardware Installation Guide...
Page 133: Index
10Base5 connector 1-11 setting 3-7 10Base5 loopback connector wiring B-3 10Base5 port pin/signal allocation A-3 10BaseT connector 1-11 Cables 10BaseT loopback connector wiring B-3 maximum lengths 2-8, 2-9 10BaseT port pin/signal allocations A-4 Remote Annex 2000 Hardware Installation Guide Index-1...
Page 134 Novell boot 2-13 error-free normal mode 4-3 error-free test mode 4-7 normal mode error states 4-5 test mode error states 4-9 OPER_56_ENET.SYS 4-19 InfoFACTS service xxi option_key command 3-24 initial boot parameters examples 3-24 Index-2 Remote Annex 2000 Hardware Installation Guide...
Page 135 3-33 ROM Monitor example 3-33 command syntax 3-2 status indicators 1-8 description of 1-5 subnet mask list of commands 3-2 setting 3-7 ROM Monitor vs. Console Monitor 1-5 Support Source CD xx Remote Annex 2000 Hardware Installation Guide Index-3...
Page 136 Thick Ethernet 2-4 Thin Ethernet 2-3 troubleshooting during power-up and booting 4-2 Twisted Pair Ethernet 2-5 UNIX boot 2-15 VMS boot 2-16 weight 1-12 World Wide Web Bay Networks home page on xix Index-4 Remote Annex 2000 Hardware Installation Guide...

Bay Networks Remote Annex 2000 Hardware Installation Manual

Preface

Chapter 1 Introduction

Chapter 2 Installing the Remote Annex 2000

Chapter 3 ROM Monitor Commands

Chapter 4 Troubleshooting Procedures

Appendix A Port Pin/Signal Allocations

Appendix B Cables and Connectors

Appendix C Warranty and Technical Support Information

Index

Quick Links

Need help?

Questions and answers

Related Manuals for Bay Networks Remote Annex 2000

Summary of Contents for Bay Networks Remote Annex 2000

Table of Contents