
Isolating a controller module expansion port connection fault
53
Isolating a controller module expansion port connection fault
During normal operation, when a controller module expansion port is connected to a drive enclosure, the expansion port
status LED is green. If the connected port’s expansion port LED is off, the link is down. Use the following procedure to
isolate the fault.
This procedure requires scheduled downtime.
NOTE:
Do not perform more than one step at a time. Changing more than one variable at a time can complicate the
troubleshooting process.
1.
Halt all I/O to the storage system as described in
.
2.
Check the host activity LED.
If there is activity, halt all applications that access the storage system.
3.
Check the Cache Status LED to verify that the controller cached data is flushed to the disk drives.
Solid – Cache contains data yet to be written to the disk.
Blinking – Cache data is being written to CompactFlash.
Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor.
Off – Cache is clean (no unwritten data).
4.
Reseat the expansion cable, and inspect it for damage.
Is the expansion port status LED on?
Yes – Monitor the status to ensure there is no intermittent error present. If the fault occurs again, clean the
connections to ensure that a dirty connector is not interfering with the data path.
No – Proceed to the next step.
5.
Move the expansion cable to a port on the controller enclosure with a known good link status.
This step isolates the problem to the expansion cable or to the controller module expansion port.
Is the expansion port status LED on?
Yes – You now know that the expansion cable is good. Return the cable to the original port. If the expansion port
status LED remains off, you have isolated the fault to the controller module expansion port. Replace the
controller module.
No – Proceed to the next step.
6.
Move the expansion cable back to the original port on the controller enclosure.
7.
Move the expansion cable on the drive enclosure to a known good expansion port on the drive enclosure.
Is the expansion port status LED on?
Yes – You have isolated the problem to the drive enclosure port. Replace the expansion module.
No – Proceed to the next step.
8.
Replace the cable with a known good cable, ensuring the cable is attached to the original ports used by the previous
cable.
Is the host link status LED on?
Yes – Replace the original cable. The fault has been isolated.
No – It is likely that the controller module must be replaced.
Isolating Remote Snap replication faults
Remote Snap replication is a licensed disaster-recovery feature that performs asynchronous replication of block-level
data from a volume in a primary storage system to a volume in a secondary system. Remote Snap creates an internal
snapshot of the primary volume, and copies changes to the data since the last replication to the secondary system via
iSCSI or FC links. The primary volume exists in a primary pool in the primary storage system. Replication can be
completed using either the SMU or CLI. See
“Connecting two storage systems to replicate volumes” (page 31)
for host
connection information concerning Remote Snap.