3. Check the Cache Status LED to verify that the controller cached data is flushed to the disk drives.
l
Solid – Cache contains data yet to be written to the disk.
l
Blinking – Cache data is being written to nonvolatile memory.
l
Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor.
l
Off – Cache is clean (no unwritten data).
4. Reseat the expansion cable, and inspect it for damage.
Is the expansion port status LED on?
l
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.
l
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 isolates the problem to the expansion cable or to the controller module expansion port.
Is the expansion port status LED on?
l
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 port. Replace the controller module.
l
No – Proceed to the next step.
6. Verify that you have moved 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?
l
Yes – You have isolated the problem to the drive enclosure port. Replace the expansion module.
l
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?
l
Yes – Replace the original cable. The fault has been isolated.
l
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" on page
for host
connection information concerning Remote Snap.
Replication setup and verification
After storage systems and hosts are cabled for replication, you can use the SMU to prepare to use the Remote Snap
feature. Optionally, you can use the CLI to access the Remote Snap feature.
NOTE Refer to the following manuals for more information about replication setup:
l
See
HPE MSA Remote Snap Software Technical white paper
for replication best practices.
l
See
HPE MSA 1060/2060/2062 Storage Management Guide
for procedures to setup and manage replications.
l
See
HPE MSA 1060/2060/2062 CLI Reference Guide
for replication commands and syntax.
l
See
HPE MSA Event Descriptions Reference Guide
for replication event reporting.
58
Chapter 7
Troubleshooting