Cisco MDS 9000 Family System Messages Reference (OL-15956-01, April 20078)

Send documentation comments to [e-mail]
2-384
Cisco MDS 9000 Family System Messages Reference
OL-15956-01
Chapter 2 System Messages and Recovery Procedures for the Cisco MDS 9000 Family
Error Message SYSMGR-3-PARTIAL_CFGWRITE_FAILED: Partial configuration copy failed
(error-id [hex]).
Explanation The requested configuration copy has failed. The error message shows the error ID
representing the failure reason.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-PARTIAL_CFGWRITE_VER_MISMATCH: Startup-config version not
same as current software version.
Explanation Startup configuration version not same as current software version.
Recommended Action Enter the copy running startup CLI command or use a similar Fabric
Manager/Device Manager procedure, and try again.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-3-RTDBCTRL_SRVTIMEOUT: Service [chars] failed to respond back
to System Manager in the specified timeout period.
Explanation A required service has failed to send a response after receiving a request for the fabric
switch upgrade.
Recommended Action If you purchased Cisco support through a Cisco reseller, contact the reseller
directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SYSMGR-3-RTDBCTRL_SRVTIMEOUT: Service [chars] failed to respond to the
request to return its runtime database in the timeout period.
Explanation
A required service failed to save the runtime database after a request to stop
communication. Saving of the runtime database failed.
Recommended Action If you purchased Cisco support through a Cisco reseller, contact the reseller
directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-3-SERVICE_CRASHED: Service "[chars]" (PID [dec]) hasn't caught
signal [dec][chars]
Explanation
A service has terminated its execution abnormally. The service might be restarted,
depending on the High Availability policies implemented for the service.
Recommended Action Use the show process CLI command to verify that the service has been
restarted.
Introduced Cisco MDS SAN-OS Release 1.0(2a).