556: A duplicate WWNN has been detected.

Explanation

The node has detected another device that has the same World Wide Node Name (WWNN) on the Fibre Channel network. A WWNN is 16 hexadecimal digits long. For the Lenovo Storage V series system, the first 11 digits are always 50050768020. The last 5 digits of the WWNN are given in the additional data of the error. The Fibre Channel ports of the node are disabled to prevent disruption of the Fibre Channel network. One or both nodes with the same WWNN can show the error. Because of the way WWNNs are allocated, a device with a duplicate WWNN is normally another Lenovo Storage V series node.

Explanation

The node has detected another device that has the same World Wide Node Name (WWNN) on the Fibre Channel network. A WWNN is 16 hexadecimal digits long. For a cluster, the first 11 digits are always 50050768010. The last 5 digits of the WWNN are given in the additional data of the error and appear on the front panel displays. The Fibre Channel ports of the node are disabled to prevent disruption of the Fibre Channel network. One or both nodes with the same WWNN can show the error. Because of the way WWNNs are allocated, a device with a duplicate WWNN is normally another cluster node.

User Response

  1. Find the Lenovo Storage V series node with the same WWNN as the node reporting the error. The WWNN for a Lenovo Storage V series node can be found from the node Vital Product Data (VPD) or from the node details shown by the service assistant. The node with the duplicate WWNN need not be part of the same cluster as the node reporting the error; it could be remote from the node reporting the error on a part of the fabric connected through an inter-switch link. The two nodes within a control enclosure must have different WWNNs. The WWNN of the node is stored within the enclosure chassis, so the duplication is most likely caused by the replacement of a control enclosure chassis.
  2. If a Lenovo Storage V series node with a duplicate WWNN is found, determine whether it, or the node reporting the error, has the incorrect WWNN. Generally, it is the node that has had its enclosure chassis recently replaced or had its WWNN changed incorrectly. Also, consider how the SAN is zoned when making your decision.
  3. Determine the correct WWNN for the node with the incorrect WWNN. If the enclosure chassis has been replaced as part of a service action, the WWNN for the node should have been written down. If the correct WWNN cannot be determined, contact your support center for assistance.
  4. Use the service assistant to modify the incorrect WWNN. If it is the node showing the error that should be modified, this can safely be done immediately. If it is an active node that should be modified, use caution because the node will restart when the WWNN is changed. If this node is the only operational node in an enclosure, access to the volumes that it is managing will be lost. You should ensure that the host systems are in the correct state before you change the WWNN.
  5. If the node showing the error had the correct WWNN, it can be restarted, using the service assistant, after the node with the duplicate WWNN is updated.
  6. If you are unable to find a Lenovo Storage V series node with the same WWNN as the node showing the error, use the SAN monitoring tools to determine whether there is another device on the SAN with the same WWNN. This device should not be using a WWNN assigned to a Lenovo Storage V series, so you should follow the service procedures for the device to change its WWNN. Once the duplicate has been removed, restart the node.

User Response

Follow troubleshooting procedures to configure the WWNN of the node:
  1. Find the cluster node with the same WWNN as the node reporting the error. The WWNN for a cluster node can be found from the node Vital Product Data (VPD) or from the Node menu on the front panel. The node with the duplicate WWNN need not be part of the same cluster as the node reporting the error; it could be remote from the node reporting the error on a part of the fabric connected through an inter-switch link. The WWNN of the node is stored within the service controller, so the duplication is most likely caused by the replacement of a service controller.
  2. If a cluster node with a duplicate WWNN is found, determine whether it, or the node reporting the error, has the incorrect WWNN. Generally, it is the node that has had its service controller that was recently replaced or had its WWNN changed incorrectly. Also consider how the SAN is zoned when making your decision.
  3. Determine the correct WWNN for the node with the incorrect WWNN. If the service controller has been replaced as part of a service action, the WWNN for the node should have been written down. If the correct WWNN cannot be determined contact your support center for assistance.
  4. Use the front panel menus to modify the incorrect WWNN. If it is the node showing the error that should be modified, this can safely be done immediately. If it is an active node that should be modified, use caution because the node will restart when the WWNN is changed. If this node is the only operational node in an enclosure, access to the volumes that it is managing will be lost. You should ensure that the host systems are in the correct state before you change the WWNN.
  5. If the node showing the error had the correct WWNN, it can be restarted, using the front panel power control button, after the node with the duplicate WWNN is updated.
  6. If you are unable to find a cluster node with the same WWNN as the node showing the error, use the SAN monitoring tools to determine whether there is another device on the SAN with the same WWNN. This device should not be using a WWNN assigned to a cluster, so you should follow the service procedures for the device to change its WWNN. Once the duplicate has been removed, restart the node.