Cisco NX-OS System Messages Reference (OL-15994-03, July 2009)

Send document comments to [e-mail]
2-634
Cisco NX-OS System Messages Reference
OL-15994-03
Chapter 2 System Messages and Recovery Procedures
SVC Messages
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MED_ERRS_TOO_HIGH
) Media errors on back-end Managed Disk [chars]
Explanation Media errors on backend managed disk.
Recommended Action 1. Repair the enclosure or disk controller. \ 2. Include the managed disk into
the cluster. 3. Check managed disk status. If all managed disks show a status of online, mark the
error you have just repaired as fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec]
SS_EID_VL_ER_BASE_EVENT_RESOURCE_RAN_OUT ) Software error [chars]
Explanation The error that is logged in the cluster error log indicates a software problem in the
cluster.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Run a
configuration dump and a logged data dump. Save the dump data. 3. Contact the Cisco Technical
Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac. 4. Mark the
error you have just repaired as fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec]
SS_EID_VL_ER_CONTROLLER_CONFIG_INVALID ) Incorrect controller configuration
[chars]
Explanation Incorrect disk controller configuration.
Recommended Action 1. Using service documentation for the disk controller, check that the correct
configuration is set up for the disk controller. See also the IBM TotalStorage SAN Volume
Controller for Cisco MDS 9000: Configuration Guide. 2. Mark the error you have just repaired as
fixed. 3. Start a cluster discovery operation.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec]
SS_EID_VL_ER_DEVICE_PORT_LOGIN_LOSS ) Number of controller logins reduced [chars]
Explanation The number of controller logins has been reduced. One possible cause is that the user
intentionally reconfigured the system.
Recommended Action 1. Check whether the controller has regained connectivity. If it has not, check
the cable connection to the remote-device port. 2. If all logins to a remote-device port have failed
and you cannot solve the problem by changing cables, check the condition of the remote-device port
and the condition of the remote device. 3. Start a cluster discovery operation. 4. Check the status of
the disk controller. If all disk controllers show a good status, mark the error you have just repaired
as fixed.