4.If the activity LED on a disk drive does not illuminate during the boot cycle, the disk drive may be installed incorrectly or its lightpipes may be damaged.

Check the lightpipe on the disk drive as follows:

a.Remove the disk drive.

b.Inspect the lightpipes for damage. If a lightpipe is damaged, contact HP.

CAUTION: The lightpipes are fragile. Be careful not to damage them when you inspect them or when you reinsert the disk drive.

c.Replace the disk drive.

d.Power on the server. Determine whether the LED illuminates during the boot cycle. If it does not, contact HP.

LAN LEDs

There are LAN LEDs on the rear bulkhead of the LAN HBA in PCI-X slot 2 of the HP Integrity rx3600 server.

HBA Bulkhead LAN LEDs

There are two 1 Gb LAN ports on the LAN HBA bulkhead. These are LAN A and LAN B. Table 5-29lists the 1 Gb LAN A interface provides three LEDs on the LAN bulkhead.

Table 5-29

LAN A Connector LEDs

 

 

 

 

 

LAN LED

Location

Color

State

 

 

 

 

Not used

Top

None

None

 

 

 

 

1000Mb

2nd from top

Blinking

The 1000 Mb/s ethernet protocol and twisted-pair wiring is

 

 

amber

enabled.

 

 

 

 

 

 

Off

No link

 

 

 

 

100Mb

2nd from bottom

Blinking

The 100 Mb/s with ethernet protocol and twisted-pair wiring

 

 

green

is enabled.

 

 

 

 

 

 

Off

No link

 

 

 

 

Activity

Bottom

Blinking

The activity LED is enabled.

 

 

green

 

 

 

 

 

 

 

Off

No activity

 

 

 

 

Table 5-30lists the 1 Gb LAN B interface provides two LEDs on the LAN bulkhead.

Table 5-30

LAN B Connector LEDs

 

 

 

 

 

 

LED

 

Location

Color

Description

 

 

 

 

 

Speed (upper

 

Upper left

Yellow

The 1000 MHz with ethernet protocol and twisted-pair wiring

left)

 

 

 

is enabled.

 

 

 

 

 

 

 

 

Green

The 100 MHz with ethernet protocol and twisted-pair wiring

 

 

 

 

is enabled.

 

 

 

 

 

 

 

 

Off

No link

 

 

 

 

 

Link (upper

 

Upper right

Green

link is enabled.

right)

 

 

 

 

 

 

Off

No link

 

 

 

 

 

 

 

 

172 Troubleshooting