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

Send documentation comments to [e-mail]
2-377
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-2-SAVE_RUNTIME_DB_FAILED: Saving of runtime database for
fabric switch upgrade failed (error-id [hex]).
Explanation This message indicates that the runtime database could not be saved 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-2-SHUTDOWN_FAILURE: Unable to set signal handler for graceful
shutdown: [chars] (error-id [hex]).
Explanation Graceful shutdown has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-SHUTDOWN_REJECT: The System Manager is busy saving the
configuration. Please try again later.
Explanation Shutdown was rejected because the system manager is busy.
Recommended Action Retry the graceful shutdown.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-SIGKILL_FAILURE: Service "[chars]" failure to respond to
SIGKILL causing supervisor to reset.
Explanation
Resetting the supervisor because service failed to respond to SIGKILL sent to it by
system manager.
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 1.3(1).
Error Message SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up.
Explanation The standby supervisor does not complete its boot procedure (that is, it does not reach
the login prompt on the local console) three to six minutes after the loader has been loaded by the
BIOS. This is usually caused by boot variables not properly set for the standby supervisor. This can
also be caused by a user intentionally interrupting the boot procedure at the loader prompt (by means
of pressing ESC).
Recommended Action Connect to the local console of the standby supervisor. If the supervisor is at
the loader prompt, try to use the boot command to continue the boot procedure. Otherwise, issue a
reload command for the standby supervisor from a MDS shell session on the active supervisor,
specifying the force-dnld option. Once the standby is online, fix the problem by setting the boot
variables appropriately.