The DS300 Storage Subsystem provides 3 LED indicators located on the front of the storage enclosure. Shown in Figure 1, the three enclosure LEDs are defined in the following table:
Table 1. Storage Enclosure Disk Drive LED Descriptions
|
Description |
Color |
Indication |
Possible solution |
LED 1 |
Power On |
Green |
Normally ON: This indicates that power is being supplied to the enclosure. OFF indicates no power, or that there is an issue with the power supplies. |
Check Power Supply LEDs. Refer to power supply LEDs table |
LED 2 |
Identification |
Blue |
Normally OFF. ON solid indicates that the enclosure is being identified. The enclosure management functionality on the RAID controller activates this LED when commanded to do so via a command from the Host. |
N/A |
LED 3 |
Enclosure Fault |
Amber |
Normally OFF: This indicates that no faults exist in the enclosure. ON solid indicates that the storage enclosure has a fault. This LED is driven by the enclosure management functionality on the RAID controller.
Flashing: Invalid configuration has been detected. Make sure the controller and power supply are installed in A side slots. DS300 1RL model only.
|
1. Check LEDs for all components on enclosure (disk drives, power supplies, controllers) and follow the solution instructions provided for the respective illuminated LED.
2. If no other fault LED is on, first replace the controller: DS300 – 13N1781 DS300 1RL – 13N1782
3. Replace the chassis/backplane ASM 13N1786 |
1 The enclosure fault amber LED will be ON solid when one or more of the following conditions exist:
|
The iSCSI-SCSI RAID controller has 12 LED indicators. These 12 LED indicators are located on each of the iSCSI RAID controllers installed into the I/O option slots in rear of the enclosure. Figure 2 and 3 show the location of the controller LEDs:
SP1= Serial Port 1: CLI port
SP2 = Serial Port 2: Debug port (for Engineering use only)
Note: 1RL model has only the management port (ETH0)
The twelve LEDs are defined as follows:
|
Description |
Color |
Indication |
Possible Solution |
LED 1 |
Controller Ready |
Green |
Normally ON: This indicates that the controller has successfully booted. |
N/A |
LED 2 |
Battery Fault |
Amber |
ON indicates that the battery is not capable of sustaining memory in case of power loss. Possible causes include:
OFF indicates that the battery is capable of sustaining memory in case of power loss. |
Remove the controller and replace the battery then reinsert the controller.
Replacement battery: 13N1785 Note: N/A for 1RL model since it does not have a battery. |
LED 3 |
Cache Dirty |
Amber |
ON indicates that there is data in the cache that has not been written to a disk or synchronized to the redundant controller cache. |
The Cache Dirty LED will go on and off at varying rates and durations during normal operation. No user action is required when this LED goes on.
This also may indicate an improper controller shutdown. Restart the controller to flush the cache.
WARNING! Do not remove power from the enclosure or remove the controller from the enclosure when a Cache Dirty LED is illuminated. Doing so could cause loss of data in the cache that is not mirrored.
Notes: 1)This is not a FRU 2) N/A for 1RL model since it does not support cache. |
LED 4 |
Processor DIMM Fault |
Amber |
ON indicates that the Processor DIMM memory has failed. Possible causes include:
OFF indicates that the DIMM memory is operating normally. |
1. Replace the controller: DS300 – 13N1781 DS300 1RL – 13N1782
|
LED 5 |
Cache DIMM Fault |
Amber |
ON indicates that the cache DIMM memory has failed. Possible causes include:
OFF indicates that the cache DIMM memory is operating normally. |
1. Replace the DIMM 256MB DIMM – 73P4026
2. If theDIMM replacement does not fix the problem, replace the controller: DS300 – 13N1781 DS300 1RL – 13N1782
Note: DS300 1RL does not have cache. |
LED 6 |
Controller Not Ready |
Amber |
ON indicates controller is not ready. |
This indicates that the controller has not completed POST. Contact IBM Support center to attempt to recover the controller. |
LED 7 |
GbE Link Status |
Green |
ON indicates that the GbE link is up and operational. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
LED 8 |
GbE Activity |
Green |
ON indicates that packets are being transmitted or received. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
LED 9 |
GbE Link Status |
Green |
ON indicates that the GbE link is up and operational. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
LED 10 |
GbE Activity |
Green |
ON indicates that packets are being transmitted or received. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
LED 11 |
GbE Link Status |
Green |
ON indicates that the GbE link is up and operational. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
LED 12 |
GbE Activity |
Green |
ON indicates that packets are being transmitted or received. |
First check the status on the switch. Then try another cable. Then another port on the same switch in the same network segment.
Refer to PD Maps |
The green Power OK LED is ON when the power supply is operating normally.
The amber Fault LED is ON when the enclosure services module detects a fault. It flashes when the power/cooling module locate feature is selected.
The amber Fault LED will be ON solid when one or more of the following conditions exist:
The FRU P/N for the power supply is 13N1784
Each disk drive carrier has two LED indicators that are visible from the front of the storage enclosure. The green Activity LEDs are controlled directly by the SCSI disk drives; when ON, the Activity LEDs indicate activity. The amber Fault LEDs are controlled by the enclosure management circuitry; when ON, the Fault LEDs indicate a disk drive failure.
You can run limited diagnostic from one controller to any drive (either internal or in an expansion unit) using the Command Line Interface (CLI). The Read/Write buffer test commands are issued to the selected drive from either controller. The drive side diagnostic verifies the path from the controller to the HDD and also ensures that the HDD is ready and accepting commands.
You perform the diagnostic from a Telnet CLI session. You must be in administrator mode to run diagnostics. For additional information on the CLI see Using the CLI.
Note: You may want to locate and identify the drive or drives in the enclosure in the event you need to re-seat or replace the drive. The identify device command syntax is shown in the following example.
DS300[X]# device identify
2304 2816 3328 3840 65792 66304 66816 start
2560 3072 3584 65536 66048 66560 67584 stop
The buffer test command syntax is shown in the following example. This command performs a read/write buffer and compare test on the specified drive, where device# is the specified drive.
buffer device# [iteration count] [stop-on-error]
Set iteration count to the desired value. A value of 100 takes about 45 seconds to run. Set the iteration count to continuous to run the test without a specified end. To stop the test, press Escape. To get intermediate results press Enter.
Set stop-on-error to stop on any error.
The following shows a sample CLI output:
Note: Make sure to halt I/Os before starting the test.
DS300[X]> administrator
DS300[X]# diag
DS300[X] (diag)# buffer
2304 2816 3328 3840 66560 67584
2560 3072 3584 66304 66816
DS300[X] (diag)# buffer 2304
<number of iterations> stop
continual
DS300[X] (diag)# buffer 2304 10
0 discrepancies discovered over 10 iterations
DS300[X] (diag)#
If the selected drive does not run this test successfully, then run the test on another drive. Return to the PD maps (click the Back button on your browser) for more help in isolating the problem.
Note: If you replace a drive, make sure you do a device scan from the CLI. The device scan syntax and a sample return message are shown in the following example:
DS300[X]# device scan
Scan complete.
New devices that have been discovered:
66816. IBM-ESXS Disk (enclosure 1 slot 5)
All drives will always appear in the lists of controller A and B. Although drives are located on either the A or B side of the enclosure, this does not indicate controller ownership. Thus drives installed on either side of the enclosure may be owned by either A or B controller.
Internal drives – left bank (side B) |
65536 IBM-ESXS Disk (enclosure 1 slot 0) SCSI Disk 68.37GB 65792 IBM-ESXS Disk (enclosure 1 slot 1) SCSI Disk 68.37GB 66048 IBM-ESXS Disk (enclosure 1 slot 2) SCSI Disk 68.37GB 66304 IBM-ESXS Disk (enclosure 1 slot 3) SCSI Disk 68.37GB 66560 IBM-ESXS Disk (enclosure 1 slot 4) SCSI Disk 68.37GB 66816 IBM-ESXS Disk (enclosure 1 slot 5) SCSI Disk 68.37GB 67584 IBM-ESXS Disk (enclosure 1 slot 6) SCSI Disk 68.37GB
|
Internal drives – right bank (side A) |
2304 IBM-ESXS Disk (enclosure 1 slot 7) SCSI Disk 68.37GB 2560 IBM-ESXS Disk (enclosure 1 slot 8) SCSI Disk 68.37GB 2816 IBM-ESXS Disk (enclosure 1 slot 9) SCSI Disk 68.37GB 3072 IBM-ESXS Disk (enclosure 1 slot 10) SCSI Disk 68.37GB 3328 IBM-ESXS Disk (enclosure 1 slot 11) SCSI Disk 68.37GB 3584 IBM-ESXS Disk (enclosure 1 slot 12) SCSI Disk 68.37GB 3840 IBM-ESXS Disk (enclosure 1 slot 13) SCSI Disk 68.37GB
|
Figure 6 - ServeRAID manager enclosure graphics