PortMaster Communications Server Hardware Installation Guide
Author: spider

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

# Troubleshooting A

This appendix provides the following troubleshooting procedures for the
PortMaster Communications Server:

- Observing LED behavior

- Observing boot messages

- Replacing a fuse

## Observing LED Behavior

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

For information on contacting Lucent Remote Access Technical Support, see "Contacting Lucent Remote Access Technical Support" on page xiii.

`Table A-1 Hardware Problems and Solutions`
# LED Behavior | # Possible 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 in the AC version, see "Replacing a Fuse" on page A-7.
During startup, the system LED fails to light, stays lit, or blinks three times per second continuously. | A hardware problem has occurred. | Contact Lucent Remote Access Technical Support.
During startup, the system LED blinks once per second for more than a minute. | DIP switch 2 is up and no boot server is present. Nonvolatile RAM contents are corrupt. | If no boot server is available, verify that DIP switch 2 is down and reboot; otherwise, see the network booting procedure in the Configuration Guide for PortMaster Products. If nonvolatile RAM contents are corrupt, follow the Configuration Guide for PortMaster Products procedure for network booting and rewriting the contents of nonvolatile RAM.
Immediately after booting, the system LED stays solidly lit or does not light. Note: This behavior does not refer to the boot sequence, during which the system LED is not lit for between 5 and 7 seconds. | A component might have loosened during shipping. | Open the PortMaster using antistatic precautions (see "Safety Recommendations" on page 2-3). Verify the following: All four SIMMs are firmly seated. The PROM is firmly in place. The Ethernet card is firmly in place, and the standoff screws are tight. The expansion board jumpers are positioned correctly. The 60-wire ribbon bus cable is firmly seated. If all items have been verified and the problem is not fixed, refer to "Observing Boot Messages" on page A-5, and boot in console mode. If the boot messages do not suggest a solution, record the information and contact Lucent Remote Access Technical Support.
After an ISDN S/T unit boots, an ISDN S/T status LED turns off. | The BRI is not able to synchronize with the attached NT1. | Ensure that the correct directory numbers have been assigned to each port of the BRI. Ensure that the cable connecting the BRI and the NT1 is securely attached. If the problem persists, contact your service provider.
After an ISDN U unit boots, an ISDN U status LED blinks once per second or turns off. | No SPID is set on the port. | Verify that the correct SPID has been assigned to the port and that the correct switch type is set. See the Command Line Administrators Guide for the appropriate ISDN BRI commands.
There is no circuit to the telephone company. | Verify that the BRI cable is securely attached. If the problem persists, contact your service provider.
During operation, the system LED remains solidly on or completely off. | A hardware problem might have been caused by an external device. | Disconnect all external devices except the diagnostics terminal or PC. If the LED is still solidly lit or completely off, contact Lucent Remote Access Technical Support.
No console login prompt is displayed. | Console terminal settings are incorrect, or a connection or cable is inoperable. | Verify terminal settings of 9600bps, 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 null modem cable and that it is properly connected at both ends. For cable information see "Pinout Specifications" on page B-1.
The Link LED is not lit when connected to a 10BaseT Ethernet hub. | There is no link integrity. | Verify that DIP switches 4 and 5 are up and that you have a working 10BaseT cable properly connected to the PortMaster 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 PortMaster is not receiving, or sending traffic, the network LED is not lit. | Verify that the network cabling is correct.
| If packets cannot be passed, the network might be cabled incorrectly. | 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 booting 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 Boot Messages

If you are having difficulty booting the PortMaster and are unable to isolate the problem by observing LED behavior, boot the PortMaster 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-7).

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

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

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

   PortMaster Diagnostic Boot Messages

   Testing Low Memory.... Testing System Clock.... Testing System Memory.... 1024K Checking Boot Rom.... Calibrating.... 33MHz Starting FLASH Boot..... Booting From Flash Type AM29F040 Loading Image at 0fff0000 17082 flash copy complete Verifying Load Module Checksum... Starting Load Module... Loading kernel...586988 bytes Testing High Memory... . 1024K ISDN found in slot 1 - Testing memory.. 512K Found 11 ports.... ether0 active... 64K burst-IO Running ComOS... PortMaster Console login:

   :

   `Interpreting the Diagnostic Boot Messages`
   ## Field | ## Possible Message | ## Explanation
   --- | --- | ---
   Testing Low Memory | ERROR | This error indicates a boot failure. Record all information to this point and contact Lucent Remote Access Technical Support.
   Testing System Clock | ERROR | This error indicates a boot 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 boot failure. Record all information to this point and contact Lucent Remote Access Technical Support.
   Checking Boot Rom | ERROR | This error indicates a boot failure. Record all information to this point and contact Lucent Remote Access Technical Support.
   Calibrating | 33MHz | Processor speed.
   Starting FLASH Boot | N/A | N/A
   Booting from FLASH type | AM29F040 | Nonvolatile memory brand name.
   Loading Image at | 0fff0000 | RAM address.
   flash copy complete | 17082 | Counter for nonvolatile memory bytes transferred to RAM. If the counter freezes, record all information to this point and contact Lucent Remote Access Technical Support.
   Verifying Load Module Checksum | Invalid Length for Flash at RAM address | This error indicates a boot failure. Record all information to this point and contact Lucent Remote Access Technical Support.
   Starting Load Module | N/A | N/A
   Loading kernel | 506000 | Size of kernel image in bytes.
   Testing High Memory | ERROR at failed memory address | This error indicates a boot failure. Record all information to this point and contact Lucent Remote Access Technical Support.
   Async found in slot ISDN found in slot Testing memory | 512K | ISDN or asynchronous interface found. Test of memory in progress.
   Found x Ports | 11, 21, 25, or 31 | Number of ports found, including C0, P0, or W1.
   ether0 active | 64K burst - IO | Ethernet interface found.
   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 nonvolatile RAM recovery.
   PortMaster Console login: | N/A | System is up and running.

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

## Replacing a Fuse

If your PortMaster loses power while connected to an active power source, check the fuse.

Follow these instructions to check and replace the fuse in the PortMaster.

### Required Equipment

- 5/32-inch flathead screwdriver

- 250V, 2A fuse

### Procedure

1. Turn the power switch off and disconnect the PortMaster from the power source (PM-2i shown).

2. Detach the power cord from the PortMaster.

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 fuse can be inserted from either end.

5. Press the fuse door shut until it clicks.

6. Reconnect the power cord to the PortMaster.

7. Turn the power switch on (PM-2i shown).

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

Copyright © 1998, Lucent Technologies. All rights reserved.