[Top] [Table Of Contents] [Prev] [Next] [Index]
6 out of 11 total pages
 

A Troubleshooting

 
This appendix provides the following troubleshooting information for the
PortMaster Office Router:
 

Observing LED Behavior

 
Table A-1 identifies LED behavior, likely causes of the behavior, and potential solutions

  Table A-1 Hardware Problems and Solutions  

 

  LED Indication

  Likely Cause

  Solution

  System LED does not light.

  Power is not present.

 Check the power switch, power cable, outlet, and fuse. For instructions on checking and changing the fuse,
see "Replacing a Fuse" on page A-8.

  During startup, the System LED fails to light, becomes solidly lit, or blinks three times per second continuously.

  There is a hardware problem.

  Contact Lucent InterNetworking Systems Technical Support.

  During startup, the System LED continues blinking once per second for more than a minute.

  •  DIP switch 2 is up and no boot server is present.
  •  If no boot server is present, verify that DIP switch 2 is down; otherwise, see the network booting procedure in the PortMaster Configuration Guide.  

 

  •  Nonvolatile RAM contents are corrupt.
  •  If nonvolatile RAM contents are corrupt, follow the PortMaster Configuration Guide procedure for network booting and rewriting the contents of nonvolatile RAM.

     

  Immediately after startup, the System LED stays solidly lit or does not light.

  A nonvolatile RAM problem has occurred.

  Contact Lucent InterNetworking Systems Technical Support.

  During operation, the System LED stays solidly lit or does not light.

  A hardware failure has occurred, possibly caused by an external device.

 If the LED stays solidly lit or does not light after you have removed all external devices, contact Lucent InterNetworking Systems Technical Support.
 No console login prompt is displayed.  Terminal settings are incorrect or a connection or cable is inoperable.
  •  Verify terminal settings of 9600 baud, 8 data bits, 1 stop bit, a parity of none, and software control (XON/XOFF).
  •  Verify that DIP switch 1 is up.
  •  Verify that you have a working console cable and that it is properly connected at both ends. For cable information, see "Console Cable" on page D-2.

  Link LED is solid off.

  If you are connected to an 10Base5 (AUI) Ethernet transceiver, the Link LED blinks only once at startup.

 

 Link LED is not lit when connected to a 10BaseT Ethernet hub.  There is no link integrity.

  Verify that DIP switch 3 is up and that you have a working 10BaseT cable properly connected to the Office Router and to the hub. Turn the power off and on to activate the DIP switch setting.

 Network LED is solidly lit.  Heavy traffic can cause the network LED to blink so rapidly that it appears to be solidly lit.  However, if packets cannot be passed, you might have an incorrectly cabled network.        Verify that the network cabling is correct.
 Network LED is not lit.  If the Office Router is not receiving, or sending traffic, the network LED is not lit.  Verify that the network cabling is correct.
 An undefined difficulty occurred at startup, but the cause cannot be determined from LED behavior.  See the solution column.  Try starting in console mode, and observe the boot messages. See "Observing Boot Messages" on page A-5. If the boot messages do not suggest a solution, record the information and contact Lucent InterNetworking Systems Technical Support.
.  
 

Observing the Console Display (OR-M)

 
Follow these instructions if port S1 does not appear on the console display during configuration of the Office Router:
 

Observing Boot Messages

 
If you are having difficulty starting the Office Router and are unable to isolate the problem by observing LED behavior, start the Office Router in console mode and check the boot messages.  
Follow these instructions to check boot messages:  
Use Table A-2 to interpret possible diagnostic boot messages.

  Table A-2 Interpreting the Diagnostic Boot Messages  

 
  Field   Possible Message   Explanation
 Boot Prom Rev  K  Version number of the installed boot PROM.
 Testing Low Memory  ERROR  This error indicates a startup failure. Record all information to this point and contact contact Lucent InterNetworking Systems Technical Support.
 Testing System Clock  ERROR  This error indicates a startup failure. Record all information to this point and contact Lucent InterNetworking Systems Technical Support.
 Testing System Memory  ERROR at failed memory address  This error indicates a startup failure. Record all information to this point and contact contact Lucent InterNetworking Systems Technical Support.
 Checking Boot Rom  ERROR  This error indicates a boot failure. Record all information to this point and contact contact Lucent InterNetworking Systems Technical Support.
 Starting FLASH Boot  N/A  N/A
 Booting From Flash Type  Am29F040  Nonvolatile RAM brand name.
 Loading Image at  0fff0000  RAM address.
 Flash copy complete  320112  Counter for nonvolatile RAM bytes transferred to RAM. If the counter freezes, record all information to this point and contact contact Lucent InterNetworking Systems Technical Support.
 Verifying Load Module Checksum  Invalid Length for Flash at RAM address  This error indicates a startup failure. Record all information to this point and contact contact Lucent InterNetworking Systems Technical Support.
 Starting Load Module  N/A  N/A
 Loading kernel
(OR-ST, OR-U, OR-LS, OR-HS only)
 506088 bytes  Counter for nonvolatile RAM bytes transferred to DRAM. If the counter freezes, record all information to this point and contact Lucent InterNetworking Systems Technical Support.
 Testing High Memory  ERROR at failed memory address  This error indicates a startup failure. Record all information to this point and contact Lucent InterNetworking Systems Technical Support.
 PCMCIA slot
(OR-M only)
 PCMCIA card type  PCMCIA card type.
 ISDN Found in Slot 0 - Testing memory
(OR-ST, OR-U only)
 512K  ISDN interface found. Test of ISDN memory in progress.
 Found x Ports  1, 2, 3  Number of ports detected. Note that S0 is one port and PCMCIA is another. The ISDN BRI counts as two ports.
 Ether0 active  16K burst - IO  Ethernet interface found; 16Kbps is detected as the maximum amount of data that can be input or output at any given time on the Ethernet interface.
 Running ComOS  N/A  If the system becomes suspended at this point and does not print the next message, the configuration of nonvolatile RAM has been corrupted. Refer to the troubleshooting chapter of the PortMaster Configuration Guide for instructions on nonvolatile RAM recovery.
 PortMaster Console login:  N/A  System is up and running.
 

Replacing a Fuse

 
If the Office Router loses power while connected to an active power source, check the fuse.  
Follow these instructions to check and replace the fuse in the Office Router.
 

       Required Equipment

 

       Procedure


[Top] [Table Of Contents] [Prev] [Next] [Index]
6 out of 11 total pages
spider@livingston.com
Copyright © 1999, Lucent Technologies. All rights reserved.