Explanation
The node has detected another device on the fibre-channel network with the same World Wide Node Name (WWNN) as itself. The last five digits of the node's WWNN are shown as the additional data for the error.
The node is not an active member of a cluster. It has disabled its fibre-channel ports to prevent disrupting the operation of the fibre-channel network.
Either just one node, or both nodes, with the same WWNN will show the error.
Due to the way WWNNs are allocated, the device with a duplicate WWNN should be another SAN Volume Controller node.
Only the last five digits of the WWNN are shown on the front panel displays. A WWNN is 16 hexadecimal digits long. For a SAN Volume Controller the first 11 digits are always 50050768010.
Action
- Find the SAN Volume Controller node with the same WWNN as the node reporting the error. The WWNN for a SAN Volume Controller 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 node's WWNN is stored with the service controller, so the duplication is most likely caused by a node that has recently had its service controller replaced and/or its WWNN changed.
- If a SAN Volume Controller node with a duplicate WWNN is found, determine whether it, or the node reporting the error, has the incorrect WWNN. Normally it is the node that has had its service controller replaced, and/or its WWNN changed, that is incorrect. Also consider how the SAN is zoned when making your decision.
- If both nodes with the same WWNN reported the error, the node with the correct WWNN can be restarted using the front panel power control button.
- Determine the correct WWNN for the node with the incorrect WWNN. If the complete node or 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.
- 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 I/O group, access to the VDisks that it is managing will be lost. You should ensure that the host systems are in the correct state before you change the WWNN.
- 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.
- If you are unable to find a SAN Volume Controller node with the same WWNN as the node showing the error, use the SAN monitoring tools to determine if there is another device on the SAN with the same WWNN. This device should not be using a WWNN assigned to a SAN Volume Controller, so you should follow the service procedures for the device to change its WWNN.
Possible Cause-FRUs or other: