Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerVault ME4 Series Storage System Deployment Guide

Host-side connection troubleshooting featuring CNC ports

The following procedure applies to controller enclosures with small form factor pluggable (SFP+) transceiver connectors in 8/16 Gb/s FC or 10 GbE iSCSI host interface ports.

In this procedure, SFP+ transceiver and host cable is used to refer to any qualified SFP+ transceiver supporting CNC ports used for I/O or replication.
NOTE:When experiencing difficulty diagnosing performance problems, consider swapping out one SFP+ transceiver at a time to see if performance improves.
  1. Stop all I/O to the storage system. See “Stopping I/O” in the Dell PowerVault ME4 Series Storage System Owner’s Manual.
  2. Check the host link status/link activity LED.
    If there is activity, stop 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 in the controller module.
    • 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. Remove the SFP+ transceiver and host cable and inspect for damage.
  5. Reseat the SFP+ transceiver and host cable.

    Is the host link status/link activity LED on?

    • Yes – Monitor the status to ensure that 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.
  6. Move the SFP+ transceiver and host cable to a port with a known good link status.

    This step isolates the problem to the external data path (SFP+ transceiver, host cable, and host-side devices) or to the controller module port.

    Is the host link status/link activity LED on?

    • Yes – You now know that the SFP+ transceiver, host cable, and host-side devices are functioning properly. Return the cable to the original port. If the link status LED remains off, you have isolated the fault to the controller module port. Replace the controller module.
    • No – Proceed to the next step.
  7. Swap the SFP+ transceiver with the known good one.

    Is the host link status/link activity LED on?

    • Yes – You have isolated the fault to the SFP+ transceiver. Replace the SFP+ transceiver.
    • No – Proceed to the next step.
  8. Reinsert the original SFP+ transceiver and swap the cable with a known good one.

    Is the host link status/link activity LED on?

    • Yes – You have isolated the fault to the cable. Replace the cable.
    • No – Proceed to the next step.
  9. Verify that the switch, if any, is operating properly. If possible, test with another port.
  10. Verify that the HBA is fully seated, and that the PCI slot is powered on and operational.
  11. Replace the HBA with a known good HBA, or move the host side cable and SFP+ transceiver to a known good HBA.

    Is the host link status/link activity LED on?

    • Yes – You have isolated the fault to the HBA. Replace the HBA.
    • No – It is likely that the controller module needs to be replaced.
  12. Move the cable and SFP+ transceiver back to its original port.

    Is the host link status/link activity LED on?

    • Yes – Monitor the connection for a period of time. It may be an intermittent problem, which can occur with damaged SFP+ transceivers, cables, and HBAs.
    • No – The controller module port has failed. Replace the controller module.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\