[Top] [Prev] [Next] [Bottom]

Troubleshooting        3


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  
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.

A hardware problem has occurred.

Contact Lucent Remote Access Technical Support.

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

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

A nonvolatile RAM problem has occurred.

Contact Lucent Remote Access 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 Remote Access Technical Support.

No console login prompt is displayed.

Terminal settings are incorrect or a connection or cable is inoperable.

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.

Refer to 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 Remote Access 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:

  1. Turn the power switch off.

  2. Reinsert the PCMCIA modem card. Consult the manufacturer's documentation to ensure that the modem card is inserted with the correct side up. (See "Connect a PCMCIA Modem (OR-M)" on page 2-8.)

  3. Turn on power (see "Turn On Power" on page 2-11).

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:

  1. Attach a console (see "Connect a Console" on page 2-3).

  2. Turn on power (see "Turn On Power" on page 2-11).

  3. Observe the boot messages displayed on the console screen.

    Note ¯ Boot messages vary slightly, depending on the version of the
    programmable ROM (PROM) and ComOS.

The following example of boot messages is from an OR-M:

Lucent Technologies, Inc. Boot Prom Rev K

 

Testing Low Memory ....

Testing System Clock ....

Testing System Memory .... A000

Checking Boot Rom ....

Starting FLASH Boot .....

Booting From Flash Type Am29F040

Loading Image at 0fff0000

320112 flash copy complete

Verifying Load Module Checksum ...

Starting Load Module ...

Testing High Memory ... . 1024K

PCMCIA slot .... PCMCIA card type

Found 2 ports....

Running ComOS...

PortMaster Console login:

Use Table A-2 to interpret possible diagnostic boot messages.

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 Remote Access Technical Support.

Testing System Clock

ERROR

This error indicates a startup failure. Record all information to this point and contact Lucent Remote Access 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 Remote Access Technical Support.

Checking Boot Rom

ERROR

This error indicates a boot failure. Record all information to this point and contact contact Lucent Remote Access 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 Remote Access 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 Remote Access 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 contact Lucent Remote Access 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 Remote Access 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 nonvolatile RAM has been corrupted. Refer to the troubleshooting chapter of the Configuration Guide for PortMaster Products for instructions on Flash 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

  1. Turn the power switch off and disconnect the Office Router from the power source.

  2. Detach the power cord from the Office Router.

  3. Insert a 5/32-inch flathead screwdriver between the fuse door and the chassis, and gently pull the fuse door open.

  4. If the white outer coating of the fuse is discolored (burned), replace the fuse.

    The 250V, 2A fuse can be inserted from either end.

  5. Press the fuse door shut until it clicks.

  6. Reconnect the power cord to the Office Router.

  7. Turn the power switch on.


[Top] [Prev] [Next] [Bottom]

spider@livingston.com
Copyright © 1998, Lucent Technologies, Inc. All rights reserved.