Feedback
Table Of Contents
System Messages and Recovery Procedures for the Cisco MDS 9000 Family
PORT-SECURITY Messages (Deprecated)
SAN Device Virtualization Messages
System Messages and Recovery Procedures for the Cisco MDS 9000 Family
This chapter lists messages according to the same system facility that produces the messages. Messages are listed in alphabetical order, by system facility. Within each system facility section, messages are listed alphabetically by severity and mnemonics. Each error message is followed by an explanation and a recommended action.
This chapter provides system message information for the following features:
•
PORT-SECURITY Messages (Deprecated)
•
AAA Messages
This section contains the Authentication, Authorization, and Accounting (AAA) messages.
AAA-1
Error Message AAA-1-AAA_SESSION_LIMIT_REJECT: aaa request rejected as maximum aaa sessions are in progress.Explanation The AAA request is rejected because the maximum limit for concurrent AAA sessions was reached.
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).
AAA-2
Error Message AAA-2-AAA_NVRAM_UPGRADE_FAILURE: upgrading of accounting log failed. [chars].Explanation The accounting log could not be upgraded because of a problem with NVRAM. The problem is described in the error message.
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.0(1b).
Error Message AAA-2-AAA_PROGRAM_EXIT: aaa daemon exiting: [chars].Explanation The AAA daemon is exiting.
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).
AAA-3
Error Message AAA-3-AAA_NVRAMFAILURE: nvram failure.Explanation NVRAM is not accessible. The accounting log cannot be stored in NVRAM.
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).
AAA-6
Error Message AAA-6-AAA_ACCOUNTING_MESSAGE: [chars].Explanation Accounting message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
ACL Messages
This section contains the access control list (ACL) messages.
ACL-2
Error Message ACL-2-ACL_HA_FAILURE: Failed to do high availability operation: [chars].Explanation The high availability operation failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_INIT_FAILED: Initialization failed for ACL: [chars], reason: [hex].Explanation Initialization failed for the ACL because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_LINECARD_STATUS: Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].Explanation This message gives the status from the line card.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_MTS_FAILURE: Failed to do MTS operation: [chars].Explanation The messaging and transaction service (MTS) operation failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec].Explanation Setting the messaging and transaction service (MTS) options failed because of the opcode reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].Explanation The persistent storage service (PSS) operation failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].Explanation There was a mismatch in the persistent storage service (PSS) version. The persistent storage service (PSS) service has a different version number than the expected version number.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_RUNTIME_FAILURE: [chars] [dec], Error: [hex].Explanation This error message reports an ACL runtime failure, showing the type of failure and the error reason.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-2-ACL_TCAM_FAILURE: Failed to do TCAM operation: [chars].Explanation The ternary content addressable memory (TCAM) operation failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ACL-4
Error Message ACL-4-ACL_WARNING: [chars] [dec].Explanation This message shows the details of an ACL warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ACL-5
Error Message ACL-5-ACL_ADJ_SHARING_STATUS: Successfully completed "[chars]" on Generation 2 linecards.Explanation The command completed successfully on the Generation 2 line cards.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
ACL-6
Error Message ACL-6-ACL_DIAG_EVENT_STATUS: [chars] [hex].Explanation This message reports the ACL System Health status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_E_PORT_EVENT_STATUS: [chars] [chars].Explanation This message reports the access control list E port or TE port event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_FCC_EVENT_STATUS: [chars] [chars].Explanation This message reports the ACL Fibre Channel Congestion Control (FCC) event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_LINECARD_EVENT_STATUS: [chars] [hex].Explanation This message reports the ACL line card event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_MCAST_EVENT_STATUS: [chars] [chars].Explanation This message reports the ACL multicast event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_NX_PORT_EVENT_STATUS: [chars] [chars].Explanation This message reports the ACL N port or NL port event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_PORT_MODE_EVENT_STATUS: [chars] [chars].Explanation This message reports the ACL port mode event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_RUNTIME_STATUS: [chars] [dec].Explanation This message reports the ACL runtime status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_SPAN_DEST_CONFIG_STATUS: [chars] [chars].Explanation This message reports the ACL SPAN destination configuration event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_SPAN_SRC_CONFIG_STATUS: [chars] [chars].Explanation This message reports the ACL SPAN source configuration event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_STATUS: ACL Status: [chars].Explanation This message reports the ACL status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACL-6-ACL_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].Explanation This message reports the ACL update SSRAM for QoS event status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ACLTCAM Messages
This section contains the access control list ternary content addressable memory (ACLTCAM) messages.
ACLTCAM-2
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_READ_FROM_DRIVER_FAILED: [chars] [dec], Error: [hex].Explanation The system is unable to read the configuration from the forwarding engine ASIC driver.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_WRITE_TO_DRIVER_FAILED: [chars] [dec], Error: [hex].Explanation Unable to write configuration to forwarding engine ASIC driver for the reasons shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_DATABASE: Database found inconsistent.Explanation The database is in an inconsistent state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_TCAM_CONTENTS: TCAM contents found inconsistent.Explanation The TCAM contents are inconsistent.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_INIT_FAILED: Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM.Explanation The initialization failed for forwarding engine ASIC associated with the TCAM.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_INIT_REGIONS_FAILED: Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM, [chars] Region.Explanation Initialization of regions failed for the forwarding engine ASIC associated with the TCAM, for the region shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_MALLOC_FAILURE: Memory allocation failed for size [dec].Explanation Memory allocation failed for number of bytes shown in the error message.
Recommended Action Restart the process.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ACLTCAM-2-ACL_TCAM_MTS_FAILURE: MTS operation failed: [chars].Explanation The messaging and transaction service (MTS) operation failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_MTS_REGISTRATION_FAILED: MTS registration failed for opCode: [dec].Explanation The messaging and transaction service (MTS) registration failed for the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_NO_ROUTE: ACLTCAM failed to get route for VSAN: [dec], Rewrite: [chars] DID: [chars] DID MASK: [chars], error: [hex].Explanation The ACLTCAM process experienced a failure while getting a route for the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message ACLTCAM-2-ACL_TCAM_NO_TCAM_LEFT: ACLTCAM resource exhausted for interface : [chars].Explanation The access control list TCAM hardware resource is full.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_READ_FAILED: [chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).Explanation A read from the TCAM failed. The error message shows the ASIC and TCAM associated with this failure and shows the TCAM address, number of entries, and the error that occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: [chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).Explanation A write to the TCAM failed. The error message shows the ASIC and TCAM associated with this failure and shows the TCAM address, number of entries, and the error that occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-ACL_TCAM_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].Explanation Failed to do a persistent storage service (PSS) operation because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ACLTCAM-2-PSS_OPEN_FAILED: PSS open failed - [hex].Explanation A persistent database handle could not be obtained for ACL TCAM. The error message shows the error code associated with this problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ACLTCAM-2-RECONS_FAILED: Reconstruction of TCAM contents failed during upgrade - [hex].Explanation During a nondisruptive upgrade, the ACL TCAM contents were not properly reconstructed. The error message shows the error code associated with this problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ACLTCAM-3
Error Message ACLTCAM-3-REGISTER_FAILED: Could not register to MTS opcode [chars] - error [hex].Explanation The ACLTCAM process could not register to the notifications shown in the error message. The error message also shows the error code for this problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ACLTCAM-6
Error Message ACLTCAM-6-ACL_TCAM_STATUS: Status: [chars].Explanation This message reports the ACL TCAM status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
ASCII-CFG Messages
This section contains the ASCII configuration (ASCII-CFG) messages.
ASCII-CFG-2
Error Message ASCII-CFG-2-ACFG_CONFIGURATION_APPLY_ERROR: Error encountered while Ascii configuration was being applied.Explanation At least one command failed while ASCII configuration was being applied.
Recommended Action Use the show startup-config log CLI command to view details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ASCII-CFG-2-ACFG_LIB_INVOKE_ERR: Ascii config library invocation error: [chars].Explanation An error occurred while the library function was being invoked to display the ASCII configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
BIOS_DAEMON Messages
This section contains the BIOS daemon (BIOS_DAEMON) messages.
BIOS_DAEMON-2
Error Message BIOS_DAEMON-2-BIOS_DAEMON_PRI_BOOT_FAIL: Primary BIOS is corrupted or un-bootable.Explanation The primary BIOS is corrupted or unbootable.
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.0(1).
Error Message BIOS_DAEMON-2-BIOS_DAEMON_SUP_ERROR: BIOS Sector ([dec]) is write protectedExplanation The BIOS on the module is write protected.
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.0(1b).
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_ERROR: BIOS Sector ([dec]) is write protectedExplanation The BIOS on the module is write protected.
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.0(1b).
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_PRI_BOOT_FAIL: Primary BIOS is corrupted or un-bootable.Explanation The primary BIOS on a module is corrupted.
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.0(1).
BOOTVAR Messages
This section contains the boot variable (BOOTVAR) messages.
BOOTVAR-2
Error Message BOOTVAR-2-ALLOC_MEMORY: Memory allocation failed.Explanation The service failed to allocate memory.
Recommended Action Check to see if the switch is low on memory and reset the switch if it is low.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-2-AUTOSYNC_FAILED: Image autosync failed. Reason: [chars] ([hex]).Explanation The image synchronization has failed.
Recommended Action Ensure that there is enough space on the flash. Verify the system high availability status.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-2-CONFIG_ERROR: Failed to update boot configuration.Explanation An error has occurred during the update of the boot configuration files.
Recommended Action Ensure that there is enough space on the flash. Enter the show boot CLI command to check the configured image names, and enter show loader internal configuration to compare them with the current bootloader configuration. If they are not coherent, enter the write erase CLI command and try to save the configuration again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-2-IMAGE_NOT_COMPATIBLE: Warning: image [chars] is not compatible with the current platform in Sup [dec].Explanation The input image name is not compatible with the current platform.
Recommended Action Make sure a correct image is specified before rebooting the system.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
BOOTVAR-3
Error Message BOOTVAR-3-AUTOCOPY_FAILED: Autocopy of file [chars] to standby failed, error=[hex].Explanation The automatic copy feature failed to copy the image shown to the standby module.
Recommended Action Check the error ID for the specified reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-3-AUTOCOPY_FAILED_STANDBY_FULL: Autocopy of file [chars] to standby failed due to not enough disk space on standby.Explanation There is not enough disk space on the standby supervisor for the file to be copied.
Recommended Action Clear space on the standby supervisor.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message BOOTVAR-3-INIT_FAILED: Initialization failed: Component [chars].Explanation The service failed to start. The failure occurred during initialization of the component shown in the error message.
Explanation Enter the show process CLI command to check the status of the other processes. Check the component shown in the error message. You can alternatively use Fabric Manager and Device Manager instead of the command line interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-3-LOAD_VERIFY_LIB_FAILED: Fetching library [chars] failed, reason=[chars].Explanation The boot variable verification library specified failed to load.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-3-MODULE_LOCK_FAIL: Unable to get module lock, please don't reload <error-id:[hex]Explanation Unable to acquire modlock to prevent user to reload during auto-sync.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message BOOTVAR-3-NEIGHBOR_REJECT_AUTOCOPY: auto-copy failed - not supported by neighbor supervisor.Explanation The standby supervisor does not support automatic copy. This automatic copy attempt has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-3-VERIFY_FAILED: Image [chars] for bootvar [chars] verification failed, reason=[chars].Explanation The image set for this boot variable has failed the verification process. This is just a warning.
Recommended Action Check the reason shown in the error message to determine what action to take.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
BOOTVAR-5
Error Message BOOTVAR-5-AUTOCOPY_SUCCEED: auto-copy of file [chars] to standby supervisor succeed.Explanation Automatic copy of the file succeeded. Image integrity was verified by the standby supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-5-AUTOCOPY_VERIFY_SEND_FAILED: Unable to ask standby to verify file [chars], error = [hex].Explanation After copying the image to the standby supervisor, the active supervisor failed to verify the integrity of that image on the standby supervisor.
Recommended Action Turn auto-copy off and back on.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-5-AUTOSYNC_DONE: Image autosync done.Explanation The image synchronization was done successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-5-AUTOSYNC_REBOOT: Rebooting standby after successful autosync.Explanation Image automatic synchronization was successful. The system is resetting the standby supervisor to load the new image.
Recommended Action Verify that the standby supervisor reloads correctly.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-5-AUTOSYNC_START: Starting image autosync. Please wait until completion.Explanation The standby supervisor has requested a synchronization of the current image.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-5-IMAGE_NOTEXISTS: Warning: image [chars] doesn't exist on sup[dec].Explanation The input image name does not exist on the specified supervisor.
Recommended Action Check whether the input image name you entered exists and make sure that you have the image on the flash before reboot.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by opposing supervisor, starting...Explanation The standby supervisor supports automatic copy. Automatic copy has started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
BOOTVAR-6
Error Message BOOTVAR-6-ALREADY_IN_SYNC: Image already in sync.Explanation No need to update the image on the standby supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-6-CONFIG_UPDATED: Boot configuration updated.Explanation The boot-loader configuration files have been successfully updated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message BOOTVAR-6-STARTING: Boot configuration initialized.Explanation The service has successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
CALLHOME Messages
This section contains the Call Home (CALLHOME) messages.
CALLHOME-2
Error Message CALLHOME-2-EVENT: [chars].Explanation A Call Home event occurred.
Recommended Action If you have configured your e-mail address to receive Call Home notifications, check your e-mail for more details about this Call Home event. If Call Home was not enabled, use either CLI commands or Cisco Fabric Manager procedures to get more information about the error.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CALLHOME-2-PROGRAM_EXIT: callhome process ending: [chars].Explanation Call Home process is exiting because of the reason shown in the error message.
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.2(2a).
CALLHOME-3
Error Message CALLHOME-3-CALLHOME_CFS_MERGE_OPERATION_FAILED: [chars].Explanation A Call Home merge operation failed.
Recommended Action Check the reason for the failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CALLHOME-3-CALLHOME_CFS_OPERATION_FAILED: [chars] : [chars].Explanation The Call Home operation using Cisco Fabric Services (CFS) failed because of the reason shown in the error message.
Recommended Action Check the reason for the failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CALLHOME-3-CALLHOME_MAX_ALERT_MSG: [chars].Explanation A Call Home alert occurred.
Recommended Action Check the reason listed for the Call Home message and rectify the problem.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CALLHOME-3-EVENT_PROCESS_ERROR: error in processing callhome event [chars] reason:[chars].Explanation An error occurred in processing the Call Home event because of the reason shown in the error message.
Recommended Action Verify your Call Home configuration for proper configuration. Verify the SMTP server address, verify e-mail addresses for destination profiles, and enable status of Call Home. Enter the show callhome CLI command to display the configuration. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.3(3).
Error Message CALLHOME-3-MESSAGE_SIZE_EXCEED: message size for callhome alert:[chars] exceeds maximum limit for destination profile:[chars].Explanation The message size for the Call Home alert exceeds the maximum limit for the destination profile shown in the error message.
Recommended Action Verify the maximum message size for the destination profile under question. Increase it, if possible, to match the maximum limit allowed by your e-mail destinations.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CALLHOME-6
Error Message CALLHOME-6-NONCRIT_EVENT: [chars].Explanation A noncritical Call Home event occurred.
Recommended Action If you have configured your e-mail address to receive Call Home notifications, check your e-mail for more details about this Call Home event. If Call Home was not enabled, use either CLI commands or Fabric Manager procedures to get more information about the error.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CDP Messages
This section contains the Cisco Discovery Protocol (CDP) messages.
CDP-2
Error Message CDP-2-INITFAIL: CDP Daemon Initialization failed: [chars].Explanation The Cisco Discovery Protocol daemon initialization failed because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CDP-3
Error Message CDP-3-ALLOCFAIL: Heap Memory allocation failed: [chars].Explanation The Cisco Discovery Protocol daemon is out of dynamic memory. The error message shows the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-GENERROR: [chars].Explanation The Cisco Discovery Protocol daemon encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-MCASTBINDFAIL: Failed to bind for CDP multicast address on interface [hex] - [chars].Explanation An attempt to register for packets destined to the Cisco Discovery Protocol multicast address failed. The error message identifies the interface and the reason for the failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-MTSERROR: [chars].Explanation The Cisco Discovery Protocol daemon encountered a messaging and transaction service (MTS) error. The error message shows the context where the error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-PKTRECVFAIL: Failed to receive packet - [chars].Explanation Failed to receive a packet because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-PKTSENDFAIL: Failed to send packet, interface [hex] - [chars].Explanation Failed to send a packet. The error message identifies the interface and the reason for this failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-PSSERROR: [chars].Explanation The Cisco Discovery Protocol daemon encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-SOCKBINDFAIL: Failed to bind to raw socket, interface [hex] - [chars].Explanation The Cisco Discovery Protocol failed to bind to a raw socket. The error message identifies the interface and the reason for this failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-3-SOCKOPENFAIL: Failed to open socket for receiving raw 802_2 packets - [chars].Explanation An attempt to open a socket for receiving raw 802.2 packets failed due to the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CDP-6
Error Message CDP-6-CDPDUP: CDP Daemon Up.Explanation The Cisco Discovery Protocol daemon was created successfully and is up and running.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-6-CDPEXIT: CDP daemon shutting down gracefully.Explanation The Cisco Discovery Protocol daemon is shutting down gracefully.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-6-PORTDISABLE: CDP disabled on port [chars].Explanation The Cisco Discovery Protocol was disabled on a port. The error message shows the Interface-ID string that identifies the port.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-6-PORTDOWN: A CDP enabled port [chars] went down.Explanation A Cisco Discovery Protocol enabled port became unoperational. The error message shows the Interface-ID string that identifies the port.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-6-PORTENABLE: CDP enabled on port [chars].Explanation The Cisco Discovery Protocol was enabled on a port. The error message shows the Interface-ID string that identifies the port.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CDP-6-PORTUP: A CDP enabled port [chars] came up.Explanation A Cisco Discovery Protocol enabled port became operational. The error message shows the Interface-ID string that identifies the port.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CERT ENROLL Messages
Error Message CERT_ENROLL-2-CERT_EN_PROGRAM_EXIT: cert_enroll daemon exiting: [chars].Explanation The process is responsible for digital certificate enrollment exited.
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.0(1).
Error Message CERT_ENROLL-3-CERT_EN_ERROR_MESSAGE: [chars].Explanation The digital certificate enrollment process generated an error message.
Recommended Action Review the error in the message to determine the next steps.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CERT_ENROLL-3-CERT_EN_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode : [chars].Explanation FIPS mode initialization error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message CERT_ENROLL-6-CERT_EN_MESSAGE: [chars].Explanation The digital certificate enrollment process generated an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
CFS Messages
This section contains the Cisco Fabric Services (CFS) messages.
CFS-2
Error Message CFS-2-MTS_REJECT: Verification failed reject MTS message SAP [dec]:RR-token [hex].Explanation This MTS message could have been posted by the previous active running pre 3.x; MTS structure has changed since then hence ignore the MTS message, Source SAP [dec]; RR-token [hex].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message CFS-2-CFS_REJECT: CFS reject: [chars]: Switch WWN [chars], reason [chars].Explanation When Cisco Fabric Service (CFS) receives a malformed CFS packet from a switch with WWN and IP address shown in the error message, then CFS rejects the packet.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-2-EXITING: Exit reason: [chars].Explanation The Cisco Fabric Services process has exited because of the error shown in the error message. The process will be restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-2-GENERAL_ERROR: [chars].Explanation The Cisco Fabric Services process has encountered a critical error. The description of error is shown in the error message.
Recommended Action Refer to the listed error and take action as required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-2-INITFAIL: CFS Service Init failed: [chars].Explanation The Cisco Fabric Services initialization failed. The error message explains the reason for the failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-2-LOCK_FAILED: lock failed for sap [dec] due to internal error.Explanation Lock failed because the unrestricted and uncoordinated count is not zero for an application with the service access point (SAP) shown in error message.
Recommended Action To recover from this state, use the cfs internal decrement-unrestricted <app-sap> CLI command.
Introduced Cisco MDS SAN-OS Release 3.0(2a).
Error Message CFS-2-MALLOC_ERROR: Size [dec] bytes.Explanation The Cisco Fabric Services could not allocate memory.
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.0(1b).
Error Message CFS-2-PSS_ERROR: [chars]: PSS ret. val=[dec].Explanation The Cisco Fabric Services encountered an error while operating on a persistent storage database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
CFS-3
Error Message CFS-3-ALLOCFAIL: Heap Memory allocation failed: [chars].Explanation The Cisco Fabric Services process is out of dynamic memory. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-FIPS_TEST_FAILED: FIPS compliance test failed.Explanation A FIPS compliance test failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message CFS-3-MERGE_FAILED: Merge failed for app [chars], local switch wwn [chars],ip [chars], remote switch wwn [chars], ip [chars].Explanation The Cisco Fabric Services has detected a merge failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-CFS_PSS_CORRUPTED: [chars] PSS found corrupted.Explanation The Cisco Fabric Services detected corruption in one of its persistent information databases. The database will be recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-DBERROR: [chars].Explanation The Cisco Fabric Services encountered a database error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-FAILURE_RESPONSE: [chars] [hex].Explanation The Cisco Fabric Services failed to get a response. The error message shows the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-GENERROR: [chars].Explanation The Cisco Fabric Services encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-LICERR: [chars].Explanation The Cisco Fabric Services failed to get a license.
Recommended Action Install a license.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-MTSERROR: [chars].Explanation The Cisco Fabric Services encountered a messaging and transaction service (MTS) error. The error message specifies the context where the error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-PSSERROR: [chars].Explanation The Cisco Fabric Services encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-TIMEOUT_ERROR: [chars] [hex].Explanation The Cisco Fabric Services encountered a timeout. The error message shows the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec].Explanation The Cisco Fabric Services received an unknown message from a node. This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
CFS-4
Error Message CFS-4-LICEXP: [chars].Explanation The Cisco Fabric Services license is going to expire. The error message shows the expiration time.
Recommended Action Install a license.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec].Explanation There was a version mismatch between the Cisco Fabric Services and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
CFS-6
Error Message CFS-6-BECAME_ACTIVE: Became ACTIVE from standby mode.Explanation The Cisco Fabric Services on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-BECAME_STDBY: Became STANDBY from active mode.Explanation The Cisco Fabric Services changed to standby mode from active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-EXCESSIVE_DELAY: [chars].Explanation A processing event took an excessive amount of time. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars].Explanation The Cisco Fabric Services failed to send a heartbeat message to the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-GENERAL_EVENT: [chars].Explanation The Cisco Fabric Services generated an event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-LOGICAL_DISTRIBUTION_INFO: vsan [dec], source wwn [chars], ip [chars] app-id [dec], session-id [dec], user [chars], [chars].Explanation This is an information message that is logged during different stages for coordinated distribution of an application with the application ID shown in the error message (logical scope). Different stages are LOCK_ACQUIRED, LOCK_RELEASED, LOCK_CLEAR, and COMMIT which are shown at the end of the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message CFS-6-PHYSICAL_DISTRIBUTION_INFO: source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], [chars].Explanation This is an information message that is logged during different stages for coordinated distribution of an application with the application ID shown in the error message (physical scope). Different stages are LOCK_ACQUIRED, LOCK_RELEASED, LOCK_CLEAR, and COMMIT which are shown at the end of the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message CFS-6-PSS_CREATED: [chars] PSS Created.Explanation A persistent information database for the Cisco Fabric Services has been recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-PSS_DESTROYED: [chars] PSS Destroyed.Explanation A persistent information database for Cisco Fabric Services has been deleted and will be recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-REGION_CTX_REMOVED: Region info is deleted for [chars].Explanation [chars] is in logical scope. Regions are supported only physical scope applications.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message CFS-6-SERVICE_UP: Initialized [chars].Explanation The Cisco Fabric Services process is up and ready to accept client requests. The process was initialized in the mode shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-SRVCREATED: CFS Service created.Explanation The Cisco Fabric Services process was created successfully and is up and running.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-SRVEXIT: CFS Service shutting down gracefully.Explanation The Cisco Fabric Services process is shutting down gracefully.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message CFS-6-SWITCHOVER: Switching Over to other Sup.Explanation The Cisco Fabric Services successfully switched over to the standby supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
CIMSRVPROV Messages
This section contains the Common Information Model (CIM) server (CIMSRVPROV) messages.
CIMSRVPROV-2
Error Message CIMSRVPROV-2-CIM_SYSLOG_EXIT: Message:[chars] errcode:[dec].Explanation The CIM server exited because of a critical error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-2-CIM_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec].Explanation A persistent storage service (PSS) snapshot error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-2-CIM_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec].Explanation The CIM server experienced a debug infrastructure error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
CIMSRVPROV-3
Error Message CIMSRVPROV-3-CIM_SYSLOG_COPY_CONFIG_ERR: Message:[chars] URI:[chars] errcode:[dec].Explanation The CIM server experienced a copy running startup error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-3-CIM_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec].Explanation The CIM server experienced a file handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-3-CIM_SYSLOG_MTS_ERR: message [chars].Explanation The CIM server experienced a messaging and transaction service (MTS) message handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-3-CIM_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec].Explanation The CIM server experienced a persistent storage service (PSS) handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
CIMSRVPROV-6
Error Message CIMSRVPROV-6-LOG_CIM_CERTIFICATE_CLEARED: Cleared certificate [chars].Explanation The CIM server experienced a cleared a certificate named in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message CIMSRVPROV-6-LOG_CIM_CERTIFICATE_INSTALLED: Installed certificate [chars].Explanation The CIM server installed a certificate named in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
CLOUD Messages
CLOUD-2
Error Message CLOUD-2-PROGRAM_EXIT: cloud-discovery process ending: [chars].Explanation Cloud-discovery process is exiting for the reason stated.
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.0(1).
CLOUD-3
Error Message CLOUD-3-CLOUD_CFS_MERGE_OPERATION_FAILED: [chars].Explanation CFS merge failed.
Recommended Action Check the message for the reason for failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CLOUD-3-CLOUD_CFS_OPERATION_FAILED: [chars] : [chars].Explanation CFS operation failed.
Recommended Action Check the message for the reason for failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CLOUD-3-CLOUD_FEATURE_MANAGER_ERROR: [chars] : [chars].Explanation iSLB manager experienced an error.
Recommended Action Check the message for the reason for failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CLOUD-3-CLOUD_PSS_OPERATION_FAILED: [chars] : [chars].Explanation PSS operation failed
Recommended Action Check the message for the reason for failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 3.0(1).
CLOUD-6
Error Message CLOUD-6-CLOUD_DISCOVERY_DONE: discovery over.Explanation Cloud-discovery started.
Recommended Action Check the cloud membership.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CLOUD-6-CLOUD_DISCOVERY_STARTED: [chars] discovery started.Explanation Cloud-discovery started.
Get more information using the cloud-discovery status CLI command. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 3.0(1).
CORE-DMON Messages
This section contains the core dump daemon (CORE-DMON) messages.
CORE-DMON-2
Error Message CORE-DMON-2-MODULE_COREDUMP_DONE: kernel coredump completed on module:[dec].Explanation Kernel core dump finished on the module shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message CORE-DMON-2-MODULE_COREDUMP_STARTED: kernel coredump started on module:[dec].Explanation Kernel core dump started on the module shown in the error message. Another system message will be generated when this task completes.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
CREDIT MON Messages
Error Message CREDITMON-SLOT#-2-SYSERR_CREDITMON_APP_EXITED: [chars].Explanation Credit Monitor application exited.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message CREDITMON-SLOT#-2-SYSERR_CREDITMON_MTS_INIT_ERR: [chars].Explanation Credit Monitor error binding to MTS.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
DEBUGPROXY Messages
This section contains the debug proxy (DEBUGPROXY) messages.
DEBUGPROXY-6
Error Message DEBUGPROXY-6-ILC_DEBUG_PROXY_COMMON: ilc debug proxy [chars] [dec].Explanation General intelligent line card (ILC) debug proxy information.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message DEBUGPROXY-6-SSM_DEBUG_PROXY_COMMON: SSM debug proxy [chars] [dec].Explanation General Storage Services Module (SSM) debug proxy information.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
DEVICE-ALIAS Messages
This section contains the device alias (DEVICE-ALIAS) messages.
DEVICE-ALIAS-2
Error Message DEVICE-ALIAS-2-ALLOC_FAILED: Memory allocation failed for size:[dec] type:[dec].Explanation Memory allocation failed for the size and type of memory shown in the error message.
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.0(1b).
Error Message DEVICE-ALIAS-2-INIT_FAILED: [chars].Explanation An error occurred during initialization because of the reason shown in the error message.
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.0(1b).
DEVICE-ALIAS-3
Error Message DEVICE-ALIAS-3-CFS_OPER_FAILED: [chars].Explanation An error occurred while performing a Cisco Fabric Services (CFS) operation. The error message indicates the CFS operation and the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-CLEAR_FAILED: [chars].Explanation An error occurred while clearing the session. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-COMMIT_FAILED: [chars].Explanation An error occurred while committing the database. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-COMMIT_REJECTED: [chars].Explanation Commit request received from a remote switch was rejected. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-LOCK_FAILED: [chars].Explanation An error occurred while acquiring the lock. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-LOCK_REJECTED: [chars].Explanation Lock request received from a remote switch is rejected. The error message indicates the reason for the failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_FAILED: [chars].Explanation An error occurred while activating the merged database. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_REJECTED: [chars].Explanation An activation request received from a remote switch is rejected. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-MERGE_FAILED: [chars].Explanation An error occurred during a merge operation. The error message indicates the reason for failure.
Recommended Action Compare the device-alias database with the other switches in the fabric. Resolve any conflicts and commit the changes.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DEVICE-ALIAS-3-MTS_OPER_FAILED: [chars].Explanation An error occurred during a messaging and transaction service (MTS) operation. The error message indicates the messaging and transaction service (MTS) operation and the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-PSS_OPER_FAILED: [chars].Explanation An error occurred during a persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation and the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-UNLOCK_FAILED: [chars].Explanation An error occurred while releasing the lock. The error message indicates the reason for failure.
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.0(1b).
Error Message DEVICE-ALIAS-3-UNLOCK_REJECTED: [chars].Explanation An unlock request received from a remote switch is rejected. The error message indicates the reason for failure.
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.0(1b).
DEVICE-ALIAS-6
Error Message DEVICE-ALIAS-6-CLEAR_FAILED_INFO: [chars].Explanation An error occurred while clearing the session. The error message indicates the additional information regarding failure.
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.0(1b).
Error Message DEVICE-ALIAS-6-COMMIT_FAILED_INFO: [chars].Explanation An error occurred while committing the database. The error message indicates the additional information regarding failure.
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.0(1b).
Error Message DEVICE-ALIAS-6-IMPORT_DEFINITION_CONFLICT: Fcalias [chars] could not be imported due to definition conflict.Explanation The fcalias shown could not be imported because of a definition conflict. Either there is already a device-alias configuration present with the same definition, or another VSAN specified in the import VSAN range has an fcalias with the same definition.
Recommended Action Resolve the conflict and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DEVICE-ALIAS-6-IMPORT_MEMBER_TYPE_CONFLICT: Fcalias [chars] could not be imported due to having unsupported member type.Explanation The fcalias shown in the error message could not be imported because of unsupported member types. The fcalias can be imported only if it has port WWN based members.
Recommended Action Make sure that the fcalias has port WWN based members and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DEVICE-ALIAS-6-IMPORT_NAME_CONFLICT: Fcalias [chars] could not be imported due to name conflict.Explanation The fcalias shown could not be imported because of a name conflict. Either there is already a device-alias configuration present with the same name, or another VSAN specified in the import VSAN range has an fcalias with the same name.
Recommended Action Resolve the conflict and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DEVICE-ALIAS-6-IMPORT_NUM_MEMBERS_CONFLICT: Fcalias [chars] could not be imported due to having unsupported number of members.Explanation The fcalias listed could not be imported because of an unsupported number of members. The fcalias can be imported only if it has exactly one member.
Recommended Action Make sure that the fcalias has exactly one member and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DEVICE-ALIAS-6-LOCK_FAILED_INFO: [chars].Explanation An error occurred while acquiring the lock. The error message indicates the additional information regarding failure.
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.0(1b).
Error Message DEVICE-ALIAS-6-MERGE_ACTIVATION_FAILED_INFO: [chars].Explanation An error occurred while activating the merged database. The error message indicates the additional information regarding failure.
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.0(1b).
Error Message DEVICE-ALIAS-6-UNLOCK_FAILED_INFO: [chars].Explanation An error occurred while releasing the lock.The error message shows additional information regarding failure.
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.0(1b).
DEV_LOG Messages
This section contains the DEV_LOG messages.
DEV_LOG-3
Error Message DEV_LOG-3-ERROR: [chars]Explanation Dev_log_lc encountered an error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
DMM-SLOT# Messages
DMM-SLOT#-5
Error Message DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_SRVR_ZONE: Job Id:%Ld VSAN :[dec] New N-Port FCID :[hex] Server FCID:[hex] are in the same zone. ALERT!!.Explanation A new N port has come up, which is zoned in the same zone as the server.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_STG_ZONE: Job Id:%Ld VSAN :[dec] New N-Port FCID :[hex] Storage FCID:[hex] are in the same zone. ALERT!!.Explanation A new N port has come up, which is zoned in the same zone as the storage.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_ERR_DMM_SRVR_RSCN: Job Id:%Ld Server N-Port pWWN:0x%Lx [chars].Explanation An RSCN event was received for the server associated with a job.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_ERR_DMM_STG_RSCN: Job Id:%Ld N-Port pWWN:0x%Lx Storage:[chars] [chars].Explanation An RSCN event was received for the storage associated with a job.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_COMPLETE: Job Id:%Ld NumSession:[dec].Explanation Event indicating the completion of a data migration job.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR: Job Id:%Ld NumSession:[dec].Explanation Event indicating the suspension of data migration job.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR_LOST_SSM_PEER_CONNECTION: Job Id:%Ld NumSession:[dec].Explanation Event indicating the suspension of data migrationjob because of in IP connectivity to the peer SSM.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_START: Job Id:%Ld NumSession:[dec].Explanation Event indicating the start of a data migration job.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_STOP: Job Id:%Ld NumSession:[dec].Explanation Event indicating that the data migration job was stopped by administrator.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_COMPLETE: Job Id:%Ld NumSession:[dec].Explanation Event indicating the completion of a data migration job verification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_ERROR: Job Id:%Ld NumSession:[dec].Explanation Event indicating the suspension of data migration job verification due to an error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_START: Job Id:%Ld NumSession:[dec].Explanation Event indicating the start of a data migration job verification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_STOP: Job Id:%Ld NumSession:[dec].Explanation Event indicating the suspension of data migration job verification by the user.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
DPP_DEBUG Messages
This section contains the data path processor debug (DPP_DEBUG) messages.
DPP_DEBUG-2
Error Message DPP_DEBUG-2-DPP_CRIT: [DPP[dec]] [chars].Explanation A data path processor generated a critical message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
DPVM Messages
This section contains the dynamic port VSAN membership (DPVM) messages.
DPVM-2
Error Message DPVM-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for [chars].Explanation Memory allocation 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.0(1b).
Error Message DPVM-2-FEATURE_DISABLED: [chars].Explanation The dynamic port VSAN membership feature is unavailable and disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Deprecated Cisco MDS SAN-OS Release 2.0(2b).
Error Message DPVM-2-FEATURE_ENABLED: [chars].Explanation Dynamic port VSAN membership (DPVM) is available and enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Deprecated Cisco MDS SAN-OS Release 2.0(2b).
DPVM-3
Error Message DPVM-3-DB_ERR: [chars].Explanation An error occurred during a dynamic port VSAN membership database operation. The error message indicates the reason for the error.
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.0(1b).
Error Message DPVM-3-DDAS_MODE_INVALID: [chars].Explanation The Distributing Devise Alias Services (DDAS) mode is invalid when you merge two switches that have different device aliases.
Recommended Action Make the DDAS mode consistent across switches.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message DPVM-3-INIT_FAIL: [chars].Explanation An error occurred during dynamic port VSAN membership initialization. The error message indicates the reason for failure.
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.0(1b).
Error Message DPVM-3-MTS_ERR: [chars].Explanation An error occurred in processing a messaging and transaction service (MTS) message. The error message indicates the error that occurred.
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.0(1b).
Error Message DPVM-3-PSS_ERR: [chars].Explanation An error occurred during a dynamic port VSAN membership persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation that caused the error.
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.0(1b).
DPVM-4
Error Message DPVM-4-ACTIVATION_FAIL: [chars].Explanation VSAN membership The activation of dynamic port VSAN membership (DPVM) device mappings failed because of the reason shown in the error message.
Recommended Action Correct the error and reactivate the DPVM database. Enter the dpvm activate CLI command or use a similar procedure with Fabric Manager/Device Manager.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DPVM-4-FEATURE_DISABLED: [chars].Explanation Dynamic port VSAN membership (DPVM) is unavailable and disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(2b).
DPVM-6
Error Message DPVM-6-FEATURE_ENABLED: [chars].Explanation Dynamic port VSAN membership (DPVM) is available and enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(2b).
Error Message DPVM-6-INFO: [chars].Explanation An event occurred that affects the dynamic port VSAN membership. The error message indicates the event.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
DSTATS Messages
This section contains the DSTATS messages.
DSTATS-2
Error Message DSTATS-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex].Explanation DSTATS persistent storage service (PSS) initialization failed because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
DSTATS-3
Error Message DSTATS-3-PSS_CREATE_FAIL: pss create runtime database failed due to error: [hex].Explanation DSTATS failed to create the persistent runtime database using the persistent storage service (PSS) because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [hex].Explanation DSTATS failed to delete the persistent storage service (PSS) runtime entry key because of the reason shown in the error message.
Recommended Action Enter the show flash command or similar Fabric Manager/Device Manager procedure to collect more information. See the PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to error: [hex].Explanation DSTATS failed to set the persistent storage service (PSS) runtime max key because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See the PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to error: [hex].Explanation DSTATS failed to set the persistent storage service (PSS) runtime max value because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: [hex].Explanation DSTATS failed to open the persistent storage service (PSS) runtime database because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to error: [hex].Explanation DSTATS failed to reload the persistent storage service (PSS) runtime database because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to uri:[chars] failed due to error: [hex].Explanation DSTATS failed to snapshot the persistent storage service (PSS) runtime debug to the URI because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] failed due to error: [hex].Explanation DSTATS failed to snapshot the persistent storage service (PSS) runtime to URI because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message DSTATS-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] failed due to error: [hex].Explanation DSTATS failed to store the persistent storage service (PSS) runtime entry key/value pair because of the reason shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
EPP Messages
This section contains the exchange peer parameters (EPP) messages.
EPP-5
Error Message EPP-5-EPP_FAILURE: Interface [chars] EPP Failure.Explanation Trunk protocol failed.
Recommended Action Enter show epp internal event-history err to determine what errors were encountered.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message EPP-5-EPP_LOOPBACK: Interface [chars] is looped back to the same switch.Explanation The interface is looped back to another interface on the same switch.
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ETHPORT Messages
This section contains the Ethernet port (ETHPORT) messages.
ETHPORT-3
Error Message ETHPORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported.Explanation The transceiver is not from an authorized vendor.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to determine which transceiver is being used. Contact customer support for a list of authorized transceiver vendors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ETHPORT-5
Error Message ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down).Explanation The interface has been configured to be administratively down.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to set this interface to administratively up.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change).Explanation FCIP interface temporarily down because of a reconfiguration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel admin down).Explanation This interface belongs to a PortChannel and the PortChannel is configured to be administratively down.
Recommended Action Enter the no shutdown command or use a similar Fabric Manager/Device Manager procedure on the PortChannel that the interface belongs to.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface [chars] is down (Channel membership update in progress).Explanation The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel.
Recommended Action Wait until the PortChannel configuration completes and then try the interface configuration again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to domain id assignment failure).Explanation Isolated due to a failure while assigning a domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is down (Isolation due to invalid fabric reconfiguration).Explanation Invalid fabric reconfiguration received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down (Isolation due to domain manager disabled).Explanation The interface is isolated because the domain manager is disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars] is down (Isolation due to domain manager other side not responding).Explanation Remote end domain manager is not responding.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars] is down (Isolation due to domain other side eport isolated).Explanation Isolating this interface because the remote end is isolated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to domain overlap).Explanation The interface is isolated because of a domain overlap.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ELP failure).Explanation Exchange link parameters (ELP) failed on the interface.
Recommended Action Enter show port internal info and check the status in the ELP failure reason field.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error Disabled - EPP Failure).Explanation Trunk protocol failed.
Recommended Action Enter show port internal event-history msgs to list the trunk protocol exchanges to determine why the trunk protocol failed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled).Explanation The interface encountered an error during configuration.
Recommended Action Collect more information about failed interface using show port internal all interface [char]. In most cases, you can recover using a shutdown followed by a no shutdown
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ESC failure).Explanation Exchange switch parameters (ESC) failed on the interface.
Recommended Action Check the output of show port internal event-history to show the ESC protocol exchanges and determine how it failed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port src interface down).Explanation Ethernet link to which the FCIP interface is bound is down.
Recommended Action Verify that the Ethernet cable is connected and that the interface is administratively enabled.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port src interface link down).Explanation Ethernet link to which the FCIP interface is bound is down.
Recommended Action Verify that the Ethernet cable is connected and that the remote end is also active.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not present).Explanation The small form-factor pluggable (SFP) device has been removed.
Recommended Action Insert an SFP.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down (Error disabled - Fcot vendor not supported).Explanation The inserted small form-factor pluggable (SFP) device is not supported.
Recommended Action Contact customer support for a list of authorized SFP vendors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure).Explanation The module hardware has failed.
Recommended Action Collect more information about failed module by entering the show module internal all module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive).Explanation The port VSAN has been suspended or deleted.
Recommended Action Assign a new active port VSAN to the interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down (Error disabled - Incompatible admin port mode).Explanation The configured mode is not supported on this interface.
Recommended Action Enter a show port internal info to determine the list of modes supported on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit).Explanation The configured receive BB_credit size is not supported.
Recommended Action Get the allowed receive BB_credit size from show port internal info.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize).Explanation The configured receive buffer size is not supported.
Recommended Action Get the allowed receive buffer size from show port internal info.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down (Error disabled - Incompatible admin port speed).Explanation The configured speed is not supported on this interface.
Recommended Action Enter show port internal info to determine the range of speed supported on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down (Initializing).Explanation The interface is in the process of coming up.
Recommended Action If the interface is stuck in this state for an extended time, check the output of show port internal event-history to determine what it is waiting for.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed).Explanation The interface has been removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link failure).Explanation The physical link has gone down.
Recommended Action Verify that the cable is connected and the remote end is not shut down.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure).Explanation Diagnostic tests failed on the interface.
Recommended Action Enter attach module to connect to the module and collect more information about the failed interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down (Isolation due to port loopback to same switch).Explanation The interface is looped back to another interface on the same switch.
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module removed).Explanation Interface is down because the module was removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating).Explanation The loop port has been put into nonparticipating mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_NONE: Interface [chars] is down (None).Explanation There is no apparent reason why the interface is down.
Recommended Action Enter show port internal info or show port internal event-history to collect more information about port and determine why it went down.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline).Explanation The interface has been placed into an offline state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down).Explanation The parent interface is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. closed by peer).Explanation The FCIP peer connected to this interface closed the TCP connection.
Recommended Action Enter show interface to find the IP address of this FCIP interface. Check to see why the peer closed the TCP connection.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. reset by peer).Explanation The TCP connection to the FCIP peer has been reset.
Recommended Action Enter the show interface and show ip route CLI command. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down (No operational members).Explanation This is a PortChannel interface and all its members are operationally down.
Recommended Action Enable at least one of the PortChannel's members.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to port vsan mismatch).Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends.
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and enter the shutdown and then no shutdown commands. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in progress).Explanation There is a fabric reconfiguration in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port software failure).Explanation The software servicing the data path on the port has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is down(Tunnel source module not online).Explanation The module that has the tunnel source port of this FCIP interface is not fully online.
Recommended Action The module that has the tunnel source port is coming online. Enter show module to find the module status.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down (Tunnel port src interface unbound).Explanation The tunnel port source interface is unbound.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel src port removed).Explanation The tunnel source port of this FCIP interface has been removed.
Recommended Action The source interface with an IP address that matches the IP address of the bound entity is removed. This happens normally when the module on which the source interface exists is removed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended).Explanation This interface belongs to a PortChannel and has been suspended because of an error during port bringup.
Recommended Action Enter the shutdown CLI command then no shutdown. If this happens again, enter the show port internal info and show port internal event-history CLI commands on the interface to collect more information. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode).Explanation This interface belongs to a PortChannel and the operational mode of the interface is different from that of the PortChannel.
Recommended Action Change the mode and the trunking mode of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed).Explanation This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel.
Recommended Action Change the speed of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down (Suspended due to incompatible remote switch WWN).Explanation This interface belongs to a PortChannel and the remote switch WWN of the interface is different from that of the PortChannel.
Recommended Action Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is down(TCP conn. closed - Keep alive expired).Explanation The TCP session to the FCIP peer was closed due to loss of the TCP keepalive.
Recommended Action This may be due to loss of IP connectivity. Enter the show interface and show ip route CLI commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP conn. closed - retransmit failure).Explanation Interface is down due to a maximum retransmission failure.
Recommended Action This may be due to loss of IP connectivity. Enter the show interface and show ip route CLI commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is down(TCP conn. closed - Persist timer expired).Explanation The TCP persist timer expired and the connection was in idle state for the maximum backoff time without receiving an ACK (TCP window size update) from the peer.
Recommended Action This may be due to loss of IP connectivity. Enter the show interface and show ip route commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can also use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and check the connection to the peer.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down (Linecard upgrade in progress).Explanation A line card software upgrade is in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to VSAN mismatch).Explanation This is a trunking interface and the VSANs configured here do not match the VSANs configured on the remote end.
Recommended Action Check the VSANs configured on the local end with the remote end.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to zone merge failure).Explanation The interface has been isolated due to a failure during zone merge.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is down (Isolation due to remote zone server not responding).Explanation Isolated due to remote zone server not responding.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release1.2(2a).
Error Message ETHPORT-5-IF_TRUNK_DOWN: Interface [chars], VSAN [chars] is down ([chars]).Explanation The interface is trunking and the VSAN is down due to the reason shown.
Recommended Action Enter show interface, show port internal info interface [vsan], and show port internal event-history interface [vsan] to help determine why this VSAN is down on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_TRUNK_UP: Interface [chars], VSAN [chars] is up.Explanation The interface is trunking and the VSAN is up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ETHPORT-5-IF_UP: Interface [chars] is up [chars].Explanation Interface is up. If applicable, the mode is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
EXCEPTIONLOG Messages
This section contains the exception log (EXCEPTIONLOG) messages.
EXCEPTIONLOG-SLOT#-2
Error Message EXCEPTIONLOG-SLOT#-2-LC_EXP_MSG: Linecard exception: [chars] is the affected Port bit map. [dec] Additional information - [chars].Explanation Line card exception event.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FC-TUNNEL Messages
This section contains the FC-TUNNEL messages.
FC-TUNNEL-3
Error Message FC-TUNNEL-3-INTERNAL_ERROR: Internal error: [chars].Explanation FC MPLS tunnel process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-IPFC_ERROR: IPFC API, [chars], failed with error [hex].Explanation FC MPLS tunnel invoked the IPFC API and received the error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-MTS_ERROR: MTS message transmission failed with error [dec].Explanation FC MPLS tunnel process unsuccessfully tried to send a messaging and transaction service (MTS) message. The messaging and transaction service (MTS) error number is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-NS_ERROR: FCNS API, [chars], failed with error [hex].Explanation FC MPLS tunnel invoked the Fibre Channel name server (FCNS) API and received an error code. The error message shows the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-PM_ERROR: Port Manager API, [chars], failed with error [hex].Explanation FC MPLS tunnel invoked the Port Manager API and received an error. The error message shows the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars] failed with error [hex].Explanation FC MPLS tunnel read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message shows the configuration, which the process tried to restore and system error code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-PSS_ERROR: PSS operation [chars] returned error: [hex].Explanation A persistent storage service operation failed. The error message shows the context where the failure occurred and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex].Explanation FC MPLS tunnel read the saved runtime database and encountered an error while rebuilding the runtime database. The error message shows the runtime database, which the process tried to restore and the system error code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-RIB_ERROR: RIB API, [chars], failed with error [hex].Explanation FC MPLS tunnel invoked the routing information base (RIB) API and received an error. The error message shows the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-RSVP_PROTO_ERROR: RSVP protocol error: [chars].Explanation RSVP-TE protocol error is encountered. The error message shows the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is received.Explanation FC MPLS tunnel process received unexpected messaging and transaction service (MTS) event. The error message shows the messaging and transaction service (MTS) opcode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FC-TUNNEL-5
Error Message FC-TUNNEL-5-MSG_INTERFACE_DOWN: Interface [chars] is down.Explanation The Fibre Channel interface is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FC-TUNNEL-5-MSG_INTERFACE_UP: Interface [chars] is up.Explanation The Fibre Channel interface is up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCC Messages
This section contains the Fibre Channel Congestion Control (FCC) messages.
FCC-2
Error Message FCC-2-SHUTDOWN: Process shutting down: [chars].Explanation The Fibre Channel Congestion Control process is shutting down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCC-5
Error Message FCC-5-BAD_MSG: Received bad message: [chars].Explanation The Fibre Channel Congestion Control process has received a malformed or unrecognized message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCC-5-CONGESTION_STATE_CHANGE_NOTIF: Received Congestion State Change notification to state: [dec].Explanation The Fibre Channel Congestion Control process has received a congestion state change notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC-5-DISABLE: FCC has been disabled.Explanation The Fibre Channel Congestion Control process has been disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCC-5-ENABLE: FCC has been enabled.Explanation The Fibre Channel Congestion Control process has been enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCC-5-RATE_LIMIT_END_NOTIF: Received Rate Limit End notification.Explanation The Fibre Channel Congestion Control process has received a rate limit end notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC-5-RATE_LIMIT_START_NOTIF: Received Rate Limit Start notification.Explanation The Fibre Channel Congestion Control process has received a rate limit start notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC-5-STARTING: FCC process started.Explanation The Fibre Channel Congestion Control process started successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCC-6
Error Message FCC-6-PRIO_UPDATE: Updated enable priority to [dec].Explanation The Fibre Channel Congestion Control process is active for packets with priority greater than or equal to the threshold shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCC_LC Messages
This section contains the Fibre Channel Congestion Control line card (FCC_LC) messages.
FCC_LC-2
Error Message FCC_LC-2-ERROR_SENDING_HEART_BEAT: Error sending heart beat [dec].Explanation Fibre Channel Congestion Control line card (FCC_LC) had an error sending a heartbeat.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCC_LC-2-EXITING: Exiting fcc_lc: [chars].Explanation Fibre Channel Congestion Control line card (FCC_LC) is exiting.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message FCC_LC-2-HEART_BEAT_NOT_SENT: Heart beat not sent for [dec] millisecs.Explanation Fibre Channel Congestion Control line card (FCC_LC) has not sent a heartbeat.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCC_LC-2-UNABLE_READ_DATA: Unable to read fcc data ([chars]).Explanation Fibre Channel Congestion Control is unable to read and process relevant FCC data.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCC_LC-2-SHUTDOWN: Process shutting down: [chars].Explanation The Fibre Channel Congestion Control line card process is shutting down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
FCC_LC-5
Error Message FCC_LC-5-BAD_MSG: Received bad message: [chars].Explanation The Fibre Channel Congestion Control line card process has received a malformed or unrecognized message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC_LC-5-DISABLE: FCC_LC has been disabled.Explanation The Fibre Channel Congestion Control line card process has been disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC_LC-5-ENABLE: FCC_LC has been enabled.Explanation The Fibre Channel Congestion Control line card process has been enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCC_LC-5-STARTING: FCC_LC process started.Explanation The Fibre Channel Congestion Control line card process started successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
FCC_LC-6
Error Message FCC_LC-6-PRIO_UPDATE: Updated enable priority to [dec].Explanation The Fibre Channel Congestion Control line card process is active for packets with priority less than or equal to the threshold shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
FCD Messages
This section contains the FICON control device (FCD) messages.
FCD-7
Error Message FCD-7-SB3_ABTS_EXCHANGE: sb3 aborted exchange[hex] from vsan:[dec] ch:[hex] chi:[hex] ccw:[hex] token:[hex] cmd:[hex] reason:[chars] state:[chars]:[dec].Explanation SB3 aborted exchange due to the reason given. Aborts are caused by either the channel or control unit detecting a device protocol error. Recovery actions are performed to restore communication. In certain circumstances aborts occur in normal operations.
Recommended Action No action is required if communication with FICON control device is still operational.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDD Messages
This section contains the Fibre Channel device discovery (FCDD) messages.
FCDD-SLOT#-3
Error Message FCDD-SLOT#-3-LOG_FCDD_ERR: Nonrecoverable error - exiting: [chars].Explanation Errors caused the program to exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDD-SLOT#-4
Error Message FCDD-SLOT#-4-LOG_FCDD_WARNING: Warning!: [chars].Explanation Serious errors that affect all normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDD-SLOT#-5
Error Message FCDD-SLOT#-5-LOG_FCDD_GCONF_FSM: [chars].Explanation Illegal event received in global configuration finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDD-SLOT#-5-LOG_FCDD_NOTICE: [chars].Explanation Major configuration changes occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDD-SLOT#-5-LOG_FCDD_RESCAN_FSM: [chars].Explanation Illegal event received in rescan finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDD-SLOT#-5-LOG_FCDD_TZONE_FSM: [chars].Explanation Illegal event received in twilight zone remover finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDD-SLOT#-5-LOG_FCDD_VCONF_FSM: [chars].Explanation Illegal event received in VSAN configuration finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDD-SLOT#-5-LOG_FCDD_VNO_FSM: [chars].Explanation Illegal event received in VSAN normal operation finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDD-SLOT#-7
Error Message FCDD-SLOT#-7-LOG_FCDD_DEBUG: [chars].Explanation Unexpected errors that affect some normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDD_HELPER Messages
This section contains the FCDD_HELPER messages. FCDD_HELPER messages were deprecated in Cisco MDS SAN-OS Release 1.3(3a). They were replaced with FCDDH messages.
FCDD_HELPER-SLOT#-3
Error Message FCDD_HELPER-SLOT#-3-LOG_FCDDH_ERR: Nonrecoverable error - exiting: [chars].Explanation Errors caused the program to exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCDD_HELPER-SLOT#-4
Error Message FCDD_HELPER-SLOT#-4-LOG_FCDDH_WARNING: Serious error: [chars].Explanation Serious errors that affect all normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCDD_HELPER-SLOT#-5
Error Message FCDD_HELPER-SLOT#-5-LOG_FCDDH_DEBUG: Unexpected error: [chars].Explanation Unexpected errors that affect some normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCDD_HELPER-SLOT#-5-LOG_FCDDH_NOTICE: [chars].Explanation Major configuration changes occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCDDH Messages
This section contains the Fibre Channel device discovery helper FCDDH messages.
FCDDH-SLOT#-3
Error Message FCDDH-SLOT#-3-LOG_FCDDH_ERR: Nonrecoverable error - exiting: [chars].Explanation Errors caused the program to exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FCDDH-SLOT#-4
Error Message FCDDH-SLOT#-4-LOG_FCDDH_WARNING: Serious error: [chars].Explanation Serious errors that affect all normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FCDDH-SLOT#-5
Error Message FCDDH-SLOT#-5-LOG_FCDDH_DEBUG: Unexpected error: [chars].Explanation Unexpected errors that affect some normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FCDDH-SLOT#-5-LOG_FCDDH_NOTICE: [chars].Explanation Major configuration changes have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FCDOMAIN Messages
This section contains the Fibre Channel domain manager (FCDOMAIN) messages.
FCDOMAIN-2
Error Message FCDOMAIN-2-DOMS_CONFLICT: Conflict detected: ([dec]) domain ID [dec] WWN [chars].Explanation Two switches have the same WWN or domain ID.
Recommended Action Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-2-EPORT_ALREADY_ISOLATED: Interface [chars] is down - VSAN [dec].Explanation The domain manager was going to isolate the interface in the VSAN shown in the error message, but the interface does not exist.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-2-EPORT_ISOLATED: Isolation of interface [chars] (reason: [chars]).Explanation The domain manager has isolated the interface because of the reason shown in the error message. Enter show interface. Based on the reason specified, you might have to reinitialize the port or ensure the domains are adequate and unique in the VSAN and perform a disruptive restart by entering fcdomain restart disruptive.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-FC2_INITIALIZATION_FAILED: FC initialization sequence failed.Explanation The domain manager process has not been able to complete the initialization sequence with the FC (Fibre Channel) subsystem. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-FC2BIND_FAILED: Bind to FC2 Service failed.Explanation The domain manager has not been able to contact the FC2 module.
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.2(2a).
Error Message FCDOMAIN-2-FCID_PERSISTENT_TBL_COMPLETELY_FULL: FCID persistent table is completely full.Explanation The domain manager has the FC ID persistent table full with entries. Enter show fcdomain fcid persistent to view the entries currently in the table. No more entries can be saved as persistent FC IDs across reboots.
Recommended Action Enter purge fcdomain fcid to purge stale entries and to obtain more free entries. Alternatively, you can disable the feature on certain VSANs which are not critical using no fcdomain fcid persistent.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-INITIALIZATION_FAILED: Initialization sequence failed.Explanation The domain manager has not been able to complete the initialization sequence. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-MTS_INITIALIZATION_FAILED: IPC initialization sequence failed.Explanation The domain manager has not been able to complete the initialization sequence with the interprocess communication (IPC) subsystem. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain 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.2(2a).
Error Message FCDOMAIN-2-MTSBIND_FAILED: Bind to IPC failed.Explanation The domain manager has not been able to contact the inter-process communication (IPC) module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-MTSREGISTRATION_FAILED: Registration of opcodes with IPC Service failed.Explanation The domain manager has not been able to register its messages with the inter-process communication (IPC) module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.Explanation The local switch has the same domain ID and WWN of another switch.
Recommended Action Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-2-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected conflict between two switches having the same non-virtual domain ID [dec] and the same WWN [chars].Explanation Two switches have the same non-virtual domain ID and the same WWN.
Recommended Action Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-2-PSSBIND_FAILED: Bind to Persistent Storage Service failed.Explanation The domain manager has not been able to contact the persistent storage service (PSS).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-RDIRJT: Rejected request for domain ID [dec], WWN requestor [chars] (reason code [dec]).Explanation An invalid request for domain IDs has been rejected by fcdomain.
Recommended Action Enter show fcdomain for all the switches in the affected VSAN. If a switch does not have a valid current domain ID, configure the preferred domain ID zero, then enter the fcdomain restart CLI command in the affected VSAN. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-SDWRAPBIND_FAILED: Bind to Debug Server failed.Explanation The domain manager has not been able to contact the history debug service. Any problems occurring in the domain manager will not be logged to this debug history list.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-SDWRAPHISTINIT_FAILED: Initialization of history message list failed.Explanation The domain manager has not been able to contact the history debug service. Any problems occurring in the domain manager will not be logged to this debug history list.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-2-SYSBIND_FAILED: Bind to System Manager service failed.Explanation The domain manager has not been able to contact the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-SYSMGR_INITIALIZATION_FAILED: System Manager initialization sequence failed.Explanation The domain manager has not been able to complete the initialization sequence with the system manager. The domain manager process depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-2-VSAN_MERGE_DETECTED: Merge detected with VSAN [dec] (Common Fabric Name [chars]).Explanation The local VSAN and remote VSAN have the same principal switch and are connected in the same logical fabric.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDOMAIN-3
Error Message FCDOMAIN-3-COMMITERRORLOCALINVALIDALLOWEDDOMS: A remote switch attempted to locally apply an illicit allowed domains configuration.Explanation A remote switch attempted to locally apply an allowed domains configuration that does not include all currently assigned domains or the locally configured domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-3-COMMITERRORREMOTEINVALIDALLOWEDDOMS: A remote switch (domain ID [dec], WWN [chars]) refuses to locally apply the proposed allowed domains.Explanation The remote switch the with domain ID and WWN listed in the error message refuses to locally apply the proposed allowed domains. This is probably because the proposed allowed domains list is incompatible with the locally configured domain or domain ID list.
Recommended Action Check the configuration on the remote switch, and make sure that the proposed allowed domains include the local domain ID. Also, make sure that the proposed allowed domains include all the domains in the local domain ID list.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-3-MTSOPENTRX_FAILED: IPC failure (opening of a transaction failed).Explanation The domain manager was not able to open a transaction for high availability purposes.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-MTSRECV_FAILED: IPC failure (receiving of a message failed).Explanation The domain manager has not been able to receive a message from the inter-process communication (IPC) module.
Recommended Action Execute a nondisruptive fcdomain restart in the affected VSAN.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-MTSRESP_FAILED: IPC failure (replying to a message failed).Explanation The domain manager has not been able to reply to a request coming from the inter-process communication (IPC) module.
Recommended Action Execute a nondisruptive fcdomain restart in the affected VSAN.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-MTSSEND_FAILED: IPC failure (sending of a message failed).Explanation The domain manager has not been able to send a message to the message transactional service (MTS).
Recommended Action Execute a nondisruptive fcdomain restart in the affected VSAN.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-MTSSENDREQ_FAILED: IPC failure (sending of a request failed).Explanation The domain manager was not able to send a request using the inter-process communication module.
Recommended Action Execute a nondisruptive fcdomain restart in the affected VSAN.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-NVRAMFAILURE: NVRAM open failed.Explanation Reading the last assigned run time domain IDs from NVRAM failed.
Recommended Action The domain manager is able to continue without using the NVRAM.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-3-PORT_SUSPENDED: Response (Cmd Code [hex]) for SWILS [hex] intended for [chars] is received on [chars].Explanation An FC2 SW-ILS response frame has been received on the wrong interface.
Recommended Action Check the configuration of both the interfaces on the local switch; also check the interfaces on the other side of the corresponding links. Ensure whether the interfaces should all belong to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message FCDOMAIN-3-SDWRAPBIND_FAILED: Bind to debug server failed.Explanation The domain manager feature has not been able to contact the debug service. Any problems occurring in the The domain manager feature will not be logged.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-3-SDWRAPHISTINIT_FAILED: Initialization of history message list failed.Explanation The domain manager feature has not been able to contact the debug history service. Any problems occurring in the fcdomain feature will not be logged to this debug history.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-3-VSAN_MERGE_DETECTED: Merge detected with VSAN [dec] (Common Fabric Name [chars]).Explanation The local VSAN and VSAN [dec] have the same principal switch [chars], hence are connected in the same logical fabric.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
FCDOMAIN-4
Error Message FCDOMAIN-4-DM_ALLOWED_DM_LIST_MOD_ON_SUBORDINATE: Allowed domain list for vsan [dec] modified on subordinate switch with fcdomain distribution enabled.Explanation The allowed domai list was modified on a non-principal switch while fcdomain distribution was enabled.
Recommended Action We recommend that you modify the allowed domain list on the principal switch only when fcdomain distribution is enabled. Discard the current session on the local switch and start a new one on the principal switch.
Introduced Cisco MDS SAN-OS Release 3.0(2).
Error Message FCDOMAIN-4-FABRICCONFSTARTRCF: Disruptive reconfiguration started.Explanation A disruptive reconfiguration (RCF phase) started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-4-FC2_CORRUPTED: Received malformed FC2 [chars] frame.Explanation The domain manager received a malformed FC2-SWILS frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-4-FCID_PERSISTENT_TBL_ALMOST_FULL: FCID persistent table is almost full.Explanation The domain manager has 80% or more of the FC ID persistent table full with entries. Enter show fcdomain fcid persistent to view the entries currently in the table.
Recommended Action Enter purge fcdomain fcid to purge stale entries and to obtain more free entries.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDOMAIN-5
Error Message FCDOMAIN-5-DOMAIN_TYPE_IS_PREFERRED: The domain ID type is currently configured as preferred in all the existing VSANs.Explanation All the currently existing VSANs have the domain ID type configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link.
Recommended Action Use the CLI or Fabric Manager/Device Manager to configure the domain ID type as static in an existing VSAN. On the CLI, enter the fcdomain domain [static vsan vsan-id] command.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-5-FABRICCONFSTARTBF: Nondisruptive reconfiguration started - VSAN [dec].Explanation A nondisruptive reconfiguration started on VSAN [dec].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-5-FCIDP_DISABLED: FCID persistency feature is currently not enabled in any of the existing VSANs.Explanation All the currently existing VSANs have the FC ID persistency feature disabled.
Recommended Action Enter fcdomain fcid persistent [vsan]
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-5-FCID_PERSISTENT_TBL_HALF_FULL: FCID persistent table is half full.Explanation The domain manager has 50% of the FC ID persistent table full with entries. Enter show fcdomain fcid persistent
Recommended Action Enter purge fcdomain fcid to purge stale entries and to obtain more free entries.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-5-PSWSSTARTED: Principal Switch Selection started - VSAN [dec].Explanation The principal switch selection has started for the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSDATAREQUEST: Received CFS Data request from unknown domain [dec].Explanation A CFS Data request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSLOCKREQUEST: Received CFS Lock request from unknown domain [dec].Explanation A CFS Lock request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSRELEASEREQUEST: Received CFS Release request from unknown domain [dec].Explanation A CFS Release request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-5-UNKNOWNDOMAININUNKNOWNCFSREQUEST: Received CFS request from unknown domain [dec].Explanation A CFS request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
FCDOMAIN-6
Error Message FCDOMAIN-6-BF_STARTED: BF started by [chars].Explanation A build fabric has started in this VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message FCDOMAIN-6-CANNOTFREESINGLEFCID: Impossible to free single FCIDs.Explanation It is not possible to free single FC IDs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-CLEARLOCKNOTIFICATIONRECEIVED: Implict lock release.Explanation Lock has been implicitly released due to a clear session operation.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release.
Error Message FCDOMAIN-6-DOMAINID_INVALID: Local domain ID invalid.Explanation The local domain ID is invalid.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-6-DOMAINID_VALID: Local domain ID [dec] available.Explanation The domain ID is available.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a)
Error Message FCDOMAIN-6-DOWNSTREAM_SWITCHED: Downstream interface has been fast-switched from [chars] to [chars].Explanation The downstream interface has been fast-switched because of a link failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(2)
Error Message FCDOMAIN-6-UPSTREAM_SWITCHED: Upstream interface has been fast-switched from [chars] to [chars].Explanation The upstream interface has been fast-switched because of a link failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(2)
Error Message FCDOMAIN-6-EPORT_ALREADY_CREATED: Interface [chars] already created.Explanation The interface is already created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-EPORT_ALREADY_DOWN: Interface [chars] is already down.Explanation The interface is already down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-EPORT_CLEANUP: Interface [chars] received cleanup request.Explanation The domain manager on the interface has received a cleanup request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-EPORT_CREATED: Creation of interface [chars].Explanation The domain manager is going to create the interface shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-EPORT_DOWN: Interface [chars] is down.Explanation The domain manager is going to remove the interface from its database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-FABRICCONFSTARTBF: Nondisruptive reconfiguration started.Explanation A nondisruptive reconfiguration (BF phase) of the VSAN has started. This can happen when two or more fabrics merge, or when the user manually triggers a nondisruptive reconfiguration of the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-6-FABRICNAME_INVALID: Fabric name not available.Explanation Fabric name is not available.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-FABRICNAME_VALID: Fabric name [chars] available.Explanation Fabric name is available.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-FCIDALREADYFREE: FCIDs already free.Explanation FC IDs are already free.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-FCIDNOTSTORED: FCIDs not stored.Explanation FC IDs are not stored.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-FCIDS_ASSIGNED: Assigned FCID(s) [hex]:[hex]:[hex] with mask [dec].Explanation The domain manager assigned the FC ID(s) with mask shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message FCDOMAIN-6-FCIDS_FREED: Freed FCID(s) [hex]:[hex]:[hex] with mask [dec].Explanation The domain manager freed FC ID(s) with the mask shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message FCDOMAIN-6-FCIDP_ENABLED_DOM_TYPE_PREFERRED: FCID persistency is enabled, but the domain ID type is configured as preferred.Explanation The FC ID persistency feature is enabled, but the domain ID type is configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link. Should the domain ID change, all the FC IDs associated with it would be invalidated.
Recommended Action Use the CLI or Fabric Manager/Device Manager to configure the domain ID type as static in an existing VSAN. On the CLI, enter the fcdomain domain static vsan [vsan-id] command.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-6-FCIDS_ASSIGNED: Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].Explanation The domain manager assigned a sequence of 256 contiguous FC IDs starting from the FC ID shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-6-FCIDS_FREED: Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].Explanation The domain manager freed a sequence of 256 contiguous FC IDs starting from FC ID shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-6-INCORRECTDOMAIN: Requested FCIDs with domain field different from local domain.Explanation FC IDs were requested with the domain field different from local domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-INCORRECTDOMAINRANGE: Requested FCIDs with domain field not in expected range.Explanation Requested FC IDs with domain field not in expected range.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-INVALIDARG: Requested FCID of type 00.00.YY, but specifying an entire area.Explanation An FC ID was requested with type 00.00.YY, but specified an entire area.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.Explanation It has been detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.
Recommended Action Check which switches have the same WWN and change either one; then change the domain ID of either one.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-MY_SAME_WWN_DIFFERENT_DOMS_CONFLICTS: During VSAN merge detected local WWN [chars] is already in use by another switch (the two switches have different domain IDs: [dec] (local) and [dec]).Explanation It has been detected that the local switch has the same WWN [chars] of another switch, and that they have different domain IDs: [dec] (local) and [dec].
Recommended Action Check which switches have the same WWN and change either one.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCDOMAIN-6-NODOMAIN: Local domain not available.Explanation The local domain is not available yet.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-NOFREEFCID: No free FCIDs.Explanation No free FC IDs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected conflict between two switches having the same non-virtual domain ID [dec] and the same WWN [chars].Explanation It has been detected that two switches have the same non-virtual domain ID [dec] and the same WWN [chars].
Recommended Action Check which switches have the same WWN and change either one; then change the domain ID of either one.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-NOTOWNER: Feature [dec] cannot free FCID ([dec]:[dec]:[dec]).Explanation Feature universal unique ID (UUID) cannot free the FC ID shown in the error message because it is not its owner.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-OTHER_SIDE_VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected overlap with virtual IVR domain ID [dec] from across the link.Explanation The VSAN merge detected an overlap between the local VSAN domain ID list and the IVR virtual domain ID list in the remote VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-PSWSSTARTED: Principal Switch Selection started.Explanation A principal switch selection (PSwS phase) has started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-6-RCF_STARTED: RCF started by [chars].Explanation A fabric reconfiguration has started in this VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message FCDOMAIN-6-REQSINGLEFCIDWITHINRESERVEDRANGE: Requested single FCIDs in area [dec] within the reserved range.Explanation Requested single FC IDs in an area within the reserved range.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-REQUESTEDFCIDNOTFREE: Requested FCIDs not free.Explanation Requested FC IDs are not free.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-REQUESTEDFCIDRESERVED: Requested reserved FCIDs.Explanation Requested reserved FC IDs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-REQUESTEDRESERVEDFCIDMISMATCH: Requested persistent FCIDs, but there is a mismatch.Explanation Requested persistent FC IDs, but there is a mismatch.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-SAME_WWNS_DIFFERENT_DOMS_CONFLICTS: During VSAN merge detected two switches with same WWN [chars] and different non-virtual domain IDs [dec] and [dec].Explanation Two switches have the same WWN but different non-virtual domain IDs.
Recommended Action Check which switches have the same WWN and change either one.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-TIMER_UNKNOWN: fcdomain has received a notification for an unknown timer expiration.Explanation A timer unknown to the domain manager has expired.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected overlap with local virtual IVR domain ID [dec].Explanation The VSAN merge detected an overlap between the IVR virtual domain ID on the local VSAN and the domain IDs on the remote VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FCDOMAIN-6-UUIDNOSPACEFOUND: No available space to store the identity of the requestor the FCIDs.Explanation No available space to store the identity of the requestor for the FC IDs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-6-UUIDNOTFOUND: Universal Unique ID (UUID) not found.Explanation Universal unique ID (UUID) not found.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCDOMAIN-7
Error Message FCDOMAIN-7-EPORT_ALREADY_ISOLATED: Interface [chars] is down.Explanation The domain manager was going to isolate the interface, but the interface does not exist.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDBF: Nondisruptive reconfiguration completed.Explanation A nondisruptive reconfiguration (BF phase) completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDRCF: Disruptive reconfiguration completed.Explanation A disruptive reconfiguration (RCF phase) has completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-FC2_RETRY: Retransmission of FC2 frame on interface [chars] (Cmd Code: [hex]).Explanation The domain manager is retrying an FC2 frame on the interface because of a loss/no response. The command code of the frame is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-FCID_IN_USE_PURGING_FOR_FICON_MGR: FICON needs to purge the persistent FCID table, but at least one FCID is still in use, preventing this purge from completely remove all entries belonging to the VSAN.Explanation There may be a problem in the sequence that shuts down all interfaces before fcdomain receives a request from FICON manager to purge the persistent FC ID table.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FCDOMAIN-7-FSM_FAILED: FSM transition failed on interface [chars] (current state [chars]).Explanation The domain manager finite state machine generated an invalid event on the interface for which no proper action was defined.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-FSM_FORBIDDEN_TRANSITION: fcdomain state machine has hit a forbidden transition.Explanation The domain manager state machine has tried to execute a forbidden transition.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-INTERFACERDY: Interface [chars] ready.Explanation Interface is ready.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-PREACTIONTYPE_UNKNOWN: fcdomain state machine has hit an unknown pre-action type.Explanation An undefined pre-action type has been used.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-PSWSCOMPLETED: Principal Switch Selection completed (Fabric Name [chars]).Explanation The principal switch selection (PSwS phase) has completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCDOMAIN-7-RDIACC: Assigned domain ID [dec], WWN of requestor [chars] (requested domain ID [dec]).Explanation Domain ID has been received by VSAN with WWN shown in the error message. The requested domain ID is also shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCFWD Messages
This section contains the FCFWD messages.
FCFWD-3
Error Message FCFWD-3-ERROR: [chars].Explanation FCFWD encountered an error.
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.2(2a).
FCFWD-4
Error Message FCFWD-4-WARNING: [chars].Explanation FCFWD is generating a relevant notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCFWD-6
Error Message FCFWD-6-INFO: [chars].Explanation An FCFWD event happened.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCMPLS Messages
This section contains the FC MPLS messages. FC MPLS messages were deprecated in Cisco MDS SAN-OS Release 1.3(1).
FCMPLS-2
Error Message FCMPLS-2-PROC_SHUTDOWN: daemon shutting down.Explanation FC MPLS process exited.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-2-PROC_STARTING: daemon started in the [chars] mode.Explanation FC MPLS process started. The error message describes the start mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCMPLS-3
Error Message FCMPLS-3-INTERNAL_ERR: Internal err: [chars].Explanation FC MPLS process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-3-NO_MEM: out of memory.Explanation FC MPLS process is out of dynamic memory.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-3-PSS_ERR: PSS err: [chars].Explanation The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-3-RIB_ERROR: RIB api error, api to [chars] returned [dec].Explanation FC MPLS invoked routing information base (RIB) API and received the error. The error message describes the API.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, 0x[dec], is received.Explanation FC MPLS process received unexpected messaging and transaction service (MTS) event. MTS opcode is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCMPLS-5
Error Message FCMPLS-5-LDP_SES_ESTABLISHED: LDP session with [chars] is established.Explanation A new LDP session is established.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-5-LDP_SES_SHUTDOWN: LDP session with [chars] is shutdown.Explanation Existing LDP session has been shut down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCMPLS-6
Error Message FCMPLS-6-FT_SEQ_ROLLOVER: Rolling over the local ft ack number.Explanation Fault-tolerant LDP is handling sequence number overflow.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-6-LDP_START_SENDING_HELLO: LDP start sending hellos to [chars].Explanation LDP start sending hellos to establish a session.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-6-LDP_STOP_SENDING_HELLO: LDP stop sending hellos to [chars].Explanation LDP stopped sending hello messages to the LDP peer specified in [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-6-UNKNOWN_MSG_TYPE_RXED: Unknown LDP message type 0x[hex] is received from [chars].Explanation LDP process received an unknown LDP message type is specified in hex.The error message describes the LDP peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FCMPLS-6-UNKNOWN_TLV_RXED: Unknown LDP TLV: type 0x[hex], length [dec], is received from [chars].Explanation LDP process received an unknown TLV. TLV type received is specified in [hex]. TLV length is specified. The error message describes the LDP peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
FCNS Messages
This section contains the Fibre Channel name server (FCNS) messages.
FCNS-2
Error Message FCNS-2-DB_FULL: the database; max entries [dec] exceeded.Explanation Name server database is full. The max number of entries of ports is already present in the database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-2-INIT_FAILURE: : [chars].Explanation The Fibre Channel name server initialization has failed due to [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-2-NO_RESPONSE: domain [dec].Explanation No response in the VSAN from domain shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-2-PSS_VERSION_MISMATCH: : for [chars].Explanation Version mismatch for persistent storage service (PSS) for the type shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-2-RELOAD_FAILURE: : [chars].Explanation Failed to reload information from persistent storage service( PSS).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCNS-3
Error Message FCNS-3-BAD_FRAME: : [chars].Explanation Received a bad frame from the network.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-CFG_FAILURE: : [chars].Explanation A failure related to the Fibre Channel name server configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-CHUNK_FAILURE: : [chars].Explanation Chunk memory failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-DB_FAILURE: : [chars].Explanation A failure occurred in the Fibre Channel name server database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-MALLOC_FAILURE: : [chars].Explanation Memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-MTS_FAILURE: : [chars] [chars].Explanation Failure occurred trying to do a messaging and transaction service messaging and transaction service (MTS) operation.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-3-PSS_FAILURE: : [chars].Explanation Persistent storage service (PSS) failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCNS-6
Error Message FCNS-6-DB_INFO: : [chars] [hex].Explanation Database modification for the entry shown in the error message has occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCNS-6-STATUS_INFO: : [chars].Explanation A change in the Fibre Channel name server status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCS Messages
This section contains the Fabric Configuration Server (FCS) messages.
FCS-2
Error Message FCS-2-ALLOC_FAILED: Memory allocation failed for size:[dec].Explanation Memory allocation failed.
Recommended Action Restart the process.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCS-2-CHUNK_ALLOC_FAILED: Chunk memory allocation failed for [chars] chunk.Explanation Chunk memory allocation failed. The error message indicates the chunk name.
Recommended Action Restart the process.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCS-2-NO_RESPONSE: Retried maximum number of times for [chars] to domain [dec] in VSAN [dec].Explanation Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message FCS-2-RANDNUM_FAIL: [chars].Explanation There was a critical error during random number generation. This error message indicates details of the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
FCS-3
Error Message FCS-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].Explanation There was a mismatch in the persistent storage services (PSS) version.The error message indicates the PSS service, its current version number, and the expected version.
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.2(2a).
Error Message FCS-3-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex].Explanation An invalid Fabric Configuration Server (FCS) FC-CT frame received from FC ID is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCS-3-DB_ERR: [chars].Explanation An error occurred during a Fabric Configuration Server (FCS) database operation. [chars] indicates the reason for the error.
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.2(2a).
Error Message FCS-3-INIT_FAIL: [chars].Explanation An error happened during Fabric Configuration Server (FCS) initialization. The error message indicates the reason for failure.
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.2(2a).
Error Message FCS-3-MTS_ERR: [chars].Explanation An error occurred in processing of a messaging and transaction service (MTS) message. The error message indicates the error that occurred.
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.2(2a).
Error Message FCS-3-NO_MTS_RESP: [chars].Explanation There was no response to a messaging and transaction service (MTS) request. The error message indicates details of the messaging and transaction service (MTS) message.
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.2(2a).
Error Message FCS-3-NO_REMOTE_RESP: No response for request [chars] from domain [dec] in VSAN [dec].Explanation There was no response to an FC2 request. The error message indicates Fabric Configuration Server (FCS) request, remote domain, and VSAN ID.
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.2(2a).
Error Message FCS-3-OTHER_ERR: [chars].Explanation A Fabric Configuration Server (FCS) generic error occurred. The error message indicates the description of the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCS-3-PSS_ERR: [chars].Explanation An error occurred during a Fabric Configuration Server (FCS) persistent storage service (PSS) operation. The error message indicates the PSS operation that caused the error.
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.2(2a).
Error Message FCS-3-SOCK_ERR: sd: [dec], [chars].Explanation An FC-2 socket error occurred on socket-id (sd) listed in the error message. The error message indicates the reason for failure.
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.2(2a).
FCS-4
Error Message FCS-4-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex].Explanation An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
FCS-5
Error Message FCS-5-API_FAIL: [chars]: [chars].Explanation An API called by Fabric Configuration Server (FCS) failed. The error message indicates the failed API name and the reason for failure.
Recommended Action If this message is seen during a cold boot, it means that the queried module came up after Fabric Configuration Server (FCS) and this case can be ignored.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCS-6
Error Message FCS-6-INFORMATION: [chars].Explanation An event happened that affects FCS. The error message indicates the event.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCS-6-REXMIT_PKT: Retransmitting request [chars] to domain [dec] in VSAN [dec].Explanation There was a retransmission of an FC2 request. The error message indicates Fabric Configuration Server (FCS) request, the remote domain, and the VSAN ID.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FCSP-MGR Messages
This section contains the Fibre Channel Security Protocol (FCSP-MGR) messages.
FCSP-MGR-2
Error Message FCSP-MGR-2-ASSERT_FAILED: Code path reached unexpected location: assert might have been activated: File [chars] Line [dec].Explanation This is a deprecated message and should be ignored.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message FCSP-MGR-2-DBG_INIT_FAILED: Debug Infrastructure Initialization failed ( [chars] ).Explanation The debug infrastructure initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FCSP-MGR-2-FC2_E_INIT_FAILED: Fibre-Channel Initialization of an E_Port failed ( [chars] ).Explanation FC-SP manager is unable to initialize with the FC-2 E port infrastructure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-FC2_F_INIT_FAILED: Fibre-Channel Initialization of an F_Port failed ( [chars] ).Explanation FC-SP manager is unable to initialize with the FC-2 F port infrastructure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown FC-2 frame on [chars].Explanation Received an unexpected or unknown FC-2 frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-FCSP_AUTHENT_FAILURE: FC-SP Authentication failure on Port [chars] (FC-SP Failure Reason: [chars] [chars]).Explanation Fibre Channel authentication failed on the port.The error message shows the reason code detail.
Recommended Action Verify password configuration and ensure appropriate security modes on this port as well as its peer port.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FCSP-MGR-2-FSMU_INIT_FAILED: State Machine Infrastructure Initialization failed ( [chars] ).Explanation The state machine infrastructure has not initialized properly.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-IPC_INIT_FAILED: IPC (Inter Process Communication) Initialization failed ( [chars] ).Explanation FC-SP manager is unable to initialize with the inter-process communications infrastructure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service exiting.Explanation The license is unavailable. The FC-SP service will exit now.
Recommended Action Install the license file to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FCSP-MGR-2-MEM_FAILED: Memory operations failed File: [chars] Line [dec] for size [hex] bytes.Explanation A memory operation has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] ).Explanation FC-SP has failed following normal initialization.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FCSP-MGR-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed ( [chars] ).Explanation The persistent storage services (PSS) infrastructure initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FCSP-MGR-3
Error Message FCSP-MGR-3-TASK_Q_INIT_FAILED: Task Queue initialization failed.Explanation The task queue initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a)).
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
Error Message FCSP-MGR-3-TIMER_GRP_INIT_FAILED: Timer Group initialization failed.Explanation The timer group initialization failed.
Recommended Action No action is required.
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
FCSP-MGR-6
Error Message FCSP-MGR-6-UNCOMMON_RT_PATH: Runtime path reached special location: File [chars].Explanation This is a deprecated, internal message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
FDMI Messages
This section contains the Fabric-Device Management Interface (FDMI) messages.
FDMI-2
Error Message FDMI-2-MTS_ERROR: MTS message transmission failed with error [dec].Explanation The Fabric-Device Management Interface (FDMI) process unsuccessfully tried to send a messaging and transaction service (MTS) message. MTS error number is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-2-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars] failed with error [hex] for key type [dec].Explanation The Fabric-Device Management Interface (FDMI) read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message describes the configuration that the process tried to restore and the system error code.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FDMI-2-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex].Explanation The Fabric-Device Management Interface (FDMI) read the saved runtime database and encountered an error while rebuilding the runtime database. The error message describes the runtime database that the process tried to restore and the system error code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FDMI-3
Error Message FDMI-3-BAD_FRAME: Malformed frame received: [chars].Explanation The Fabric-Device Management Interface (FDMI) process received malformed frame. The error message describes the problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-BAD_RESPONSE: response with command code: [hex].Explanation The Fabric-Device Management Interface (FDMI) process received bad payload in response.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FDMI-3-INTERNAL_ERROR: Internal err: [chars].Explanation The Fabric-Device Management Interface (FDMI) process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-MTS_API_ERROR: API, [chars] returned [hex].Explanation The Fabric-Device Management Interface (FDMI) invoked the API and received the error code specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-MTS_FORMAT_ERROR: Unknown MTS message format in opcode [dec] from module [chars].Explanation The Fabric-Device Management Interface (FDMI) received message from the module that contains an unknown message format. The messaging and transaction service (MTS) opcode is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-NO_RESPONSE: No response from switch whose domain id is [dec].Explanation The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to a switch and has not received the response. The domain ID for the switch is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-PSS_ERROR: PSS operation [chars] returned err: [hex].Explanation The error message specifies the context where the failure occurred and specifies the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FDMI-3-SW_REJ_RESPONSE: Reject response [chars] from switch whose domain id is [dec].Explanation The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to a switch and has received the reject response with reason code in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message FDMI-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is received.Explanation The Fabric-Device Management Interface (FDMI) process received an unexpected messaging and transaction service (MTS) event. The messaging and transaction service (MTS) opcode is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FDMI-4
Error Message FDMI-4-SW_REJ_RESPONSE: Reject response [chars] from switch whose domain id is [dec].Explanation The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to the switch and has received the reject response with reason code in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FDMI-6
Error Message FDMI-6-DEBUG_INFO: [chars].Explanation This is Fabric-Device Management Interface (FDMI) process debug information.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FEATURE-MGR Messages
This section contains the feature manager (FEATURE-MGR) messages.
FEATURE-MGR-2
Error Message FEATURE-MGR-2-MODULE_FM_DONE: feature manager completed.Explanation Feature manager completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FEATURE-MGR-2-MODULE_FM_STARTED: feature manager started.Explanation Feature manager started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FICON Messages
This section contains the FICON messages.
FICON-2
Error Message FICON-2-E_DUPLICATE_PN_BRINGUP_FAIL: [chars].Explanation This port has the same port number assigned to another port in the same FICON VSAN. If two ports have duplicate port numbers in a FICON VSAN, only one port can be up at a time.
Recommended Action Avoid duplicate number assignment in each FICON VSAN
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-2-E_PN_PA_NOT_IN_BOUND: [chars].Explanation Port number or port address in the startup configuration is out of bound.
Recommended Action Change the FICON port number assigned and save the running configuration to the startup configuration.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-2-SHUTDOWN: FICON Manager process shutting down: [chars].Explanation FICON manager is shutting down.
Recommended Action This is a severe error. Provide the reason given in the message to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FICON-3
Error Message FICON-3-E_ASSIGN_BINDING_PN_FAIL: [chars].Explanation Port number has FCIP or port channel binding that cannot be removed or changed.
Recommended Action Remove port number binding of the logical interface first.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_ASSIGN_INVALID_PN_PARAM: [chars].Explanation Invalid port number parameters in command.
Recommended Action Check port numbers in the command.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_ASSIGN_OVERLAP_PN_FAIL: [chars].Explanation Port number assigned to physical and logical cannot overlap.
Recommended Action Check the port numbers in the command.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_ASSIGN_PN_NOT_DOWN_FAIL: [chars].Explanation Only port number assigned to a port in the down state can be removed or changed.
Recommended Action Bring down the port and then change the assigned port number.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_ASSIGN_PROHIBIT_PN_FAIL: [chars].Explanation Logical port address cannot be prohibited.
Recommended Action Check port numbers in the command.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_DUPLICATE_PN_ASSIGN_WARNING: [chars].Explanation This port has the same port number assigned to another port in the same FICON VSAN. No more than one port should have the same port number in each FICON VSAN.
Recommended Action Avoid duplicate number assignments in each FICON VSAN.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_INVALID_PA_BRINGUP_FAIL: [chars].Explanation This port either has an invalid port address assigned or has no port address assigned.
Recommended Action Assign a valid FICON port number to the port.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_PORT_PROHIBIT_BRINGUP_FAIL: [chars].Explanation This port has been prohibited. Prohibiting E or TE ports is not allowed. This port cannot be configured in E mode or TE mode until the prohibit dynamic connectivity mask configuration is changed.
Recommended Action Correct the prohibit dynamic connectivity mask (PDCM) for this port to bring it up as an E or TE port in a FICON VSAN.
Introduced Cisco MDS SAN-OS Release 1.3(3).
Error Message FICON-3-PDCM_CHANGE_REJ_E_PORT: [chars].Explanation The FICON prohibit dynamic connectivity mask (PDCM) change rejected because an E or TE port is being prohibited. Prohibiting an E or TE port in not allowed.
Recommended Action Correct the prohibit dynamic connectivity mask (PDCM) for this port to bring the port up as an E or TE port in a FICON VSAN.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message FICON-3-E_UNASSIGN_NO_PN_FAIL: [chars].Explanation Only port number already assigned can be removed.
Recommended Action Check port numbers in the configuration.
Introduced Cisco MDS SAN-OS Release 3.0(1).
FICON-5
Error Message FICON-5-STARTING: FICON manager process starting.Explanation FICON manager process is being started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FICON-6
Error Message FICON-6-PDCM_CHANGE: VSAN [dec] port-address [dec] prohibit mask set to [chars].Explanation The FICON prohibit dynamic connectivity mask (PDCM) for this port has changed. The VSAN port address PDCM is now set to the value shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(3).
Error Message FICON-6-PORT_SWAP: port number [dec] [dec] swapped.Explanation FICON port numbers swapped.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FICON-6-VSAN_DISABLED: FICON disabled on VSAN [dec].Explanation FICON has been disabled on the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message FICON-6-VSAN_ENABLED: FICON enabled on VSAN [dec].Explanation FICON has been enabled on the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
FLOGI Messages
This section contains the fabric login (FLOGI) messages.
FLOGI-5
Error Message FLOGI-5-MSG_IF_REINIT_ALPA_CONFLICT: [VSAN [dec], Interface [chars]] FL/TL interface [chars] re-initialized as ALPA - PWWN map conflict occurred.Explanation The FL or TL interface reinitialized as an arbitrated loop physical address (ALPA) and now conflicts with an existing fabric login (FLOGI) session after the Loop Initialization Protocol (LIP). All devices will log in again with new ALPA and pWWN mapping.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message FLOGI-5-MSG_PORT_LOGGED_IN: [VSAN [dec], Interface [chars]] Nx Port [chars] with fcid [chars] logged IN.Explanation Nx port logged in with the specified information.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FLOGI-5-MSG_PORT_LOGGED_OUT: [VSAN [dec], Interface [chars]] Nx Port [chars] logged OUT.Explanation Nx port logged out.
Recommended Action Enter the show interface, show VSAN, or show module command (or use an equivalent Fabric Manager/Device Manager procedure) to help determine why this Nx port logged out. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF Messages
This section contains the Fabric Shortest Path First (FSPF) messages.
FSPF-2
Error Message FSPF-2-SHUTDOWN: Routing daemon shutting down : [chars].Explanation Fabric Shortest Path First (FSPF) routing daemon is shutting down because of the reason shown in the error message.
Recommended Action This is a severe problem. Provide the reason shown and the log files for Fabric Shortest Path First (FSPF) to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF-3
Error Message FSPF-3-BAD_FC2_PKT: Received bad FC2 packet on interface [chars] VSAN [dec] : [chars].Explanation Fabric Shortest Path First (FSPF) received a bad FC2 packet on the interface and VSAN shown in the error message. The error description is shown in the error message.
Recommended Action FSPF daemon has received a bad FC frame. Provide the output of the debug fc2 pkt CLI command to your customer service representative.You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-CHECKSUM_FAIL: Checksum test failed for LSR domain [dec] in VSAN [dec].Explanation Periodic database checksum test failed for LSR for the domain and VSAN shown in the error message.
Recommended Action This indicates that the internal database is corrupted because of some memory corruption problem. Provide the output of show fspf database to your customer service representative. You may need to power cycle the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-FC2_PROC_ERR: Error in processing [chars] packet on interface [chars] VSAN [dec], Error = [chars].Explanation An error occurred in processing the FC2 packet on the interface and VSAN shown in the error message. The internal error code is also shown in the error message.
Recommended Action Enter debug fspf error to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Provide the output of the show fspf vsan [vsan-id] and show fspf vsan[vsan-id] interface commands and the debug fspf fc pkt command results for the specific interface to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-FLOOD_ERR: Error in flooding the local LSR in VSAN [dec] , Error = [chars].Explanation Fabric Shortest Path First (FSPF) had an error in flooding the local LSR in VSAN shown in the error message. The error description is shown in the error message.
Recommended Action Provide the output of the debug fspf flood and debug fspf error CLI commands. If an error is reported in transmitting a packet, check if the interface is up and then enter the debug fc2 error CLI command.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-HELLO_MISMATCH: Mismatch in [chars] in the Hello packet on interface [chars] in VSAN [dec].Explanation There is a mismatch in the entry in the hello packet received on the interface and VSAN shown in the error message. The packet will be dropped.
Recommended Action Check the configuration of the the hello or dead interval on the switches on the two ends of the interface to see if there is a mismatch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-INTF_TIMER_ERR: Error in processing interface timer event [chars] for interface [chars] in VSAN [dec] , error = [chars].Explanation Fabric Shortest Path First (FSPF) had an error processing a timer event for the named interface. The error is shown in the error message.
Recommended Action Provide the output of the debug fspf error command to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-IPC_PROC_ERR: Error in processing IPC message : Opcode = [dec], Error code = [hex].Explanation Fabric Shortest Path First (FSPF) had an error processing a message (opcode shown in the error message). The internal error code is shown in the error message.
Recommended Action An incorrect IPC message may have been received by FSPF. Provide the output of the debug fspf mts pkt and debug fspf error CLI command to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-LOCK_FAIL: FSPF failure in gaining lock.Explanation There is a problem with locking a shared resource between Fabric Shortest Path First (FSPF) threads.
Recommended Action Provide the output of the debug fspf all CLI command to your customer service representative.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FSPF-3-MTS_MSG_BEFORE_GSYNC: FSPF in standby received MTS message opcode = [hex] before GSYNC.Explanation Fabric Shortest Path First (FSPF) in standby received a messaging and transaction service (MTS) message before receiving the GSYNC message.
Recommended Action Provide the output of the debug fspf mts pkt command to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-RIB_ERR: Error in RIB : [chars].Explanation Fabric Shortest Path First (FSPF) had an error in interacting with the routing information base (RIB). The error description is shown in the error message.
Recommended Action Enter show processes to check if RIB application is running. Provide the output of the debug fspf route command and RIB debug traces to your customer service representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-ROUTE_COMPUTE_ERR: Error in computing or sending routes for VSAN [dec] : Error = [chars].Explanation Fabric Shortest Path First (FSPF) had an error in computing routes for the VSAN. The error description is shown in the error message.
Recommended Action Provide the error code and the output of the debug fspf error and debug fspf route CLI commands if the problem is reproducible.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-3-UNLOCK_FAIL: FSPF failure in releasing lock.Explanation Cannot release the lock on the shared resource between Fabric Shortest Path First (FSPF) threads.
Recommended Action Provide the output of the debug fspf all CLI command to your customer support representative.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message FSPF-3-VSAN_TIMER_ERR: Error in processing VSAN timer event [chars] for VSAN [dec] , error description = [chars].Explanation Fabric Shortest Path First (FSPF) had an internal error in processing timer event for the VSAN. The error description is shown in the error message.
Recommended Action Provide the output of thedebug fspf error CLI command to your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF-4
Error Message FSPF-4-FC2_DOWN_INTF: Received FC2 packet on DOWN interface [chars] in VSAN [dec].Explanation Fabric Shortest Path First (FSPF) received a FC2 packet on inactive interface in the VSAN shown in the error message.
Recommended Action This message may be printed for the first FSPF packet when an interface is brought up. If the message is seen continuously, check if FSPF is disabled on one end for the interface or the VSAN. Otherwise, enter the show interface command to see if the interface is physically up only on one side. Also check if there is any error message printed for IPC_PROC_ERR.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-4-FC2_DOWN_VSAN: Received FC2 packet on inactive VSAN [dec].Explanation Fabric Shortest Path First (FSPF) received a FC2 packet on the inactive VSAN.
Recommended Action If this message is seen continuously, check if FSPF is disabled on the VSAN. Investigate whether the VSAN is active and a valid domain is assigned on the switch. Also check if the IPC_PROC_ERR message is printed in the message logs.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-4-ILLEGAL_FSM_EVENT: Illegal FSM event for state [chars] in interface [chars] in VSAN [dec].Explanation An illegal protocol event has occurred for the Fabric Shortest Path First (FSPF) state machine. The old state is shown in the error message for the interface and VSAN.
Recommended Action It is possible to get this message if a protocol packet gets dropped, but FSPF should recover and move back to FULL state. Enter show fspf interface to check the state of the interface. If it is stuck in a state other than full, provide the output the of debug fspf event and debug fspf fc pkt CLI commands for the interfaces involved to your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-4-LSR_DROPPED: [chars], Dropping LSR [dec] received on interface [chars] in VSAN [dec].Explanation An LSR packet is dropped because of the reason shown in the error message. LSR belonged to the domain shown in the error message and was received on the interface and VSAN shown in the error message.
Recommended Action Provide the reason given for dropping the LSR and the output the of debug fspf fc pkt CLI command. If the reason is checksum failure, investigate for possible packet corruption or truncation. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-4-LSR_MIN_LS_ARRIVAL: Packet arrived before MIN_LS_ARRIVAL, Dropping LSR [dec] on interface [chars] in VSAN [dec].Explanation An LSR packet is dropped as it arrived before MIN_LS_ARRIVAL.LSR belonged to the domain shown in the error message and was received on the interface and VSAN shown in the error message.
Recommended Action This can occur in a transient situation; the protocol recovers by retransmitting the LSR. If the message is seen continuously, provide the output of the debug fspf flood, debug fspf retrans and debug fspf error CLI commands. The message may be seen more often when interoperating with other vendors. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-4-LSU_RX_INIT: Dropping LSU received in state INIT on interface [chars] in VSAN [dec].Explanation An LSU packet is dropped because the interface is in the initialization (INIT) state when it received the LSU.
Recommended Action This can occur in some transient situations. If the problem persists, provide the output of the show fspf VSAN [dec] interface and debug fspf fc pkt and debug fspf event VSAN [dec] commands to your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF-5
Error Message FSPF-5-STARTING: Routing daemon started.Explanation Fabric Shortest Path First (FSPF) routing daemon has been started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF-6
Error Message FSPF-6-ADD_LSR: New LSR added for domain [dec] in VSAN [dec].Explanation A new LSR is added to the database for the domain and VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-DELETE_LSR: LSR deleted for domain [dec] in VSAN [dec].Explanation The LSR for the domain is deleted from the database for VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-INTF_OPER_DOWN: Down on interface [chars] in VSAN [dec].Explanation Fabric Shortest Path First (FSPF) has become operationally down on the interface and VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-INTF_OPER_UP: Up on interface [chars] in VSAN [dec].Explanation Fabric Shortest Path First (FSPF) has become operational on the interface and VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-MAX_AGE: LSR [dec] in VSAN [dec] reached Maxage.Explanation The LSR for the domain and VSAN shown in the error message reached the maximum age and will be deleted from all the connected switches.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-ROLLOVER: Rolling over the incarnation number of Local LSR of VSAN [dec].Explanation The incarnation number of local LSR in the VSAN shown in the error message reached the maximum value and is rolling over.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-SELF_ORIGINATED: Received local LSR in VSAN [dec] with higher incarnation number.Explanation An LSR for the local domain was received in the VSAN shown in the error message with an incarnation number higher than the one in the database. This situation should only occur initially on a topology change. If the situation persists, the domain assignment of switches may not be unique.
Recommended Action If this message is received continuously, check if the domain assignment is unique in the fabric.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-STATE_CREATED: Internal state created [chars].Explanation Fabric Shortest Path First (FSPF) has created its internal state stateless or stateful condition shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-VSAN_OPER_DOWN: Down on VSAN [dec].Explanation Fabric Shortest Path First (FSPF) has become operationally down on the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message FSPF-6-VSAN_OPER_UP: Up on VSAN [dec] with local domain [dec].Explanation Fabric Shortest Path First (FSPF) has started on the VSAN with the local domain shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
FSPF-7
Error Message FSPF-7-ROUTE_THREAD_STARTED: Thread number [dec] started.Explanation Route computation thread number shown in the error message has been started for Fabric Shortest Path First (FSPF).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IKE Messages
This section contains the Internet Key Exchange (IKE) messages.
IKE-3
Error Message IKE-3-CRYPTO_INIT_ERROR: IKEv2 crypto init error: [chars].Explanation Cryptographic initialization error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-ENABLE_ERROR: Unable to store enable flag in configuration (error-id [hex]).Explanation The Internet Key Exchange (IKE) service failed to store the enable flag in the configuration. As a result, IKE will exit.
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.0(1b).
Error Message IKE-3-FIPS_MODE_ERROR: Could not set FIPS mode.Explanation The FIPS mode could not be set by IKE.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IKE-3-MAX_HALF_CONN_LIMIT_REACHED: IKEv1 : Exceeded the limit for number of half open Phase 1 connections.Explanation The number of half open connections has exceeded the maximum limit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(3).
Error Message IKE-3-PHASE1_NEGOTIATION_FAILED: IKEv1: Phase 1 negotiation failed for peer [chars].Explanation The Internet Key Exchange (IKE) policy negotiation failed for the peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-PHASE1_PROPOSAL_MISMATCH: IKEv1: No matching phase 1 proposal found for peer [chars].Explanation There is an Internet Key Exchange (IKE) policy mismatch for the peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-PHASE2_NEGOTIATION_FAILED: IKEv1: Phase 2 negotiation failed for peer [chars].Explanation IPsec policy negotiation failed for the peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-PHASE2_PROPOSAL_MISMATCH: IKEv1: No matching phase 2 proposal found for peer [chars].Explanation There is an IPsec policy mismatch for the peer.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-IKE_PROGRAM_EXIT: [chars].Explanation The Internet Key Exchange (IKE) process experienced an abnormal exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-3-UNSUPPORTED_EXCHANGE: IKEv1: Unsupported exchange [dec] received from [chars].Explanation An unsupported Internet Key Exchange (IKE) was received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IKE-4
Error Message IKE-4-INVALID_PAYLOAD_APPEAR: IKEv2 received message (from [chars]) with payload ([chars]) appeared in [chars]([chars]).Explanation Internet Key Exchange (IKE) received a payload in an inappropriate exchange.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-4-MESSAGE_ERROR: IKEv2 message (from [chars]) message error: [chars].Explanation Internet Key Exchange (IKE) received a malformed message that does not adhere to the IKE protocol.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-4-PARSING_ERROR: IKEv2 message (from [chars]) parsing error: [chars].Explanation Internet Key Exchange (IKE) received a malformed message that cannot be parsed appropriately.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-4-UNKNOWN_PAYLOAD: IKEv2 received message (from [chars]) with un-recognized payload ([chars]).Explanation Internet Key Exchange (IKE) received an invalid payload.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IKE-4-UNSUPPORT: [chars] is not supported (message from [chars]).Explanation Internet Key Exchange (IKE) received something unsupported.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IKE-6
Error Message IKE-6-POLL_START_DONE: IKE is exiting since it is not enabled.Explanation Internet Key Exchange (IKE) is exiting because it has not been enabled in the configuration.
Recommended Action This is an informational message.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
ILC_HELPER Messages
This section contains the intelligent line card helper messages.
ILC_HELPER-2
Error Message ILC_HELPER-2-NO_LICENSE_REBOOT: Linecard [dec] will reboot now.Explanation The SSE license has expired; therefore, the line card will be rebooted.
Recommended Action Install the appropriate SSE license so you can use the Storage Services Module (SSM) features.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ILC_HELPER-3
Error Message ILC_HELPER-3-INVALID_BOOTVAR: Invalid [chars] boot variable configured. The linecard will come online in L2 mode.Explanation The boot variable is misconfigured to a wrong image. So the linecard comes online in normal L2 mode instead of L3 mode.
Recommended Action Configure a proper image for the target boot variable.
Introduced Cisco MDS SAN-OS Release 3.0(3).
ILC_HELPER-6
Error Message ILC_HELPER-6-LICENSE_VALID: A valid license for linecard [dec] has been obtained.Explanation A valid license has been obtained for the Storage Services Module (SSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ILC-SPAN Messages
This section contains the intelligent line card SPAN (ILC-SPAN) messages.
ILC-SPAN-3
Error Message ILC-SPAN-3-ERROR: [chars].Explanation The intelligent line card SPAN manager encountered an error.
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.0(1b).
IMAGE_DNLD Messages
This section contains the image download (IMAGE_DNLD) messages.
IMAGE_DNLD-SLOT#-2
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_COMPLETE: Module image download process. [chars].Explanation Image download completed. The module image is being installed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_FAILED: Module image download process failed. [chars].Explanation The add-on image download to the module failed. This module is not operational until an add-on image has been successfully installed.
Recommended Action Verify the location and version of your module image. Enter install module CLI command or use a similar Fabric Manager/Device Manager procedure to download a new module image.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_STARTED: Module image download process. [chars].Explanation The add-on image download started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_SUCCESSFUL: Module image download process. [chars].Explanation The add-on image download and install successful.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_COMPLETE: Module image download process. [chars].Explanation The image download completed. The module image is being installed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FAILED: Module image download process. [chars].Explanation The image download failed. The module may be inoperable.
Recommended Action Enter the show module CLI command or use a similar Fabric Manager/Device Manager procedure to verify the state of this module. Enter the install module CLI command or use a similar Fabric Manager/Device Manager procedure to retry the image download.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_CHECK_ERROR: File System check failed: [chars].Explanation The file system consistency check failed.
Recommended Action Use the fsck command to repair the file system. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_RECREATION: File System checking and recreation. [chars].Explanation File system checking and recreation if necessary for /images.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_STARTED: Module image download process. [chars].Explanation The image download started. The module image downloads are nondisruptive to module operation.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IMAGE_DNLD-SLOT#-5
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_COMPLETE: Addon module image download process completed. [chars].Explanation The add-on image download to the module has completed. The module should now be installing this new image.
Recommended Action This message is informational only.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_STARTED: Addon module image download process started. [chars].Explanation The add-on image download to the module has started. This is a disruptive download and this module will be inoperable until this download process is complete.
Recommended Action This message is informational only.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_SUCCESSFUL: Addon module image download and install process successful. [chars].Explanation The add-on image download and install to the module is successful.
Recommended Action Enter show module to verify the module's operational status.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IMAGE_UPGRADE Messages
This section contains the image upgrade (IMAGE_UPGRADE) messages.
IMAGE_UPGRADE-SLOT#-2
Error Message IMAGE_UPGRADE-SLOT#-2-IMAGE_UPGRADE_ERROR: [chars].Explanation An image upgrade error has occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IMAGE_UPGRADE-SLOT#-6
Error Message IMAGE_UPGRADE-SLOT#-6-IMAGE_UPGRADE_INFO: [chars].Explanation The image upgrade information is shown.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPACL Messages
This section contains the IP access control list (IP-ACL) messages.
IPACL-0
Error Message IPACL-0-EMERG: [chars].Explanation IP-ACL caused a system failure.
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.2(2a).
IPACL-1
Error Message IPACL-1-ALERT: [chars].Explanation The IP access control list caused failures in other services.
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.2(2a).
Error Message IPACL-2-CRIT: [chars].Explanation The IP access control list encountered a catastrophic error.
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.2(2a).
IPACL-3
Error Message IPACL-3-ERR: [chars].Explanation The IP access control list encountered an error.
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.2(2a).
IPACL-4
Error Message IPACL-4-WARN: [chars].Explanation The IP access control list ignored an unexpected condition.
Recommended Action Enter debug ipacl all, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPACL-5
Error Message IPACL-5-NOTE: [chars].Explanation The IP access control list does not support this operation.
Recommended Action Enter debug ipacl all, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPACL-6
Error Message IPACL-6-INFO: [chars].Explanation An IP access control list event occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPCONF Messages
This section contains the IP configuration manager (IPCONF) messages.
IPCONF-2
Error Message IPCONF-2-ALLOC_MEMORY: Memory allocation failed.Explanation The IP configuration manager failed to allocate a block of dynamic memory.
Recommended Action Check if the system is low on memory; if so reset the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPCONF-3
Error Message IPCONF-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error: [chars].Explanation The IP configuration manager failed to write to a file. This is probably because the file sytem is full.
Recommended Action Check the file systems and remove unnecassary files.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPCONF-3-INIT_FAILED: Initialization failed. Component [chars].Explanation The service failed to start. The failure is initializing the component shown in the error message.
Recommended Action Enter show process to check the status of the other processes. Debug the specified component.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPCONF-4
Error Message IPCONF-4-DAD_FAILED_EVENT: Duplicate address detection failed for [chars] on [chars].Explanation Duplicate address detection for IP address failed.
Recommended Action Check the IP addresses and correct any duplicates.
Introduced Cisco MDS SAN-OS Release 3.0(1).
IPCONF-6
Error Message IPCONF-6-CONFIG_EVENT: IP Configuration Msg:.Explanation An IP configuration event occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPCONF-6-INTERFACE_DELETED: The interface [chars] has been deleted.Explanation The specified interface has been deleted. The service will delete all the configuration in that interface.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPCONF-6-INTERFACE_EVENT: IP address [chars] [chars] on interface [chars].Explanation The IP address has been successful in handling the condition shown in the error message for the interface shown.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPCONF-6-ROUTE_NOT_ACTIVE: The [chars] is not active.Explanation The specified route is successfully configured but currently is not active.
Recommended Action Check that the route is correct and the outgoing interface is operationally up.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPCONF-6-STARTING: IP configuration Manager started.Explanation The IP configuration manager service has successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPFC Messages
This section contains the IP over Fibre Channel (IPFC) messages.
IPFC-2
Error Message IPFC-2-ALLOC_MEMORY: Memory allocation failed.Explanation The service failed to allocate a block of dynamic memory.
Recommended Action Check if the system is low on memory and reset the switch if necessary.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPFC-3
Error Message IPFC-3-INIT_FAILED: Initialization failed. Component [chars].Explanation The service failed to start. The failure occurred while initializing the component shown in the error message.
Recommended Action Enter show processes to check the status of the other processes,. Debug the specified component.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IPFC-3-IOCTL_FAILED: IOCTL failed.Explanation An IOCTL to the character device failed.
Recommended Action Enter show ipfc internal interface vsan for all the configured VSAN interfaces to check the internal status, and enter the show ipfc internal mip CLI command to check the internal status. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPFC-3-GENERIC_ERROR: Error: [chars]. Err_value: [dec].Explanation Error occurred while bringing a VSAN interface up or down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(2b).
Error Message IPFC-3-PSSERROR: [chars].Explanation IPFC manager encountered a PSS error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
IPFC-6
Error Message IPFC-6-CONFIG_EVENT: VSAN interface [dec] [chars].Explanation The specified VSAN interface successfully handled the condition shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPFC-6-STARTING: IP Over Fiber Channel service started.Explanation The service successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPFC-6-STATE_CHANGE: VSAN interface [dec] [chars].Explanation The specified VSAN interface is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
IPS Messages
This section contains the IP service (IPS) messages.
IPS-2
Error Message IPS-2-ISCSI_IPS_INIT: Ips initialization of [chars] [chars].Explanation The IP service (IPS) initialization 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 1.2(2a).
IPS-3
Error Message IPS-3-IPS_EGRESS_PERR: Parity error on dma-bridge egress. Count: [dec].Explanation Parity error occured in dma-bridge egress direction.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message IPS-3-FCIP_FTA_ACCEL_CHAIN_ABORTED: Exch Aborted FC oxid [hex] My oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] (Internal [hex]:[hex]).Explanation FICON tape acceleration exchange was discarded.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(3).
Error Message IPS-3-FCIP_FTA_DATA_SENSE: Sense data with ERA [hex] sent to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation Sense data with ERA sent.
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.0(1).
Error Message IPS-3-FCIP_FTA_ERA_35: ERA [hex] presented to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP got an ERA 35.
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.0(1).
Error Message IPS-3-FCIP_FTA_ERA_38: ERA 0x38 received CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] at tape capacity: [dec] MB.Explanation FCIP got an ERA 38.
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 IPS-3-FCIP_FTA_LOCATE_RBID_MISMATCH: Permanent Error due to Locate RBID Mismatch, CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec].Explanation FCIP-FTA received a permanent error.
Recommended Action This error message is informational. No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IPS-3-FCIP_FTA_PERM_ERR: Permanent Error, ERA [hex] rcvd CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] sense_byte[2,6]: [[hex], [hex]].Explanation FCIP-FTA received a permanent error.
Recommended Action This error message is informational. No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IPS-3-IPS_CRYPTO_FIPS_FAILED: IPS module [dec] has failed FIPS tests. FIPS info - [chars].Explanation FIPS error occurred in the IPS module.
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 IPS-3-IPS_FIPS_TEST_FAILED: IPS FIPS compliance test failed.Explanation IPS FIPS compliance test failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IPS-3-IPS_HIFN_CRYPTO_ENGINE_POST_FAILED: Crypto engine in the IPS module [dec] has failed POST tests. POST info - [chars].Explanation An error occurred in the crypto engine used in the IPS module.
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 IPS-3-IPS_INGRESS_PERR: Parity error on dma-bridge ingress. Count: [dec].Explanation Parity error occured in dma-bridge ingress direction.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message IPS-3-ISLB_CFS_CLEAR_FAILED: [chars].Explanation An error occurred while clearing the CFS lock. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_COMMIT_FAILED: [chars]; [chars].Explanation An error occurred while issuing a CFS commit. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_CONFIG_FAILED: [chars]; [chars].Explanation An error occurred while distributing the CFS config data. The reason for the failure is listed in the message.
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.
Error Message IPS-3-ISLB_CFS_LOCK_FAILED: [chars].Explanation An error occurred while acquiring the CFS lock. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_ACTIVATION_FAILED: [chars]; [chars].Explanation An error occurred while activating a merged configuration. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_CLEARED: [chars].Explanation Merge has been cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_COMMIT_FAILED: [chars]; [chars].Explanation An error occurred while committing the CFS merged config data. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_CONFIG_FAILED: [chars]; [chars].Explanation An error occurred while distributing the CFS merge config data. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_FAILED: [chars]; [chars].Explanation An error occurred while merging iSLB CFS fabrics. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_PRECOMMIT_FAILED: [chars]; [chars].Explanation An error occurred while pre-committing merge data. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGE_REQ_REJECTED: [chars].Explanation Merge request rejected.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-3-ISLB_CFS_PWWN_RESV_CLAIM_FAILED: [chars].Explanation PWWN reservation claim failed. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_MERGING_CONFIG_DB_FAILED: [chars]; [chars].Explanation An error occurred while merging the config data. The reason for the failure is listed in the message.
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.
Error Message IPS-3-ISLB_CFS_PRECOMMIT_FAILED: [chars]; [chars].Explanation An error occurred while pre-committing data. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_PWWN_RESV_RELEASE_FAILED: [chars].Explanation PWWN reservation release failed. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_UNLOCK_FAILED: [chars].Explanation An error occurred while releasing the CFS lock. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_CFS_VRRP_DIST_FAILED: [chars].Explanation An error occurred while distributing the VRRP CFS runtime data. The reason for the failure is listed in the message.
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.0(1).
Error Message IPS-3-ISLB_ZONE_ACTIVATION_FAILED: iSLB zoneset activation returned [hex] for VSAN [dec].Explanation iSLB zone set activation 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 3.0(1).
Error Message IPS-3-ISLB_ZONE_ACTIVATION_RETRY: iSLB zoneset activation returned [hex] for VSAN [dec].Explanation iSLB zone set activation failed because the zone server was busy.
Recommended Action Retry the iSLB zone set activation.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-3-ISLB_ZONE_NO_ACTIVE_ZONESET: iSLB zonset activation returned [hex] for VSAN [dec].Explanation iSLB zone set activation failed because there is no active zone set.
Recommended Action Activate a zone set in the specified VSAN and retry.
Introduced Cisco MDS SAN-OS Release 3.0(1).
IPS-4
Error Message IPS-4-FCIP_FTA_CFG_MISMATCH: [chars]: Mismatch in FCIP FICON Tape Acceleration configuration with peer.Explanation The FCIP FICON Tape Acceleration configuration does not match the peer's configuration.
Recommended Action Adjust the FCIP FICON tape acceleration configuration to be consistent with the peer.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-4-FCIP_FTA_VSAN_UPDATE_WARNING: FCIP FICON tape acceleration VSAN update had an error ([chars]) on interface [chars] causing a flap of the interface.Explanation The FCIP FICON tape acceleration VSAN configuration experienced an error when disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and re-enabled as a result of this error to ensure data integrity.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-4-FCIP_LICENSE_BIND_FAILED: Bind failed for [chars] due to [chars] for license failure; configuration accepted but bind failed.Explanation The FCIP configuration was accepted but the FCIP interface did not bind to a physical interface because the appropriate license was not available. If a license becomes available in the future, this FCIP interface will bind to a physical interface automatically.
Recommended Action Check the license state using either the CLI show license usage command or a similar Fabric Manager procedure. Acquire the necessary FCIP license.
Introduced Cisco MDS SAN-OS Release 3.0(1).
IPS-5
Error Message IPS-5-FCIP_BIND_FAILED: Bind failed for [chars] due to [chars] for [chars].Explanation The FCIP interface bind to the Ethernet port failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-FCIP_FTA_ALREADY_OFF: FTA Already Off, [chars] VSAN: [hex].Explanation FTA is already turned off.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_ALREADY_ON: FTA Already ON, [chars] VSAN: [hex].Explanation FTA is already turned on.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_CB_DOWN: FTA [chars] is DOWN.Explanation FTA is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_CB_UP: FTA [chars], is UP.Explanation FTA is up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_DISBAND_GRP_CMD: Disband Group message processed PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP disbanded a group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_ERA_90: ERA 90 rcvd CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP internal error generated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_EST_GRP_CMD: Path Group establised for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP established a Path Group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_INVALID_FRAME: INVALID FTA FRAME :[chars].Explanation Invalid FICON tape acceleration frame received.
Recommended Action Informational message. No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS1: RSCN Cleanup Pass1 [chars] FCID1: [hex] FCID2: [hex] VSAN: [hex].Explanation RSCN cleanup first pass is in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS2: RSCN Cleanup Pass2 [chars] FCID1: [hex] FCID2: [hex] VSAN: [hex].Explanation RSCN cleanup second pass is in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_RESIGN_GRP_CMD: Resign group processed for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP resigned a group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_RESP_3490: 3490 device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation Device type discovered is 3490.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_RESP_3590: 3590 device discovered by FCIP CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation Device type discovered is 3590.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_RESP_NOT_TAPE: Non-tape device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex].Explanation FCIP discovered a non-tape device.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_TURN_OFF_LAST_VSAN: FTA turned off for the Last VSAN, [chars] VSAN: [hex].Explanation FTA twas turned off for the last Vsan.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_TURN_OFF_NONLAST_VSAN: FTA turned off for the Non-Last VSAN, [chars] VSAN: [hex].Explanation FTA was turned off for the non-last Vsan.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_TURN_ON: Turn ON FTA, [chars] VSAN: [hex].Explanation FTA was turned on.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_FTA_WARNING: FTA Warning :[chars].Explanation Generic FTA Warning.
Recommended Action This error message is informational. No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IPS-5-FCIP_IF_CR_DEL: Interface [chars] [chars].Explanation The FCIP interface was created or deleted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-FCIP_NUM_TCP_CONNS_MISMATCH: [chars]: configured for 2 tcp connections but currently operating with 1 connection.Explanation The number of configured TCP connections do not match the number of connections currently up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-FCIP_RA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Read Acceleration capability with peer.Explanation The FCIP Tape Read Acceleration capability does not match the peer configuration.
Recommended Action Adjust the FCIP Tape Read Acceleration capability to be consistent with the peer.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_TA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Acceleration configuration with peer.Explanation The FCIP tape acceleration configuration does not match the configuration on the peer.
Recommended Action Adjust the FCIP tape acceleration configuration to be consistent with the peer.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPS-5-FCIP_TA_ITL_MISMATCH: [chars]: Mismatch in FCIP Write/Tape Acceleration software capability with peer.Explanation The FCIP Write/Tape Acceleration software capability does not match with peer's software capability.
Recommended Action Fix the FCIP software to be consistent with the peer.
NPV-2-NPV_EXITED: NPV process exited in file [chars]
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message IPS-5-FCIP_TSTAMP_CHK_FAILED: [chars]: Timestamp check failed on ingressing frames.Explanation The timestamp between local and remote sides exceeds the configured tolerance.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-IPS_TCP_PORT_IN_USE: Cannot bringup interface [chars], local port already in use.Explanation FCIP and iSCSI interfaces are trying to use the same local port.
Recommended Action Use different ports.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-ISCSI_BAD_DATA_DIGEST_CRC: iSCSI ingress data digest error from initiator [chars] alias [chars] S_ID [hex] to D_ID [hex].Explanation iSCSI ingress data digest CRC failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI session down from initiator [chars] alias [chars] ip [chars] to target [chars], reason: [chars].Explanation iSCSI session goes down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_CONN_DOWN_BATCH: [chars]: [dec] iSCSI sessions failed in last [chars], reason: [chars].Explanation The listed number of iSCSI sessions were down during the last interval for the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IPS-5-ISCSI_CONN_UP: [chars]: iSCSI session up from initiator [chars] alias [chars] ip [chars] to target [chars].Explanation An iSCSI session has come up and reached full-feature phase.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSI initiator [chars] alias [chars] ip [chars] target [chars]. FC session failed over to port [chars].Explanation The FC session for the iSCSI session failed over to a newly active port.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_SB_GET_TGT: iSCSI SB get [dec] targets, initiator [chars] alias [chars] ip [chars].Explanation iSCSI FCNS query response.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_SESSION_CREATE_REDIRECT: [chars]: iSCSI Session initiator [chars] target [chars] redirected to [chars]/[chars].Explanation iSCSI session create was redirected.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISCSI_SESSION_REDIRECT_TIMEOUT: iSCSI Session initiator [chars] to [chars] redirected to [chars] timeout.Explanation iSCSI session redirect has timed out.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-ISLB_CFS_SESSION_CLEARED: CFS Session Cleared.Explanation CFS session has been cleared by a user.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-FCIP_WA_CFG_MISMATCH: [chars]: Mismatch in FCIP Write Acceleration configuration with peer.Explanation The FCIP write acceleration configuration does not match the configuration on the peer.
Recommended Action Fix the FCIP write acceleration configuration to be consistent with the peer.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPS-5-IPS_IPACL_LOG_MSG: [chars].Explanation The message lists details of the packet dropped due to ACLs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI session down from [chars] [chars] to target [chars], reason: [chars].Explanation The iSCSI session going down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-ISCSI_CONN_UP: [chars]: iSCSI session up from [chars] [chars] to target: [chars].Explanation The iSCSI session came up and reached full-feature phase.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSIExplanation The Fibre Channel session for the iSCSI session failed over to newly active port.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS-5-ISCSI_SESSION_CREATE_FAILURE: [chars]: iSCSI Session initiator [chars] target [chars] create failed. [chars].Explanation The iSCSI session create failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-ISCSI_SESSION_DESTROY_FAILURE: [chars]: iSCSI Session initiator [chars] target [chars] destroy failed. [chars].Explanation The iSCSI session destroy failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS-5-PORT_IPCFG_FAILED: Cannot configure ip address for interface [chars].Explanation Cannot configure IPS port IP address.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SB_MGR_CORE_FAILED: Ethernet Processing core [chars] failed due to [chars].Explanation Ethernet processing core failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SFRAME_ENTITY_ID_MISMATCH: [chars]: special frame profile id mismatch.Explanation A special frame was received, and the destination profile ID does not match the local profile ID.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SFRAME_FABRIC_WWN_MISMATCH: [chars]: special frame fabric wwn mismatch.Explanation A special frame was received, and the source or destination fabric WWN does not match the local destination or source fabric WWN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SFRAME_IF_ADMIN_DOWN: [chars]: special frame recvd if down.Explanation A special frame was received and the interface is administratively down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SFRAME_IF_NOT_ENABLED: [chars]: special frame not enabled.Explanation A special frame was received and the interface special frame configuration is disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-5-SFRAME_INVALID_NONCE: [chars]: special frame response has invalid nonce for FCIP.Explanation Special frame response has a different server-specified data string (nonce) than was originally sent in the special frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-SFRAME_NOT_RECV: [chars]: special frame was not received by passive-side FCIP.Explanation Special frame was not received by the passive-side of the FCIP TCP tunnel within given time period.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-SFRAME_RESP_MISMATCH: [chars]: special frame response has byte mismatch for FCIP.Explanation Special frame response has a mismatch in one of the bytes from what was sent from the FCIP special frame sender.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IPS-5-SFRAME_RESP_NOT_RECV: [chars]: special frame response was not received by active-side FCIP.Explanation Special frame response was not received by the active-side of the FCIP TCP tunnel within given time period.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
IPS-7
Error Message IPS-7-ISCSI_FCNS_QUERY_REQ: return [hex], wait [dec], VSAN [dec], Init: [chars].Explanation The iSCSI Fibre Channel name server (FCNS) query details are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-7-ISCSI_FCNS_QUERY_RESP: result [hex], [dec] tgts, wait [dec], Init: [chars].Explanation The iSCSI Fibre Channel name server (FCNS) query response details are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-7-ISCSI_SB_GET_TGT: iSCSI SB get [dec] tgts, Init: [chars] [chars].Explanation The iSCSI Fibre Channel name server (FCNS) query response details are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IPS-7-ISNS_SVR_ERR_RESPONSE: isns server returned following error code on isns request for interface [chars] : [dec].Explanation The Internet Storage Name Service (iSNS) server returned an error for a register or deregister request. For select error codes, the ISNS client would retry and re-register all target nodes corresponding to the interface.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
IPS_SB_MGR Messages
This section contains the IP Storage services sibyte manager (IPS_SB_MGR) messages.
IPS_SB_MGR-SLOT#-2
Error Message IPS_SB_MGR-SLOT#-2-NODE_CORE_NOT_RESPONDING: [Node [dec], Core [dec]]: Not responding to heartbeats, state=[hex].Explanation The node is not sending heartbeats periodically.
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(2a).
Error Message IPS_SB_MGR-SLOT#-2-NODE_NOT_RESPONDING: [Node [dec], Core [dec]] : Not responding to heartbeats.Explanation Node manager is not receiving heartbeat responses from the node.
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(2a).
Error Message IPS_SB_MGR-SLOT#-2-NODE_REIMAGE_PREPARE_FAIL: [Node [dec]]: Disk formatting failed during node install.Explanation There was a problem during the partitioning of the disk and creation of the file systems during the node install.
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(2a).
Error Message IPS_SB_MGR-SLOT#-2-PORT_SOFTWARE_FAILURE: Port software failure, module [dec] port [dec].Explanation The software servicing the data path on the port failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IPS_SB_MGR-SLOT#-2-SB0_REIMAGE_PREPARE_FAIL:Sibyte0 reimage disk formatting failed.Explanation There was a problem during the partitioning of the disk and the creation of file systems during reimage.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-2-SB1_REIMAGE_PREPARE_FAIL:Sibyte1 reimage disk formatting failed.Explanation There was a problem during the partitioning of the disk and the creation of file systems during reimage.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-2-SIBYTE_CORE0_NOT_RESPONDING:Sibyte [dec] Core0 is not responding to heartbeats, state=0x[hex].Explanation The code of core-0 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte 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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-2-SIBYTE_CORE1_NOT_RESPONDING:Sibyte [dec] Core1 is not responding to heartbeats, state=0x[hex].Explanation The code of core-1 is not incrementing heartbeats.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-2-SIBYTE_NOT_RESPONDING:Sibyte is not responding to heartbeats.Explanation The code of either core-0 or core-1 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte 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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
IPS_SB_MGR-SLOT#-3
Error Message IPS_SB_MGR-SLOT#-3-COMP_FAILURE: Heartbeat failure in compression engine (error [hex]).Explanation The compression engine did not respond to heartbeats because of some failure. The compression engine will be restarted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPS_SB_MGR-SLOT#-3-CRYPTO_FAILURE: Heartbeat failure in encryption engine (error [hex]).Explanation The encryption engine did not respond to heartbeats because of some failure. The encryption engine will be restarted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IPS_SB_MGR-SLOT#-3
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_ADD_ON: svc-node[dec] image is not compatible with svclc image.Explanation The SAN Volume Controller (SVC) image on the node is not compatible with the add-on image running on the line card.
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(2a).
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_CURRENT: svc-node[dec] image is not compatible with current node image.Explanation The new SAN Volume Controller (SVC) image is not compatible with the SVC image currently running on the node.
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(2a).
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_SUP: svc-node[dec] image is not compatible with system image.Explanation The SAN Volume Controller (SVC) image on the node is not compatible with the supervisor image.
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(2a).
Error Message PS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_ADD_ON:Sibyte0 is not compatible with add on.Explanation The code of sibyte0 is not compatible with the add-on image running on the line card.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_SB:Sibyte0 is not compatible with current sibyte image.Explanation The new code of sibyte0 is not compatible with the running sibyte image.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_SUP:Sibyte0 is not compatible with supervisor.Explanation The code of sibyte0 is not compatible with the supervisor image.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_ADD_ON:Sibyte1 is not compatible with add on.Explanation The code of sibyte1 is not compatible with the add on image running on the line card.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_SB:Sibyte1 is not compatible with current sibyte image.Explanation The new code of sibyte1 is not compatible with the running sibyte image.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_SUP:Sibyte1 is not compatible with supervisor.Explanation The code of sibyte1 is not compatible with the supervisor image.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
IPS_SB_MGR-SLOT#-6
Error Message IPS_SB_MGR-SLOT#-6-SBMGR_EVENT: Sbmgr event: [chars].Explanation This is an event log of the sibyte manager relating to a port or node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-6-SBMGR_SDWRAP:Sbmgr sdwrap: [chars].Explanation This is for messages from the sibyte manager on the line card to the supervisor system messages log.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(2a).
Error Message IPS_SB_MGR-SLOT#-6-SIBYTE_NOT_RESPONDING: Sibyte is not responding to heartbeats.Explanation The code of either core-0 or core-1 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte 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.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
IPsec Messages
This section contains the IPsec messages.
IPsec-2
Error Message IPSEC-2-IPSEC_INIT: IPSec initialization of [chars] [chars]Explanation IPsec initialization 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.0(1b).
Error Message IPSEC-2-IPSEC_SPD_OVERFLOW_DUE_TO_ACL: SPD Overflow on interface due to IP ACL [chars] bound to crypto map [chars] [dec].Explanation Modifying IP-ACL caused the security policy database on the interface to overflow. The IP-ACL filter was not applied to the security policy database.
Recommended Action Remove the IP-ACL change.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IPsec-3
Error Message IPSEC-3-14_2_MODULE_PACKETS_DROPPED: [chars]: packets were dropped in the module.Explanation The 14/2-port Multiprotocol Services (14/2-MPS) module dropped packets.
Recommended Action Enter the show ipsec internal crypto-acc interface gigabit <slot/port> CLI command or use a similar Fabric Manager/Device Manager procedure to collect drop statistics. 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.0(2b).
Error Message IPSEC-3-IPSEC_FIPS_TEST_FAILED: IPSEC FIPS compliance test failed.Explanation IPsec FIPS compliance test failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IPSEC-3-IPSEC_MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars].Explanation Failed to send a message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IPsec-5
Error Message IPSEC-5-IPSEC_CMS_IF_ACL_UPDATED: IP ACL [chars] updated while Crypto map [chars] [dec] bound to interface(s).Explanation IP-ACL was updated while it is mapped to a crypto map that is bound to an interface(s).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-5-IPSEC_DISABLED: IPSec Disabled.Explanation IPsec is disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-5-IPSEC_DISABLED_LIC_EXPIRED: IPSec Disabled due to License Expiry.Explanation IPsec is disabled because the license expired.
Recommended Action Install an updated, valid license to continue using this feature.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IPSEC-5-IPSEC_ENABLED: IPSec Enabled.Explanation IPsec is enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IPsec-6
Error Message IPSEC-6-IPSEC_TUNNEL_CREATED: [chars]: IPSec tunnel created: local_ip: [chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: [chars]/[chars].Explanation IPsec tunnel created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-6-IPSEC_TUNNEL_DELETED: [chars]: IPSec tunnel deleted: local_ip: [chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: [chars]/[chars].Explanation IPsec tunnel deleted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-6-IPSEC_TUNNEL_REKEYED: [chars]: IPSec tunnel rekeyed: local_ip: [chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: [chars]/[chars].Explanation IPsec tunnel rekeyed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IPsec-7
Error Message IPSEC-7-IPSEC_SA_CREATED: [chars]: IPSec SA created: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]).Explanation An IPsec security association (SA) was created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-7-IPSEC_SA_DELETED: [chars]: IPSec SA deleted: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]), reason: [chars].Explanation An IPsec security association (SA) was deleted.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Recommended Action No action is required.
Error Message IPSEC-7-IPSEC_SA_REKEYED: [chars]: IPSec SA rekeyed: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]).Explanation An IPsec security association (SA) was rekeyed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IPSEC-7-IPSEC_TUNNEL_REKEYED: [chars]: IPSec tunnel rekeyed: local_ip: [chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: [chars]/[chars].Explanation IPsec tunnel rekeyed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
ISAPI Messages
This section contains the intelligent switch application programming interface (ISAPI) messages.
ISAPI-SLOT#-0
Error Message ISAPI-SLOT#-0-ILC_EMERG: [chars].Explanation This is an intelligent switch API emergency software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-0-INVISTA_EMERG: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-0-NSP_EMERG: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-0-SSM_EMERG: [chars].Explanation This is an intelligent switch API emergency software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message ISAPI-SLOT#-0-SSM_EMERG: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
ISAPI-SLOT#-1
Error Message ISAPI-SLOT#-1-ILC_ALERT: [chars].Explanation This is an intelligent switch API alert software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-1-INVISTA_ALERT: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-1-NSP_ALERT: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-1-SSM_ALERT: [chars].Explanation This is an intelligent switch API alert software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message ISAPI-SLOT#-1-SSM_ALERT: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
ISAPI-SLOT#-2
Error Message ISAPI-SLOT#-2-ILC_CRIT: [chars].Explanation This is an intelligent switch API critical software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-2-INVISTA_CRIT: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-2-NSP_CRIT: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-2-SSM_CRIT: [chars].Explanation This is an intelligent switch API critical software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message ISAPI-SLOT#-2-SSM_CRIT: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
ISAPI-SLOT#-3
Error Message ISAPI-SLOT#-3-ILC_ERROR: [chars].Explanation This is an intelligent switch API error software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-3-INVISTA_ERROR: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-3-NSP_ERROR: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-3-SSM_ERROR: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-3-SSM_ERROR: [chars].Explanation This is an intelligent switch API error software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ISAPI-SLOT#-4
Error Message ISAPI-SLOT#-4-ILC_WARN: [chars].Explanation This is an intelligent switch API warning software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-4-INVISTA_WARN: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-4-NSP_WARN: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-4-SSM_WARN: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-4-SSM_WARN: [chars].Explanation This is an intelligent switch API warning software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ISAPI-SLOT#-5
Error Message ISAPI-SLOT#-5-ILC_NOTICE: [chars].Explanation This is an intelligent switch API notice software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-5-INVISTA_NOTICE: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-5-NSP_NOTICE: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-5-SSM_NOTICE: [chars].Explanation Isapi software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-5-SSM_NOTICE: [chars].Explanation This is an intelligent switch API notice software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ISAPI-SLOT#-6
Error Message ISAPI-SLOT#-6-ILC_INFO: [chars].Explanation This is an intelligent switch API informational software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-6-INVISTA_INFO: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-6-NSP_INFO: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-6-SSM_INFO: [chars].Explanation This is an intelligent switch API informational software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ISAPI-SLOT#-7
Error Message ISAPI-SLOT#-7-ILC_DEBUG: [chars].Explanation This is an intelligent switch API debug software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ISAPI-SLOT#-7-INVISTA_DEBUG: [chars].Explanation Isapi-invista software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-7-NSP_DEBUG: [chars].Explanation Isapi-nsp software messages.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ISAPI-SLOT#-7-SSM_DEBUG: [chars].Explanation This is an intelligent switch API debug software message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
ISNS Messages
This section contains the Internet Storage Name Service (ISNS) messages.
ISNS-2
Error Message ISNS-2-ISNS_CFS_OPERATION_FAILED: iSNS CFS [chars] failed.Explanation iSNS CFS operation 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 3.0(1).
Error Message ISNS-2-ISNS_INIT: iSNS initialization of [chars] [chars].Explanation Internet Storage Name Service (ISNS) initialization failed. ISNS is automatically restarted.
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.0(1b).
IVR Messages
This section contains the inter-VSAN routing (IVR) messages.
IVR-2
Error Message IVR-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars] was lost in the middle of an active CFS session. Abort the CFS session and re-enter the configuration changes.Explanation Due to port flaps (enable and disable of the VSAN), link outages, switch restarts and so on, a CFS peer switch of IVR was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync. with this peer. We recommend that you discard this CFS session using ivr abort command and then re-enter the configuration changes. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.
Recommended Action No action is required.
Error Message IVR-2-DEVICE_FCID_REWRITE_FAILURE: Failure while programming FCID rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able to communicate with its peer devices.Explanation Device failed to program the FC ID rewrite entries; this probably occurred because the hardware ran out of FC ID rewrite entries. This can happen if there are too many devices in an inter-VSAN routing (IVR) zone, or there are too many local VSANs in the VSAN topology.
Recommended Action Reduce the number of devices involved in inter-VSAN routing (IVR) in the active IVR zone set. Also, reduce the number of redundant transit VSANs, if any.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-2-DEVICE_ON_WRONG_NATIVE_AFID_VSAN: Device with port WWN [chars] (FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec].Explanation Device has come online on a different AFID/VSAN from the configured native AFID/VSAN, or the device does not satisfy unique domain criteria.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-2-DEVICE_ON_WRONG_NATIVE_VSAN: Device with port WWN [chars] (FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because domain [hex] exists in VSAN [dec].Explanation Device has come online on a VSAN different from the configured native VSAN, or the device does not satisfy unique domain criteria.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-DEVICE_STATE_INCOMPATIBLE_WITH_NAT_MODE: State for device with port WWN [chars] could not be restored because it was incompatible with the current NAT mode([dec]). This probably happened because NAT mode was modified without completely deactivating the active IVR zoneset.Explanation This can happen if the Network Address Translation (NAT) mode is modified without completely deactivating the active inter-VSAN routing (IVR) zone set.
Recommended Action Reboot the switch.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-2-DEVICE_VSAN_REWRITE_FAILURE: Failure while programming VSAN rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able to communicate with its peer devices.Explanation Device failed to program the VSAN rewrite entries, probably because the hardware ran out of VSAN rewrite entries. This can happen if there are too many devices in an inter-VSAN zone or too many local VSANs in the VSAN topology.
Recommended Action Reduce the number of domains involved in IVR by moving the members of the active IVR zone set to fewer switches. Also, reduce the number of redundant transit VSANs, if any.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-DOMAIN_DISALLOWED_IN_INTEROP: Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is disallowed in the interop mode for VSAN [dec].Explanation VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. Refer to the Cisco MDS 9000 Family CLI Configuration Guide or Cisco MDS 9000 Family Fabric Manager Configuration Guide for details on the domain range limitations.
Recommended Action Change the domain of the switch to which this IVR zone member is connected so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using the fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fcdomain's allowed-domains interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-DOMAIN_UNAVAILABLE: Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec].Explanation Device with the port WWN and FC ID shown in the error message may not be able to participate in the inter-VSAN zone because the domain shown is already assigned in a VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-INTEROP_MODE_2_OR_3_BF_FAILED: [chars] VSAN [dec] Virtual Domain [chars].Explanation Build fabric failed in VSAN [dec]. The build fabric was initiated to remove an unused virtual domain from the fcdomain list in that VSAN. The virtual domain still remains in the fcdomain list and hence it would not be available in that VSAN for assignment.
Recommended Action Perform a manual build fabric using fcdomain's interface if you would like to remove the unused virtual domain(s) from the fcdomain list.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message IVR-2-INTEROP_MODE_2_OR_3_RDI_FAILED: VSAN [dec], requested domain [chars], received domain [chars] sWWN [chars]. Return Code [chars].Explanation Request domain identifier (RDI) failed to allocate virtual domain in the VSAN. Received another domain instead, as shown in the error message. IVR-members connected to a third-party switch may not participate in IVR communications. It is likely that the domain requested in the IVR RDI command is already in use.
Recommended Action Reassign the domains so that the domain requested by RDI does not overlap any existing domain in that VSAN.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message IVR-2-IVR_ASSERTION_FAILED: Unexpected assertion failure in File [chars] at Line [dec].Explanation The inter-VSAN routing code shows an assertion failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-2-IVR_DISABLE_FAILED: Inter-VSAN Routing disable failed for reason: [chars].Explanation Inter-VSAN routing disable failed for the reason shown in the error message. Cleanup might not have completed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-IVZS_ACTIVATION_FAILED_RETRYING: Inter-VSAN zoneset activation failed in VSAN [dec] : [chars]. retrying after [dec] seconds.Explanation Inter-VSAN zone set activation failed in the listed VSAN. This could be an intermittent, regular zone set activation error. The activation will be retried after the number of seconds listed in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IVR-2-NO_LICENSE_SHUTDOWN: Inter-VSAN Routing is shutting down.Explanation License required for continued IVR operation is not available. IVR is shutting down.
Recommended Action Install the appropriate license for IVR services and then enable IVR again.
Introduced Cisco MDS SAN-OS Release2.0(1b).
Error Message IVR-2-NO_LICENSE_WARNING: Inter-VSAN Routing would shutdown in [dec] seconds.Explanation License required for continued IVR operation is not available. Unless the required license is installed, IVR will shut down in the number of seconds shown in the error message. IVR configurations will be lost.
Recommended Action Install the appropriate license for IVR services within the shown seconds to continue uninterrupted operation.
Introduced Cisco MDS SAN-OS Release2.0(1b).
Error Message IVR-2-PERSISTENT_VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the configured persistent virtual domain/fcid could not be assigned.Explanation This can happen if the virtual domain/FC ID configured by the user is already in use (either by IVR or a switch) or not allowed because of the interop mode or allowed domain list configured.
Recommended Action Verify that the configured virtual domain/FC ID is allowed and available for use.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IVR-2-VIRTUAL_DOMAIN_CONFLICT: In VSAN [dec] virtual domain [dec] from native VSAN [dec] conflicts with native VSAN [dec] for the same virtual domain.Explanation The currently advertised virtual domain in the VSAN shown in the error message is native to different VSAN. This switch has learned of a device that is a member of the active IVR zone and has the same domain ID, but belongs to a different native VSAN. This device is not advertised in that VSAN until the domain conflict is resolved.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-2-VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the internally generated FCID conflicts with fcid assigned to WWN [chars]. Please configure fcid for WWN [chars] too.Explanation This can happen if the virtual domain/FCID internally configured is already in use by another active device.
Recommended Action Assign a different persistent virtual FCID.
Introduced Cisco MDS SAN-OS Release 3.2(1).
IVR-3
Error Message IVR-3-ACL_ERROR: ACL API, [chars], failed with error [hex].Explanation IVR invoked the ACL API and received an error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-ACL_PERMIT_ENTRY_ERROR: ACL permit entry update on interface [chars] failed for reason: [chars].Explanation ACL could not program permit entries for IVR traffic.The error message describes the interface named and the system error message from ACL. IVR traffic coming from the interface may be dropped.
Recommended Action If the problem persists, contact your support representative. 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(2a).
Error Message IVR-3-ACL_PLOGI_ENTRY_ERROR: PLOGI capture entry update in slot [dec] failed for reason: [chars].Explanation ACL could not program IVR. Port login (PLOGI) could not be programmed. The error message describes the line card slot number, and the error detected. PLOGI and its response may be dropped because the IVR process cannot capture those frames.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message IVR-3-AFID_CONFLICT: [chars].Explanation AFID configuration is different at different IVR-enabled switches in the same VSAN.
Recommended Action Change either the AFID configuration (auto mode) or the VSAN topology configuration (user mode) to make it consistent.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-3-CFS_INVALID_PAYLOAD_RECEIVED: Inter-VSAN process received invalid payload from CFS.Explanation Inter-VSAN process received invalid payload from CFS.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message IVR-3-CLEAR_FAILED: [chars].Explanation An error occurred while clearing the lock. The reason for the failure is shown in the error message.
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.0(1b).
Error Message IVR-3-COMMIT_FAILED: [chars].Explanation An error occurred while issuing a CFS commit. The reason for the failure is shown in the error message.
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.0(1b).
Error Message IVR-3-COMMIT_PARTIALLY_FAILED: [chars].Explanation An error occurred while committing the configuration. Configuration could not be committed on some switches. The reason for the failure is that the configuration is inconsistent in the fabric.
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 IVR-3-COMMIT_REJECTED: [chars].Explanation The commit request received from the remote switch is rejected. The reason for the failure is shown in the error message.
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 IVR-3-DDAS_LOCK_TIMER_EXPIRED: IVR database lock is released, as device-alias commit/abort notification is not received in the expected time frame.Explanation When device-alias sends the validation request, the IVR database is locked and a timer is started. For any reason, if device-alias commit/abort notification is not received within the expected time frame, the lock timer expires and the lock is released. If device-alias commit notification is received after the lock is released, the changes are not applied and this could cause inconsistency between IVR and device-alias.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IVR-3-DEVICE_NOT_PRESENT_IN_FB_DB_FICON: Device with port WWN [chars] could not be exported to VSANs [chars] because its native switch is not present in the current active fabric binding database of those VSANs.Explanation This happens if FICON is enabled on VSANs and native switch of device with port WWN is not present in the current active fabric binding database of those VSANs. This is a requirement for FICON compliance.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-DEVICE_ON_WRONG_NATIVE_AFID_VSAN: Device with port WWN [chars] (FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec].Explanation Device has come online on a AFID/VSAN different from the configured native AFID/VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-DEVICE_ON_WRONG_NATIVE_VSAN: Device with port WWN [chars] (FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because domain [hex] exists in VSAN [dec].Explanation Device has come online on a VSAN different from the configured native VSAN or the device does not satisfy unique domain criteria.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-DM_ERROR: Domain Manager API, [chars], failed with error [hex].Explanation IVR invoked the domain manager API and received an error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-DOMAIN_DISALLOWED_IN_INTEROP: Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is disallowed in the interop mode for VSAN [dec].Explanation VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. Refer to the Cisco MDS 9000 Family CLI Configuration Guide or Cisco MDS 9000 Family Fabric Manager Configuration Guide for details on the domain range limitations.
Recommended Action Change the domain of the switch to which this IVR zone member is connected so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fcdomain allowed-domains' interface.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-DOMAIN_UNAVAILABLE: Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec].Explanation Device with the named port WWN and FC ID may not be able to participate in Inter-VSAN zone because the named domain is already assigned in the named VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-FC2_ERROR: FC2 API [chars] failed with error [hex] for [chars].Explanation IVR invoked a Fibre Channel Layer 2 (FC-2) API for a socket and received an error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-INTERNAL_ERROR: Internal error: [chars].Explanation The IVR process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-FCID_REWRITE_REQUEST_TO_ACL_FAILED: fcid rewrite [chars] request vsan [dec] did [chars] sid [chars] failed:[chars].Explanation This happens either after IVR retried the request few times or ACL experienced error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED: qos iod undrop request vsan [dec] did [chars] failed:[chars].Explanation This happens either after IVR retried the request few times or ACL experienced error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-IVZ_ACTIVATION_FAILED: Inter-VSAN zoneset [chars] activation failed.Explanation Inter-VSAN zone set activation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-IVZ_ACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars] activation failed in VSAN [dec].Explanation Inter-VSAN zone set activation failed in the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-IVZ_DEACTIVATION_FAILED: Inter-VSAN zoneset [chars] deactivation failed.Explanation Inter-VSAN zone set deactivation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-IVZ_DEACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars] deactivation failed in VSAN [dec].Explanation Inter-VSAN zone set deactivation failed in the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-LOCK_FAILED: [chars].Explanation An error occurred while acquiring the lock. The reason for the failure is listed.
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.0(1b).
Error Message IVR-3-MERGE_FAILED: [chars].Explanation An error occurred while merging the configuration. The reason for the failure is shown in the error message.
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.0(1b).
Error Message IVR-3-MTS_ERROR: MTS message transmission failed with error [dec].Explanation IVR process unsuccessfully tried to send a messaging and transaction service (MTS) message. The messaging and transaction service (MTS) error number is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-NS_ERROR: FCNS API, [chars], failed with error [hex].Explanation IVR invoked the Fibre Channel name server (FCNS) API and received an error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars] failed with error [hex].Explanation IVR read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message describes the configuration that the process tried to restore and describes the system error code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-PSS_ERROR: PSS operation [chars] returned error: [hex].Explanation A persistent storage service error occurred. The error message specifies the context where the failure occurred and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex].Explanation IVR read the saved runtime database and encountered an error while rebuilding the runtime database. The error message describes the runtime database that the process tried to restore and shows the system error code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-RIB_ERROR: RIB API, [chars], failed with error [hex].Explanation IVR invoked the Routing Information Base (RIB) API and received an error code. The error message describes the API and the error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-ROUTE_REQUEST_TO_ACL_FAILED: route [chars] request vsan [dec] domain [dec] failed:[chars].Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-3-TOPOLOGY_COMPUTATION_FAILED: Inter-VSAN Topology computation has failed due to: [chars].Explanation Inter-VSAN topology has failed because of the reason shown in the message. Possible reasons are (a) number of AFID/VSAN combination is more than the maximum supported value of 128, or (b) number of IVR-enabled switches is more than the maximum supported value of 128.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is received.Explanation IVR process received an unexpected message and transaction service (MTS) event. The MTS opcode is specified in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-UNLOCK_FAILED: [chars].Explanation An error occurred while releasing the lock. The reason for the failure is shown in the error message.
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.0(1b).
Error Message IVR-3-VSAN_SEGMENTED: [chars].Explanation VSAN is segmented. VSAN is removed from the topology graph and therefore inter-VSAN traffic cannot flow through this VSAN.
Recommended Action To correct the segmentation, use one of the following methods:
–
–
–
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-3-ZS_POLICY_IS_DENY_NO_ACTIVE_ZS: Default zone behavior policy changed to deny on VSAN [dec] and there is no active zoneset.Explanation The default zone behavior is changed to deny, and there is no active zone set. Inter-VSAN zone members may not be able to communicate in this VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message IVR-3-ZS_POLICY_IS_PERMIT_NO_FORCE: Default zone behavior policy changed to permit on VSAN [dec] and the force option is off.Explanation The default zone behavior is changed to permit and the force option is off. Inter-VSAN zone set activation in this VSAN has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-3-ZS_POLICY_IS_PERMIT_ZS_DEACTIVATED: Default zone behavior policy changed to permit on VSAN [dec] and regular zoneset deactivated.Explanation Default zone behavior is changed to permit and the regular zone set is deactivated. Inter-VSAN zone members may not be able to communicate.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
IVR-4
Error Message IVR-4-AUTO_TOPOLOGY_UPDATE_DISCARDED: [chars].Explanation The auto-topology update is discarded because of conflicts.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING: fcid rewrite [chars] request vsan [dec] did [chars] sid [chars] failed:[chars]. Retrying the request again.Explanation This happens when either the line cards are being upgraded or the ACL experienced an error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-4-PERSISTENT_VIRTUAL_DOMAIN_MERGE_CONFLICT: [chars].Explanation Merge failed because of a conflict in the persistent virtual domain configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IVR-4-PERSISTENT_VIRTUAL_FCID_MERGE_CONFLICT: [chars].Explanation Merge failed because of a conflict in the persistent virtual FC ID configuration.
Recommended Action Check the configuration and resolve merge issues.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IVR-4-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED_AND_RETRYING: qos iod undrop request vsan [dec] did [chars] failed:[chars]. Retrying the request again.Explanation This happens when either line cards are being upgraded or the ACL experienced an error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-4-ROUTE_REQUEST_TO_ACL_FAILED_AND_RETRYING: route [chars] request vsan [dec] domain [dec] failed:[chars]. Retrying the request again.Explanation This happens when either line cards are being upgraded or the ACL experienced an error while processing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-4-UNKNOWN_NATIVE_VSAN: Unknown native VSAN for the virtual domain [dec] in VSAN [dec] local native VSAN for the same virtual domain is [dec].Explanation Could not determine the native VSAN of the currently advertised virtual domain in the VSAN shown in the error message. This switch has learned of a device that is a member of the active IVR zone, has the same domain ID, but belongs to another native VSAN.This device is not advertised in that VSAN until the native VSAN information is resolved.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
IVR-5
Error Message IVR-5-FCID_NAT_MODE_ACTIVATED: FCID network address translation (NAT) mode has been activated.Explanation FC ID Network Address Translation (NAT) mode has been activated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-5-FCID_NAT_MODE_DEACTIVATED: FCID network address translation (NAT) mode has been deactivated.Explanation FC ID Network Address Translation (NAT) mode has been deactivated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-5-IVR_ASSERTION_FAILED: Unexpected assertion failure in File [chars] at Line [dec].Explanation A software assertion occurred in the IVR code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message IVR-5-IVZS_ACTIVATION_RETRYING: Inter-VSAN zoneset activation failed with error [hex] in VSAN [dec]. retrying after [dec] seconds.Explanation Inter-VSAN zone set activation failed with VSAN shown in the error message. This could be an intermittent regular zone set activation error. The activation retried in the number of seconds shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(3).
Error Message IVR-5-IVZS_WAITING_FOR_LOWEST_SWWN: Waiting for lowest switch WWN Inter-VSAN enabled switch in VSAN [dec].Explanation This switch does not have the lowest switch world wide name (sWWN) in the VSAN. Only the inter-VSAN enabled switch with the lowest sWWN can add the inter-VSAN zones to the regular active zone set in a VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IVR-5-IVZ_ACTIVATED: Inter-VSAN zoneset [chars] activated.Explanation Inter-VSAN zone set activated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_ACTIVATED_VSAN: Inter-VSAN zoneset [chars] activated in VSAN [dec].Explanation Inter-VSAN zone set activated in the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_CLEANUP_DONE: Inter-VSAN clean-up is done.Explanation Inter-VSAN related configuration might not be cleaned up before exiting.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_CLEANUP_DONE_BY_TIMER: Inter-VSAN clean-up is not done after waiting for 5 minutes.Explanation Inter-VSAN related configuration might not be cleaned up before the IVR process is terminated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message IVR-5-IVZ_DEACTIVATED: Inter-VSAN zoneset [chars] deactivated.Explanation Inter-VSAN zone set deactivated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_DEACTIVATED_VSAN: Inter-VSAN zoneset [chars] deactivated in VSAN [dec].Explanation Inter-VSAN zone set deactivated in the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_PARTIALLY_ACTIVATED: Inter-VSAN zoneset [chars] partially activated.Explanation Inter-VSAN zone set activated.
Recommended Action Check if it is successful in all VSANs by entering the show ivr zone set status command or use a similar Fabric Manager/Device Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-IVZ_PARTIALLY_DEACTIVATED: Inter-VSAN zoneset [chars] partially deactivated.Explanation Inter-VSAN zone set deactivated.
Recommended Action Check if it is successful in all VSANs by entering the show ivr zone set status command or use a similar Fabric Manager/Device Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message IVR-5-LICENSE_CHECKIN_FAILED: Failed to checkin [chars] license: Err=[chars].Explanation Failed to check in the listed license.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message IVR-5-SERVICE_GROUP_ACTIVATED: Inter-VSAN Service Group has been activated.Explanation Inter-VSAN Service Group has been activated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IVR-5-SERVICE_GROUP_DEACTIVATED: Inter-VSAN Service Group has been deactivated.Explanation Inter-VSAN Service Group has been deactivated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message IVR-5-VSAN_NO_LONGER_SEGMENTED: [chars].Explanation VSAN is no longer segmented. VSAN is added back to the topology graph and inter-VSAN traffic can now flow through this VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-5-VSAN_TOPOLOGY_ACTIVATED: Inter-VSAN Topology has been activated.Explanation Inter-VSAN topology has been activated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
IVR-6
Error Message IVR-6-DRAV_ASYNC_DOMAIN_RELEASE: [chars].Explanation A virtual domain finite state machine (DRAV FSM) has unconditionally released a domain because of a conflict after a fabric merge. The details are shown in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-6-DRAV_CRITICAL_RETRY_EXCEED: [chars].Explanation An attempt is being made to resend the DRAV FSM frames. The details are shown in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-6-DRAV_DOMAIN_ALLOC: Virtual domain [dec] for Native AFID: [dec] Native VSAN [dec].Explanation A virtual domain (indicated in the message) has been reserved for a device with native AFID and native VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-6-DRAV_DOMAIN_RELEASE: Virtual domain [dec] for Native AFID: [dec] Native VSAN [dec].Explanation A virtual domain representing a native AFID/VSAN (DRAV) on a finite state machine (FSM) has unconditionally released a domain because of a conflict, a domain was unused, or a release request was received from the owner. The domain is indicated by the name shown in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-6-DRAV_TOPO_UPDATE: [chars].Explanation DRAV FSM topology has been updated as indicated by the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message IVR-6-LICENSE_VALID: A valid license for inter-VSAN Routing has been obtained.Explanation A valid license for inter-VSAN routing has been obtained.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
IVR-7
Error Message IVR-7-CFS_REQ_RCVD: [chars].Explanation CFS request is received. The WWN of the switch that originated this request and the rr-token of the request are provided in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-7-CFS_RESP_SENT: [chars].Explanation CFS response is sent. The rr-token of the corresponding request and the status are provided in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message IVR-7-IVR_ASSERTION_FAILED: Unexpected assertion failure in File [chars] at Line [dec].Explanation An internal assertion failed in inter-VSAN routing. This is a low-level debug message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
LC-FCFWD Messages
This section contains the line card Fibre Channel forwarding (LC-FCFWD) messages.
LC-FCFWD-3
Error Message LC-FCFWD-3-ERROR: [chars].Explanation LC-FCWFD encountered an error.
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.2(2a).
LC-SPAN Messages
This section contains the line card switched port analyzer (LC-SPAN) messages.
LC-SPAN-3
Error Message LC-SPAN-3-ERROR: [chars].Explanation The line card switched port analyzer (LC-SPAN) manager encountered an error.
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).
LC_CFG Messages
This section contains the line card configuration manager (LC_CFG) messages.
LC_CFG-SLOT#-2
Error Message LC_CFG-SLOT#-2-LC_CFG_ABORT: ERROR: lc_cfg_mgr aborted registration (code [dec]).Explanation Lc_cfg_mgr exited on linecard.
Recommended Action No action is required.
Error Message LC_CFG-SLOT#-2-LC_CFG_EXITED: ERROR: lc_cfg_mgr exited on linecard (code [dec]).Explanation The line card configuration manager exited on the line card.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LC_CFG-SLOT#-2-LC2_CPU_ERRORS: [chars], Total IC [dec], DC [dec], Tag [dec], MBit [dec], SBit [dec], I30 [dec].Explanation The line card configuration manager detected CPU Cache errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
LC_PORT_CHANNEL Messages
This section contains the line card PortChannel (LC_PORT_CHANNEL) messages.
LC_PORT_CHANNEL-SLOT#-0
Error Message LC_PORT_CHANNEL-SLOT#-0-HW_FAILURE: fatal error in configuring [chars]: [chars].Explanation Fatal hardware error in the PortChannel configuration.
Recommended Action Reset the module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message LC_PORT_CHANNEL-SLOT#-0-IDX_FULL: D_IDX table full (current [dec], new [dec], total [dec]).Explanation Major error in the PortChannel configuration.
Recommended Action Reset the module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
LC_PORT_CHANNEL-SLOT#-3
Error Message LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_ERROR: [chars].Explanation General error in the PortChannel configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_IDXMAP_FAILURE: could not lookup port index for interface [chars].Explanation Could not look up the port index.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
LC_PORT_MGR Messages
This section contains the line card port manager (LC_PORT_MGR) messages.
LC_PORT_MGR-SLOT#-2
Error Message LC_PORT_MGR-SLOT#-2-LC_MTS_ERROR: An MTS error has occurred in ([chars]) with the following conditions: opc=[dec] ssap=[hex] dsap=[hex] syserr=[hex].Explanation This is a software error in message communications between two applications.
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.0(1b).
LC_RDL Messages
This section contains the line card remote domain lookup (LC_RDL) messages.
LC_RDL-3
Error Message LC_RDL-3-SYSLOG_ALLOC_FAIL: : [chars].Explanation The line card remote domain lookup (LC_RDL) memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec].Explanation The line card remote domain lookup (LC_RDL) experienced the context error shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_ERR: : [chars].Explanation The line card remote domain lookup (LC_RDL) syslog errors are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_EXIT: : [chars].Explanation The line card remote domain lookup (LC_RDL) exited on errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars].Explanation The line card remote domain lookup (LC_RDL) initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_MTS_ERR: : [chars].Explanation The line card remote domain lookup (LC_RDL) messaging and transaction service (MTS) errors occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-3-SYSLOG_MTS_REG_FAILED: : [dec] [dec].Explanation The line card remote domain lookup (LC_RDL) context error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
LC_RDL-6
Error Message LC_RDL-6-SYSLOG_DEBUG_1: : [chars] [hex].Explanation The line card remote domain lookup (LC_RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-6-SYSLOG_DEBUG_2: : [chars] [hex].Explanation The line card remote domain lookup (LC_RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-6-SYSLOG_INFO: : [chars].Explanation The line card remote domain lookup (LC_RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LC_RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec].Explanation The line card remote domain lookup (LC_RDL) context error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
LICMGR Messages
This section contains the license manager (LICMGR) messages.
LICMGR-2
Error Message LICMGR-2-LOG_LIC_GRACE_EXPIRED: Grace period expired for feature [chars].Explanation The unlicensed feature has exceeded its grace period. Applications using this license will be shut down immediately.
Recommended Action Install the license file to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-2-LOG_LIC_EXIT: License manager exiting: [chars].Explanation License manager is now exiting. The reason for the exit is shown in the message.
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).
LICMGR-3
Error Message LICMGR-3-LOG_LICAPP_NO_LIC: Application [chars] running without [chars] license, shutdown in [dec] days.Explanation Application [chars1] has not been licensed. The application will work for a grace period of [dec] days after which it will be shut down unless a license file for feature [chars2] is installed.
Recommended Action Install the license to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(3).
Error Message LICMGR-3-LOG_LICAPP_TOO_MANY_LIC: Only [dec] licenses are supported for [chars] feature, where as [dec] licenses are installed.Explanation More licenses are installed than allowed.
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(3).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message LICMGR-3-LOG_LIC_FILE_MISSING: License file(s) missing for feature [chars].Explanation One or more license files for the feature shown in the error message are missing and must be reinstalled.
Recommended Action Install the license to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-3-LOG_LIC_INVALID_HOSTID: Invalid license hostid VDH=[chars] for feature [chars].Explanation The feature has a license with an invalid license host ID. This can happen if a supervisor card with licensed features for one switch is installed on another switch.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-3-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for feature [chars].Explanation The feature has exceeded its evaluation time period. The feature will be shut down after a grace period.
Recommended Action Install the license to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-3-LOG_LIC_MESSAGE_ERROR: could not handle message: [chars] of type [dec] from addr [dec]:[dec].Explanation Could not handle an interprocess communications (IPC) message, of the type shown in the error message, sent by a component running on the shown node and service access point (SAP).
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.2(2a).
Error Message LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature [chars]. Application(s) shutdown in [dec] days.Explanation The feature has not been licensed. The feature will work for a grace period, then any applications using the feature will be shut down.
Recommended Action Install the license to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-3-LOG_LIC_SERVER_DOWN: License Server Down [dec].Explanation A connection to the license server could not be created.
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.2(2a).
Error Message LICMGR-3-LOG_LIC_SPROM_LIC: Feature [chars] issued [dec] licenses without a valid license file.Explanation The feature has been licensed the number of times shown in the error message without a valid license file. This means one or more license files are missing for the feature and must be reinstalled.
Recommended Action Install the license to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-3-LOG_LIC_TOO_MANY_LIC: Only [dec] licenses are supported for [chars] feature, where as [dec] licenses are installed.Explanation More licenses are installed than allowed.
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(3a).
LICMGR-6
Error Message LICMGR-6-LOG_LICAPP_EXPIRY_WARNING: Application [chars] evaluation license [chars] expiry in [dec] days.Explanation Application will exceed its evaluation time period days and will be shut down unless a permanent license for the feature is installed.
Recommended Action Install the license file to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-6-LOG_LIC_FEATURE_CLEARED: Cleared [dec] license(s) for feature [chars].Explanation Uninstalled license(s) for the feature shown in the error message.
Recommended Action Enter the show license usage command or use a similar Fabric Manager/Device Manager procedure to verify this license feature removal.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LICMGR-6-LOG_LIC_FEATURE_INSTALLED: Installed [dec] license(s) for feature [chars].Explanation Installed license(s) for the feature shown in the error message.
Recommended Action Enter the show license usage command or use a similar Fabric Manager/Device Manager procedure to verify this license feature installation.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LICMGR-6-LOG_LIC_INVALID_HOSTID: Feature [chars] has an invalid license hostid.Explanation The feature has an invalid license host ID. This can happen if a supervisor card with licensed features for one switch is installed on another switch.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED: Cleared license file [chars].Explanation Uninstalled the named license file.
Recommended Action Enter the show license command or use a similar Fabric Manager/Device Manager procedure to verify this license removal.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED_ALL: Cleared all licenses.Explanation Cleared all license files.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message LICMGR-6-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for feature [chars].Explanation The feature exceeded its evaluation time period and was shut down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message LICMGR-6-LOG_LIC_LICENSE_EXPIRY_WARNING: Evaluation license for feature [chars] will expire in [dec] days.Explanation The feature will exceed its evaluation time period in days and will be shut down.
Recommended Action Install an appropriate license for this feature.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message LICMGR-6-LOG_LIC_LICENSE_INSTALLED: Installed license file [chars].Explanation Installed the named license file.
Recommended Action Enter the show license command or use the similar Fabric Manager/Device Manager procedure to verify this license installation.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
MAC Messages
This section contains the MAC messages.
MAC-SLOT#-2
Error Message MAC-SLOT#-2-MAC_INFO: [chars]Explanation MAC Informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
MCAST Messages
This section contains the multicast (MCAST) messages.
MCAST-2
Error Message MCAST-2-SHUTDOWN: Process shutting down: [chars].Explanation The multicast process is shutting down.
Recommended Action The action depends on the situation. The multicast process can shut down gracefully because of a system restart (in which case no action needs to take place) or because of a failure. The message associated with the syslog should be self explanatory. If the process can restart properly, there is no immediate harm for the system stability and the suggested action is to report the syslog event together with an explanation of the operations most recently performed on the system. If the component cannot restart properly, contact your support representative. 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.2(2a).
MCAST-4
Error Message MCAST-4-ERROR: [chars].Explanation Multicast encountered a generic error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
MCAST-5
Error Message MCAST-5-BAD_MSG: Received bad message: [chars].Explanation Multicast has received a malformed or unrecognizable message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MCAST-5-START: Process has been started.Explanation The multicast process has started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
MODULE Messages
This section contains the module messages.
MODULE-2
Error Message MODULE-2-LCM_UPGRADE_DONE_GENERAL_FAIL: Upgrade ready message fails seq [dec].Explanation Upgrade ready message failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-2-LCM_UPGRADE_OVER_FAIL: Upgrade over message returned [dec] [hex] for SAP [dec].Explanation Upgrade done message failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-2-LCM_UPGRADE_READY_FAIL: Upgrade ready message returned [dec] [hex] for SAP [dec].Explanation Upgrade ready message failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL: Upgrade ready message fails seq [dec].Explanation Upgrade ready message failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-2-MOD_DIAG_FAIL: Module [dec] reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error [hex]).Explanation The module reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.
Recommended Action Collect information about the module by entering the show module internal all module [decimaldigit] CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec].Explanation The module failed to download a new image from the supervisor module.
Recommended Action Collect module information by entering the show module internal all module [decimaldigit] command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-2-MOD_FAIL: Initialization of module [dec] failed.Explanation The module reported a failure during the initialization phase and will be powered down.
Recommended Action Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-2-MOD_MAJORSWFAIL: Module [dec] reported a critical failure in service [chars].Explanation A critical failure caused by the service occurred in the module. The module restarted automatically.
Recommended Action Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message MODULE-2-MOD_MINORSWFAIL: Module [dec] reported a failure in service [chars].Explanation A non-critical failure in the service occurred on the module. The module will not be restarted.
Recommended Action Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-2-MOD_NOT_ALIVE: Module [dec] not responding... resetting.Explanation The module is not replying to the hello message. The module manager will reset the module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-2-MOD_REGFAILED: Registration failed for module [dec].Explanation The module sent the registration message notifying a failure.
Recommended Action Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-2-MOD_SOMEPORTS_FAILED: Module [dec] reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]).Explanation Module reported a failure in the runtime diagnostic because of a failure in some of the ports.
Recommended Action Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-2-MOD_UNKNOWN: Module type [[dec]] in slot [dec] is not supported.Explanation The software card ID of module [dec] is not supported by the supervisor.
Recommended Action Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure. Update SPROM contents by entering the update sprom command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-2-XBAR_DIAG_FAIL: Xbar [dec] (serial: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error [hex]).Explanation The xbar in the slot reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.
Recommended Action Collect information about the module by issuing the show module internal all xbar CLI command or by using a similar Fabric Manager procedure.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-2-XBAR_FAIL: Initialization of xbar [dec] (serial: [chars]) failed.Explanation Xbar reported a failure during the initialization phase and will be powered down.
Recommended Action Collect information about the module by issuing the show module internal all xbar <modulenumber> CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (serial: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]).Explanation Xbar reported a failure in the runtime diagnostic because of failure in some of the ports.
Recommended Action Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-2-XBAR_UNKNOWN: Xbar type [[dec]] in slot [dec] is not supported.Explanation The software card ID of xbar is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
MODULE-3
Error Message MODULE-3-MOD_SRG_NOT_COMPATIBLE: Module [dec] firmware is not compatible with supervisor, downloading new image.Explanation The software version of the module is not supported by the supervisor module.
Recommended Action Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
MODULE-4
Error Message MODULE-4-MOD_WARNING: Module [dec] reported warnings on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error [hex]).Explanation Module reported a warning in the runtime diagnostic because of a failure in some of the ports.
Recommended Action Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-4-XBAR_WARNING: Xbar [dec] (serial: [chars]) reported warnings on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error [hex]).Explanation Xbar reported a warning in the runtime diagnostic because of failure in some of the ports.
Recommended Action Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
MODULE-5
Error Message MODULE-5-ACTIVE_SUP_OK: Supervisor [dec] is active.Explanation Module is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-MOD_DIAG_FAIL: Module [dec] reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]).Explanation The module in the slot reported a failure in the runtime diagnostic. Module manager will power cycle the module.
Recommended Action Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-5-MOD_OK: Module [dec] is online (serial: [chars]).Explanation Module named is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-5-MOD_MINORSWFAIL: Module [dec] reported a failure in service [chars].Explanation A non-critical failure caused by the service occurred in the module. The module will not be reset.
Recommended Action Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-5-MOD_OK: Module [dec] is online (serial: [chars]).Explanation Module named is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-5-MOD_OK: Module [dec] is online.Explanation Module is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-MOD_PURGE_CONFIG: Purging the configuration for module [dec].Explanation Notification is sent to remove module configurations.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-5-MOD_REINIT: Re-initializing module [dec].Explanation Module reported a failure during the initialization phase and will be reinitialized.
Recommended Action Collect module information by entering the show module_internal all module command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-MOD_RESTART: Module [dec] is restarting after image download.Explanation Module completed image download and restarted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-MOD_SOMEPORTS_FAILED: Module [dec] reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]).Explanation Module reported a failure in the runtime diagnostic because of the failure of some of the ports.
Recommended Action Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-5-MOD_STARTUP_CFG_MISMATCH: The startup configuration cannot be applied to a different module type for module [dec] (serial: [chars]). [chars] module is replacing [chars].Explanation The startup configuration for the module contains information about a different type of module instead of containing information about the current one.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-MOD_WARNING: Module [dec] reported warnings on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]).Explanation Module [dec] reported a warning in the runtime diagnostic because the failure of some of the ports.
Recommended Action Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 2.0(1b).
Error Message MODULE-5-STANDBY_SUP_OK: Supervisor [dec] is standby.Explanation Module is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message MODULE-5-XBAR_OK: Xbar [dec] is online (serial: [chars]).Explanation Xbar is ready to be configured and to switch traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message MODULE-5-XBAR_REINIT: Re-initializing xbar [dec] (serial: [chars]).Explanation Xbar reported a failure during the initialization phase and will be rebooted.
Recommended Action Collect information about the module by issuing the show module internal all xbar <modulenumber> CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
MODULE-6
Error Message MODULE-6-MOD_PURGE_CONFIG: Purging the configuration for module [dec].Explanation Notification is sent to remove module configurations.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message MODULE-6-MOD_REG_OK: Registration succeeded for module [dec].Explanation Module sent a successful registration message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NASB Messages
This section contains the Network-Accelerated Serverless Backup (NASB) messages.
NASB-SLOT#-5
Error Message NASB-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN :[dec] VT pWWN :[chars] DPP died.Explanation The data path processor (DPP) associated with the virtual target failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message NASB-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars] VT Activate failed.Explanation The activate step for a virtual target failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message NASB-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN :[dec] VT pWWN :[chars] VT and NPort creation FAILED !!!.Explanation The virtual target and N port creation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message NASB-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target : [chars] Deleted.Explanation The virtual target in the associated VSAN is being destroyed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message NASB-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars] VSAN down.Explanation The VSAN where the virtual target is configured is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
NPC Messages
This section contains the N port creator (NPC) messages.
NPC-SLOT#-3
Error Message NPC-SLOT#-3-LOG_NPC_ERR: Nonrecoverable error: [chars].Explanation Errors caused the program to exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NPC-SLOT#-4
Error Message NPC-SLOT#-4-LOG_NPC_WARNING: Serious error: [chars].Explanation Serious errors that affect the all normal operations occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NPC-SLOT#-5
Error Message NPC-SLOT#-5-LOG_NPC_DEBUG: Unexpected error: [chars].Explanation Unexpected errors occurred that affect some normal operations.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NPC-SLOT#-5-LOG_NPC_NVP_FSM: Illegal event received: [chars].Explanation Illegal event received in N port creator virtual N port (NPC_NVP) finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NPC-SLOT#-5-LOG_NPC_VSAN_FSM: Illegal event received: [chars].Explanation Illegal event received in the N port creator virtual N port (NPC_NVP) finite state machine (FSM).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NPV Messages
This section contains the N-Port Virtualization(NPV) messages.
NPV-2
Following are critical-level NPV system log messages.
Error Message NPV-2-NPV_DISABLE_FAILED: NPV could not disabled : [chars] [chars].Explanation NPM could not be disabled due to the reason specified.
Recommended Action Try again.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-2-NPV_EXITEDExplanation NPM process exited in file error system logs.
Recommended Action .No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
NPV-3
Error Message NPV-3-ACL_UPDATE_FAILEDExplanation ACL update request initiated by the NPV process has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-F_RJT_SENTExplanation NPV Process sent a F_RJT frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-FC2_SEND_FAILED: [chars].Explanation NPV process could send an FC2 message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-FRAME_DISCARDED: [chars].Explanation NPV process discarded an FC2 frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-LCP_PROGRAMMING_FAILED: [chars].Explanation LCP programming request initiated by the NPV process has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-LS_RJT_SENTExplanation NPV Process sent a LS_RJT frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-LS_RJT_RCVD: [chars].Explanation NPV process received an LS_RJT frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-MALLOC_FAILED: [chars].Explanation An assertion failed in NPV code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-MTS_SEND_FAILED: [chars].Explanation NPV process could not send an MTS message.
Recommended Action No action is required
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-NPIV_DISABLE_FAILEDExplanation NPIV feature could not be disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-PORT_BRINGUP_FAILEDExplanation NPV process has failed to bring up the port.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-PORT_REINIT_FAILEDExplanation Port reinit request initiated by the NPV process has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-3-UNEXPECTED_EVENT: [chars].Explanation NPV process has received an unexpected event in the current state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
NPV-5
Following are notification-level NPV system log messages:
Error Message NPV-5-ASSERTION_FAILEDExplanation An assertion failed in NPV code.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
NPV-6
Following are informational-level NPV system log messages:
Error Message NPV-6-ABTS_SENTExplanation NPV process sent a ABTS frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-EXT_IF_SELECTED: [chars].Explanation NPV process has selected an external interface to forward either all frames received on a server interface or frames received from a specific port WWN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-LS_ACC_RCVD: [chars].Explanation NPV process received an LS_ACC frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-FDISC_RCVDExplanation NPV process received an FLOGI frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-FDISC_SENTExplanation NPV process sent an FDISC frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-FLOGI_RCVDExplanation NPV process received an FLOGI frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-LC_ACC_SENTExplanation NPV process sent a LS_ACC frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-LOGO_RCVDExplanation NPV process received an LOGO frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-LOGO_SENTExplanation NPV process sent a LOGO frame.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_NOTIF_RCVDExplanation NPV process received an MTS notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_NOTIF_SENT:[CHAR].Explanation NPV sent an MTS notification.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_REQ_RCVDExplanation NPV process received an MTS request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_REQ_SENTExplanation NPV process received an MTS request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_RESP_RCVDExplanation NPV process received an MTS response.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-MTS_RESP_SENTExplanation NPV process sent an MTS response.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-NPIV_DISABLED: [chars].Explanation NPIV feature has been disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-NPIV_ENABLED: [chars].Explanation NPIV feature has been enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message NPV-6-SERVER_PROXY_LOGO_SENTExplanation NPV process sent a LOGO frame to core switch.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
NTP Messages
This section contains the Network Time Protocol (NTP) messages.
NTP-2
Error Message NTP-2-NTP_SYSLOG_CRIT_ERR: : [chars].Explanation A critical error occurred in NTP.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1.(2).
Error Message NTP-2-NTP_SYSLOG_INIT_FAIL: : [chars] [chars].Explanation Network Time Protocol (NTP) initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC[dec] for [chars].Explanation NTP did not receive response from the linecard for the request sent.
Recommended Action No action is required.
NTP-3
Error Message NTP-3-NTP_SYSLOG_ALLOC_FAIL: : [chars].Explanation Network Time Protocol (NTP) syslog allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-3-NTP_SYSLOG_ERR: : [chars].Explanation Network Time Protocol (NTP) syslog error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-3-NTP_SYSLOG_ERR_EXT: : [chars] [dec].Explanation Network Time Protocol (NTP) syslog error exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-3-NTP_SYSLOG_MTS_ERR: : [chars].Explanation Network Time Protocol (NTP) messaging and transaction service (MTS) error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NTP-6
Error Message NTP-6-NTP_SYSLOG_CREATED: : [chars]; Slot No: [dec].Explanation Network Time Protocol (NTP) syslog created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-6-NTP_SYSLOG_EXIT: : [chars].Explanation Network Time Protocol (NTP) syslog exit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message NTP-6-NTP_SYSLOG_WARN: : [chars].Explanation Network Time Protocol (NTP) syslog warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
NVP Messages
This section contains the virtual N port (NVP) messages.
NVP-6
Error Message NVP-6-NVP_INFO: [chars].Explanation virtual N port (NVP) daemon informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message NVP-6-STARTING: deamon started.Explanation The virtual N port (NVP) daemon successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
NVP-SLOT# Messages
This section contains the virtual N port slot (NVP-SLOT#) messages.
NVP-SLOT#-2
Error Message NVP-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot ILC.Explanation The listed component caused a critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
PLATFORM Messages
This section contains the platform messages.
PLATFORM-0
Error Message PLATFORM-0-CHASSIS_CLKSWITCH: Hardware clock switched to redundant clock-[dec].Explanation Clock module on chassis detected a failure and switched to the redundant clock module.
Recommended Action Enter the show platform internal info command to collect more information or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-CHASSIS_CLKSW_MODULE_RESET: Modules reset due to clock switch.Explanation The chassis clock source has been switched and all Generation 1 line cards will be reset. The system will automatically continue using a redundant clock module.
Recommended Action Replace the failed clock module.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch.Explanation Chassis clock source has failed and system will be reset. System will automatically start using the redundant clock module.
Recommended Action Replace the failed clock module during the next maintenance window.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-FAIL_REMOVED: Fan module removed before [dec] seconds.Explanation Fan module was removed. This could lead to temperature alarms.
Recommended Action Replace the fan module immediately.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-MOD_TEMPMAJALRM: Module [dec] reported major temperature alarm.Explanation Module in the slot exceeded a major temperature threshold.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-MOD_TEMPRECOVER: Module [dec] recovered from major temperature alarm. Minor temperature alarm pending.Explanation Module recovered from a major temperature threshold. Minor threshold still exceeded.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-MOD_TEMPSHUTDOWN: Module [dec] powered down due to major temperature alarm.Explanation Module shut down because temperature exceeded major threshold.
Recommended Action Enter show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-SUP_SPROM_ERROR: Unable to read SPROM for Sup in slot [dec].Explanation The supervisor in the slot named was not able to read its SPROM.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-SUP_WRONGSLOTNUM: Supervisor powered up in WRONG SLOT:[dec] (Serial number [chars]).Explanation The supervisor is coming up in wrong slot.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED: Failed to load linecard module drivers.Explanation Failed while trying to load drivers.
Recommended Action Image is possibly corrupt. Load a different image.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-SYS_RESET: [chars] System shutdown in [dec] seconds.Explanation System shut down will occur in the number of seconds shown in the error message.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-SYS_SHUTDOWN: System shutdown in [dec] seconds due to major temperature alarm.Explanation System shut down in seconds because of temperature exceeding major threshold.
Recommended Action Use the showenvtemperature CLI command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-MDS9124: System shutdown in [dec] seconds due to less than 4 fans operating.Explanation System shutdown in seconds because of less than 4 fans operating.
Recommended Action Enter a show env fan command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message PLATFORM-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in [dec] seconds due to fan removal.Explanation System shut down will occur in the number of seconds shown because the fan has been removed.
Recommended Action Enter the show env fan CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-SYS_SUP_DRIVER_LOAD_FAILED: Failed to load supervisor module drivers.Explanation Failed while trying to load drivers.
Recommended Action Image is possibly corrupt. Load a different image.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-0-XBAR_CARD_CLK_FAIL: Xbar card in slot:[dec] (Serial number [chars]) encountered clock failure.Explanation The xbar in the slot named encountered clock failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-XBAR_CARD_INCOMPAT_CHASSIS: Xbar card in slot:[dec] (Part number [chars]) Incompatible with backplane chassis Part Num:[chars].Explanation The xbar in the slot named is incompatible with backplane chassis.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-0-XBAR_WRONGSLOTNUM: Xbar powered up in WRONG SLOT:[dec] (Serial number [chars]).Explanation The xbar in the slot named powered up in wrong slot.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLATFORM-1
Error Message PLATFORM-1-CASA_FAN_FAIL: Fan module [dec] Failed.Explanation Fan module failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PLATFORM-1-FAN_FAIL: Fan module Failed.Explanation Fan module failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-1-MDS9124_FAN_FAIL: Less than 4 required fans operating.Explanation A fan module has failed leaving fewer than four total fans operating. This can lead to overheating and temperature alarms.
Recommended Action The fan needs to be replaced. Use the show platform internal info CLI command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message PLATFORM-1-MOD_PWRDENY: Module [dec] cannot be powered up due to insufficient power (Serial No. [chars]).Explanation Available power in power supplies is not sufficient to power up the module.
Recommended Action Verify available power and current usage by entering the show env power CLI command or by using a similar Fabric Manager/Device Manager procedure. Refer to power supply documentation in the relevant hardware installation guide to learn how to increase power supply capacity.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-1-MDS9124_FAN_FAIL: Less than 4 required fans operating.Explanation Fan module has failed leaving fewer than four total fans operating. This can lead to overheating and temperature alarms.
Recommended Action Use the show platform internal info CLI command to collect more information. Fan needs to be replaced.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message PLATFORM-1-XBAR_PWRDENY: Xbar [dec] can not be powered up due to insufficient power (Serial number [chars]).Explanation Available power in power supplies is not sufficient to power up the xbar.
Recommended Action Verify available power and current usage with the show env power CLI command or by using a similar Fabric Manager procedure. See the power supply document on how to increase power supply capacity.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLATFORM-2
Error Message PLATFORM-2-CASA_FAN_FAIL: Fan module [dec] Failed.Explanation Indicated fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Use the show platform internal info CLI command to collect more information or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-CASA_FAN_OK: Fan module [dec] ok.Explanation Fan module indicated is ok.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-CHASSIS_CLKMODFAULTY: Chassis clock module [dec] faulty.Explanation Indicated clock module on chassis is faulty or has been removed.
Recommended Action Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module [dec] ok.Explanation Clock module on chassis is functioning properly.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is clock-[dec].Explanation The current chassis clock source is indicated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-FAN_OK: Fan module ok.Explanation Fan module is ok.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-FANLET_FAN_FAIL: Failed Fanlets for Fan [dec] ([chars] fan) : [chars].Explanation The specified fans have failed. This can lead to overheating and temperature alarms.
Recommended Action Use the show platform internal info CLI command to collect more information or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-FANMOD_FAN_FAIL: Fan module [dec] ([chars] fan) Failed.Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Use the show platform internal info CLI command to collect more information, or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-FANMOD_FAN_OK: Fan module [dec] ([chars] fan) ok.Explanation Fan module is ok.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_ALL_PWRDN_NOXBAR: All modules powered down due to non-availability of xbar modules.Explanation All modules in a switch have been powered down because all xbar modules are offline.
Recommended Action Use the CLI commands show module, show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] to collect more information if you suspect a module has been powered down because of errors. At least one exbar module has to be up for switch modules to function.
Introduced Cisco MDS SAN-OS Release 3.0(1).'
Error Message PLATFORM-2-MOD_PWRDENY: Module [dec] can not be powered up due to insufficient power (Serial number [chars]).Explanation Available power in power supplies is not sufficient to power up the module.
Recommended Action Verify available power and current usage with the show env power CLI command or by using a similar Fabric Manager procedure. See the power supply document on how to increase power supply capacity.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_PWRFAIL: Module [dec] failed to power up (Serial number [chars]).Explanation The module in the slot named failed to power up.
Recommended Action Use the show platform internal all module [decimaldigit] CLI command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to IDPROM read error.Explanation The module cannot be powered up because of IDPROM read error.
Recommended Action Use the CLI commands show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] and show sprom module[dec][dec] to read module IDPROM contents to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_PWRUP_XBAR: Modules powered up due to xbar availability.Explanation Modules powered up because at least one xbar module is online.
Recommended Action No action needed.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_TEMPMINALRM: Module [dec] reported minor temperature alarm (sensor-index [dec] temperature [dec]).Explanation Module has exceeded a minor temperature threshold.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-MOD_TEMPOK: [chars] recovered from minor temperature alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec].Explanation The module in the slot named recovered from a major temperature threshold alarm.
Recommended Action Enter a showenvtemperature command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-MOD_TEMPRECOVER: [chars] recovered from major temperature alarm. Minor temperature alarm pending. Sensor=[dec] Temperature=[dec] MAJThreshold=[dec] MinThresh=[dec].Explanation The module in the slot named recovered from a major temperature threshold alarm and the minor threshold is still exceeded.
Recommended Action Enter a showenvtemperature command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_ABSENT: No bootflash found in Module [dec].Explanation No bootflash found.
Recommended Action Put bootflash in the module and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: Bootflash access error in Module [dec].Explanation Bad bootflash/corrupted file system.
Recommended Action Try to put in a known good bootflash in the module and try again.
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: BAD Bootflash found in Module [dec].Explanation Bad bootflash found.
Recommended Action Put a good bootflash in the module and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PFM_LC_MOD_POWERED_DOWN: Module [dec] Powered Down. Module is not supported in this chassis. (Chassis Incompatible card).Explanation Module has been powered down because the card is not supported in this chassis.
Recommended Action Use the show module CLI command to see the power down reason, or use a similar Fabric Manager procedure.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PFM_NETBOOT_DISABLE: Netboot for supervisor module in slot [dec] is disabled due to incompatible platform.Explanation Standby supervisor failed to power up.
Recommended Action Try to replace the standby supervisor.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PFM_LC_NETBOOT_FAIL: Netboot for Module [dec] failed.Explanation Netboot failed.
Recommended Action Replace the BIOS in the module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PFM_LC_REGISTRATION_FAIL: Could not register with Module [dec].Explanation Module registration failed.
Recommended Action Replace the module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PFM_LOW_MEMORY_CONDITION: Module [dec] is running low on memory. %ld percent used.Explanation Supervisor is running low on memory.
Recommended Action Switchover.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message PLATFORM-2-PFM_LC_STATUS: Module [dec] powered up with [dec] status.Explanation Status for module that failed registration.
Recommended Action Replace the module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PFM_PWR_MGMT_EPLD_VER_MISMATCH: Module [dec] Pwr Mgmt Epld (Version-[dec]) needs to be upgraded.Explanation the ELPD needs to be upgraded. Using a wrong version of EPLD can result in unexplained behaviour.
Recommended Action Upgrade the power managment EPLD. Refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PFM_STDBY_POWERUP_FAIL: standby supervisor failed to power up.Explanation Standby supervisor failed to power up.
Recommended Action Replace the standby supervisor.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_CAPACITY_DIFFER: Detected power supplies with differing capacity. It is recommended to have same capacity for both powersupplies otherwise it may cause service disruptions.Explanation Detected a power supply that has a different capacity than an the other power supply.
Recommended Action Refer tot he Cisco MDS 9000 Family CLI Configuration Guide for information on increasing or decreasing power supply capacity and configuring power supplies. Use the show environment power and show platform internal info to collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_DETECT: Power supply [dec] detected but shutdown (Serial number [chars]).Explanation Power Supply is detected but has been shut down.
Recommended Action Use the CLI commands show environment power and show platform internal info to collect more information, or use similar Fabric Manager procedures.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_FAIL: Power supply [dec] failed or shutdown (Serial No. [chars]).Explanation Power supply failed or has been shut down.
Recommended Action Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager or Device Manager procedure to collect more information. See the power supply documentation in the relevant hardware installation guide to learn more on increasing or decreasing power supply capacity and configuring power supplies.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed.Explanation Fan module in the named power supply has failed.
Recommended Action Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PLATFORM-2-PS_FANOK: Fan in Power supply [dec] ok.Explanation Fan module in the named power supply is operating.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_OK: Power supply [dec] ok (Serial number [chars]).Explanation Power Supply is ok.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_MISMATCH: Detected power supply [chars]. This reduces the redundant power available to the system and can cause service disruptions (Serial No. [chars]).Explanation Detected a new power supply that has reduced capacity compared to a previous power supply.
Recommended Action Refer to power supply document on increasing or decreasing power supply capacity, configuring power supplies, and so on. Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PS_REMOVE: Power supply [dec] removed (Serial number [chars]).Explanation Power Supply is removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-PS_REMOVE_LAST: Unexpected removal of last power supply [dec]. (Serial No. [chars]).Explanation Unexpected removal of the only power supply in the system.
Recommended Action Power supply unit may be faulty. Contact your customer support representative to replace the unit.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PS_UNKNOWN: Detected an unknown power supply [dec] for CISCO MDS 9500/9200 Multilayer Switches ((Serial number[chars]).Explanation Unable to determine power supply type. Default power supply types will be assumed.
Recommended Action Refer to the appropriate product hardware installation guide for information on increasing or decreasing power supply capacity and configuring power supplies.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-PS_UNSUPPORTED: Detected an unsupported power supply [dec] [chars] for CISCO MDS 9500/9200 Multilayer Switches (Serial number [chars]).Explanation This power supply is not supported for the Cisco MDS 9500 or 9200 series of switches.
Recommended Action Refer to the appropriate product hardware installation guide for information on increasing or decreasing power supply capacity and configuring power supplies.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-2-SYS_IDPROMBAD: Chassis IDPROM [dec] data invalid.Explanation The named chassis IDPROM contains invalid data.
Recommended Action Use the show sprom module [decimaldigit] CLI command to read module IDPROM contents and collect more information. Or, use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_FAIL: Chassis IDPROM [dec] data re-initialization Un-successful. Data is invalid.Explanation Chassis IDPROM re-initialization was unsuccessful. The data is invalid.
Recommended Action Us ethe 'show sprom module decimal digit 1 CLI command to read the module IDPROM contents and collect more information.
Introduced Cisco MDS SAN-OS Release 3.0(2).
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_PASS: Chassis IDPROM [dec] data re-initialized successfully.Explanation Chassis IDPROM invalid data was succesfully re-initialized to valid.
Recommended Action Us ethe 'show sprom module decimal digit 1 CLI command to read the module IDPROM contents and verify the information.
Introduced Cisco MDS SAN-OS Release 3.0(2).
PLATFORM-3
Error Message PLATFORM-3-MOD_PWRFAIL: Module [dec] failed to power up (Serial No. [chars]).Explanation The module failed to power up.
Recommended Action Enter the show platform internal all module [dec] CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-3-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to idprom read error.Explanation The module cannot be powered up because of an IDPROM read error.
Recommended Action Enter the show platform internal all module [dec] and show module internal all module [dec] show sprom module [dec][dec] CLI commands or use similar Fabric Manager/Device Manager procedures to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-3-SYS_IDPROMBAD: Chassis idprom [dec] data invalid.Explanation The chassis IDPROM contains invalid data.
Recommended Action Enter the show sprom module [dec] CLI command or use a similar Fabric Manager/Device Manager procedure to read module idprom contents and collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-3-XBAR_PWRFAIL: Xbar [dec] failed to power up (Serial number [chars]).Explanation The named xbar in the slot failed to power up.
Recommended Action Use the show platform internal all module [decimaldigit] CLI command to collect more information or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-3-XBAR_PWRIDPROMFAIL: Xbar [dec] failed to power up due to IDPROM read error.Explanation The xbar named cannot be powered up because of an IDPROM read error.
Recommended Action Use the CLI commands show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] and show sprom xbar [dec] [dec] to read module IDPROM contents to collect more information (or use a similar Fabric Manager procedure).
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLATFORM-4
Error Message PLATFORM-4-MOD_TEMPFAIL: [chars] temperature sensor [dec] failed.Explanation The module in the slot named contains a faulty temperature sensor.
Recommended Action Use the show env temperature CLI command to collect more information or use a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLATFORM-5
Error Message PLATFORM-5-CHASSIS_CLKMODOK: Chassis clock module [dec] ok.Explanation Clock module on chassis is functioning properly.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-CHASSIS_CLKSRC: Current chassis clock source is clock-[dec].Explanation The current chassis clock source is shown in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-FAN_OK: Fan module ok.Explanation Fan module is operating normally.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_DETECT: Module [dec] detected (Serial No. [chars]).Explanation A new module has been detected.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_PWRDN: Module [dec] powered down (Serial No. [chars]).Explanation The module is powered down.
Recommended Action Enter the show module, show platform internal all module[dec] and show module internal all module [dec] CLI commands or use similar Fabric Manager/Device Manager procedure to collect more information if you suspect the module has been powered down because of errors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_PWRUP: Module [dec] powered up (Serial No. [chars]).Explanation The module is powered up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_REMOVE: Module [dec] removed (Serial No. [chars]).Explanation The module has been removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_TEMPFAIL: Module [dec] temperature sensor failed.Explanation Module contains a faulty temperature sensor.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-MOD_TEMPOK: Module [dec] recovered from minor temperature alarm.Explanation Module exceeded a major temperature threshold.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-PS_CAPACITY_CHANGE: Power supply PS[dec] changed its capacity. possibly due to power cable removal/insertion (Serial number [chars]).Explanation A power supply capacity change has been detected.
Recommended Action Refer to power supply documentation on increasing and decreasing power supply capacity, configuring power supplies, and other information about power supplies. Use the show environment power CLI command and the show platform internal info CLI command to collect more information.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message PLATFORM-5-PS_DETECT: Power supply [dec] detected but shutdown (Serial No. [chars]).Explanation Power supply is detected, but it is shut down.
Recommended Action Enter the show environment power and show platform internal info CLI commands or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-PS_FANOK: Fan in Power supply [dec] ok.Explanation Fan module in the named power supply is operating normally.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PLATFORM-5-PS_OK: Power supply [dec] ok (Serial No. [chars]).Explanation Power supply is operating normally.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-PS_REMOVE: Power supply [dec] removed (Serial No. [chars]).Explanation Power supply has been removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-SYS_SHUTDOWN: System shutdown in [dec] seconds due to major temperature alarm.Explanation System shut down in seconds because the temperature exceeded a major threshold.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PLATFORM-5-XBAR_DETECT: Xbar [dec] detected (Serial number [chars]).Explanation A new xbar in the slot named has been detected.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-5-XBAR_PWRDN: Xbar [dec] powered down (Serial number [chars]).Explanation The xbar in the slot named is powered down.
Recommended Action Perform a showmodulexbar','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodul e[decimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-5-XBAR_PWRUP: Xbar [dec] powered up (Serial number [chars]).Explanation The xbar in the slot named is powered up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PLATFORM-5-XBAR_REMOVE: Xbar [dec] removed (Serial number [chars]).Explanation The xbar in the slot named has been removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLATFORM-7
Error Message PLATFORM-7-PFM_CLOCK_UPD_FAIL: Clock update failed due to context-switch delay of [dec] msec.Explanation System will shut down in seconds because of a clock update failure.
Recommended Action Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PLOG Messages
This section contains the persistent logger (PLOG) messages.
PLOG-4
Error Message PLOG-4-PLOG_LC_EXIT: Persistent Logger encountered an error [dec].Explanation Persistent Logger encountered an error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PLOG_SUP Messages
This section contains the persistent logger (PLOG_SUP) messages.
PLOG_SUP-4
Error Message PLOG_SUP-4-PLOG_SUP_EXIT: Persistent Logger encountered an error [dec].Explanation Persistent Logger encountered an error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
PORT Messages
This section contains the port messages.
PORT-3
Error Message PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported.Explanation Transceiver (SFP) is not from an authorized vendor.
Recommended Action Enter the show interface transceiver CLI command or use a similar Fabric Manager/Device Manager procedure to determine the transceiver being used. Contact your customer support representative for a list of authorized transceiver vendors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT-5
Error Message PORT-5-EC_DISABLED_AS_LICENSE_NOT_PRESENT: Extended credit feature has been disabled as Enterprise Package license could not be checked out.Explanation The Enterprise Package license is not available. The extended credit feature has been disabled even though it was present in the startup configuration.
Recommended Action Install the Enterprise Package license and re-enable the extended credit feature.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message PORT-5-IF_BRINGUP_ALLOWED_FCOT_CHECKSUM_ERR: Interface [chars] is allowed to come up even with SFP checksum error.Explanation SFP checksum on this interface failed.
Recommended Action Replace the SFP on this interface.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message PORT-5-IF_BRINGUP_NOT_ALLOWED_PORT_CONFIG_FAILURE: Interface [chars] is not allowed to be operational due to port config failure for reason: [chars] ([hex]).Explanation Check interface configuration.
Recommended Action Try to change the configuration on the interface with the current available hardware capability.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down).Explanation Interface has been configured to be administratively down.
Recommended Action Enter the CLI commands config terminal, interface, no shutdown or use a similar Fabric Manager procedure to bring up the interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED: Interface [chars] is down (Error disabled - bit error rate too high).Explanation The port has detected a bit error rate too high in frames received from attached device.
Recommended Action Check the attached device and replace it if needed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_BUNDLE_MISCFG: Interface [chars] is down (Isolation due to channel mis-configuration on local or remote switch).Explanation One port across a link is part of a PortChannel while the other is not.
Recommended Action While adding or deleting a member port from a PortChannel, both ports across the link should be added or deleted. No operation should be performed on either port until they are both added or deleted.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change).Explanation FCIP interface temporarily down because of reconfiguration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel admin down).Explanation This interface belongs to a PortChannel and the PortChannel is configured to be administratively down.
Recommended Action Bring the interface up by entering the no shutdown CLI command or by using a similar Fabric Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface [chars] is down (Channel membership update in progress).Explanation The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel.
Recommended Action Try the configuration again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DENIED_DUE_TO_PORT_BINDING: Interface [chars] is down(Suspended due to port binding).Explanation The F port is suspended because it is being denied by port binding.
Recommended Action Modify the port binding database to allow the host port to log in.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to domain id assignment failure).Explanation The interface is isolated because of a failure while assigning a domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is down (Isolation due to invalid fabric reconfiguration).Explanation Invalid RCF received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down (Isolation due to domain manager disabled).Explanation The interface is isolated because the domain manager is disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars] is down (Isolation due to domain manager other side not responding).Explanation Remote end domain manager is not responding.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DOMAIN_NOT_ALLOWED_ISOLATION: Interface [chars] is isolated (domain not allowed).Explanation There are not enough allowed domains to merge the VSANs across the link.
Recommended Action Ensure that all assigned domain IDs are in the configured allowed domains on both sides of the link.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message PORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars] is down (Isolation due to domain other side eport isolated).Explanation This interface is isolated because the remote end is isolated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to domain overlap).Explanation The interface is isolated because of a domain overlap.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_DPVM_VSAN_NOT_FOUND: Interface [chars] is down (dynamic vsan not present).Explanation The specified dynamic VSAN is not configured on this switch.
Recommended Action Configure the dynamic VSAN.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ELP failure).Explanation Exchange link parameter (ELP) failed on the interface.
Recommended Action Enter the show port internal info CLI command or use a similar Fabric Manager/Device Manager procedure to check the ELP failure reason field.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSF_PARAM_ERR: Interface [chars] is down (Isolation due to ELP failure: class F param error).Explanation Exchange link parameter (ELP) failed on the interface because of a class F parameter error.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSN_PARAM_ERR: Interface [chars] is down (Isolation due to ELP failure: class N param error).Explanation Exchange link parameter (ELP) failed on the interface because of a class N parameter error.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PAYLOAD_SIZE: Interface [chars] is down (Isolation due to ELP failure: invalid payload size).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid payload size.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PORT_NAME: Interface [chars] is down (Isolation due to ELP failure: invalid port name).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid port name.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_SWITCH_NAME: Interface [chars] is down (Isolation due to ELP failure: invalid switch name).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid switch name.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_TX_BBCREDIT: Interface [chars] is down (Isolation due to ELP failure: loopback detected).Explanation Exchange link parameter (ELP) failed on the interface because loopback connection was detected.
Recommended Action Connect to a port on another switch and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_LOOPBACK_DETECTED: Interface [chars] is down (Isolation due to ELP failure: invalid transmit B2B credit).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid transmit B2B credit.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_RATOV_EDTOV_MISMATCH: Interface [chars] is down (Isolation due to ELP failure: R_A_TOV or E_D_TOV mismatch).Explanation Exchange link parameter (ELP) failed on the interface because of an R_A_TOV or E_D_TOV time-out value mismatch.
Recommended Action Configure R_A_TOV and E_D_TOV values correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_REVISION_MISMATCH: Interface [chars] is down (Isolation due to ELP failure: revision mismatch).Explanation Exchange link parameter (ELP) failed on the interface because of a revision mismatch.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_CODE: Interface [chars] is down (Isolation due to ELP failure: invalid flow control code).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid flow control code.
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_PARAM: Interface [chars] is down (Isolation due to ELP failure: invalid flow control param).Explanation Exchange link parameter (ELP) failed on the interface because of an invalid flow control parameter .
Recommended Action Configure the attached switch port correctly and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error Disabled - EPP Failure).Explanation Trunk protocol failed.
Recommended Action Enter the show port internal event-history msgs CLI command or use a similar Fabric Manager/Device Manager procedure to see the trunk protocol exchanges and determine why it failed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled).Explanation The interface encountered an error while configuring it.
Recommended Action Enter the show port internal all interface CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information about the failed interface. In most cases, you can recover by entering the shutdown and no shutdown CLI command or similar Fabric Manager/Device Manager procedure on the interface. If that does not work, remove and reinsert the fiber cable.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ESC failure).Explanation Exchange switch parameter (ESC) failed on the interface.
Recommended Action Enter the show port internal event-history CLI command or use a similar Fabric Manager/Device Manager procedure to determine the ESC protocol exchanges to determine how it failed.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port src interface down).Explanation Ethernet link to which the FCIP interface is bound is down.
Recommended Action Ensure that the Ethernet cable is connected and that the interface is administratively enabled.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port src interface link down).Explanation Ethernet link to which the FCIP interface is bound is down.
Recommended Action Ensure that the Ethernet cable is connected and the remote end is also active.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_FABRIC_BIND_FAILURE: Interface [chars] is down(Isolation due to fabric bind failure).Explanation Fabric binding failed on this port.
Recommended Action Check the fabric binding database to ensure that the remote port is allowed to connect to this port.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (Fcot not present).Explanation The Fibre Channel optical transceiver (SFP) has been removed.
Recommended Action Insert a Fibre Channel optical transceiver.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down (Error disabled - Fcot vendor not supported).Explanation The Fibre Channel optical transceiver inserted is not a supported one.
Recommended Action Contact your customer support representative for a list of authorized transceiver (SFP) vendors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_FCSP_AUTHENT_FAILURE: Interface [chars] is down (FC-SP authentication failure).Explanation The port failed Fibre Channel Security Protocol (FC-SP) authentication with its peer.
Recommended Action Check the FC-SP configuration.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_FICON_BEING_ENABLED: Interface [chars] is down(FICON being enabled).Explanation FICON is being enabled on the port.
Recommended Action FICON enable takes some time. No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_FICON_NOT_ENABLED: Interface [chars] is down(Error disabled - ficon not enabled).Explanation FICON is not enabled on the port.
Recommended Action Enable FICON on the port.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_FICON_VSAN_DOWN: Interface [chars] is down(FICON VSAN down).Explanation FICON is being enabled on the VSAN of this port. This is an intermediary state, whereby the port VSAN is being enabled to be a FICON VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure).Explanation The module hardware has failed.
Recommended Action Enter the show module internal all module command or use a similar Fabric Manager procedure to collect more information about the failed module.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive).Explanation The port VSAN has been suspended or deleted.
Recommended Action Assign a new active port VSAN to the interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down (Error disabled - Incompatible admin port mode).Explanation The configured mode is not supported on this interface.
Recommended Action Enter the show port internal info command or use a similar Fabric Manager procedure to determine the list of modes supported on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit).Explanation The configured receive B2B credit size is not supported.
Recommended Action Enter the show port internal info command or use a similar Fabric Manager procedure to get the allowed receive B2B credit size.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize).Explanation The configured receive buffer size is not supported.
Recommended Action Enter the show port internal info command or use a similar Fabric Manager procedure to get the allowed receive buffer size.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down (Error disabled - Incompatible admin port speed).Explanation The configured speed is not supported on this interface.
Recommended Action Enter the show port internal info command or use a similar Fabric Manager procedure to determine the range of speed supported on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down (Initializing).Explanation The interface is in the process of coming up.
Recommended Action If the interface is stuck in this state for a while, enter the show port internal event-history command or use a similar Fabric Manager procedure to determine what it is waiting for.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed).Explanation Interface was removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_INVALID_ATTACHMENT: Interface [chars] is down(Invalid attachment).Explanation The peer interface does not have the compatible security attributes.
Recommended Action Ensure that the peer interface has security attributes compatible with the local interface.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_INVALID_CONFIG: Interface [chars] is down(Error disabled - Possible PortChannel misconfiguration).Explanation The local and peer interface have a PortChannel membership misconfiguration.
Recommended Action Ensure that both the local and peer interfaces are either both members of the same PortChannel or are both not part of any PortChannel.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_INVALID_FABRIC_BINDING: Interface [chars] is down(Invalid fabric binding exchange).Explanation Fabric binding failed.
Recommended Action Check the fabric binding database.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link failure).Explanation The physical link has gone down.
Recommended Action Ensure that the cable is connected and the remote end is not shut down.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_LOCALLY_DISRUPTIVE_RECONFIGURATION: Interface [chars] is down (fcdomain applied a locally disruptive reconfiguration).Explanation Fcdomain applied a locally disruptive reconfiguration. The local domain became invalid.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure).Explanation Diagnostics failed on the interface.
Recommended Action Enter the attach module command or use a similar Fabric Manager procedure to connect to the module to collect more information about the failed interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down (Isolation due to port loopback to same switch).Explanation The interface is looped back to another interface on the same switch.
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module removed).Explanation Interface is down because the module was removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating).Explanation The loop interface has been put into nonparticipating mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_NONE: Interface [chars] is down (None).Explanation There is no apparent reason the interface is down.
Recommended Action Enter the show port internal all interface command or use a similar Fabric Manager procedure to determine why the interface went down.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_NOS_RCVD: Interface [chars] is down (NOS received).Explanation The physical link has gone down.
Recommended Action Ensure that the cable is connected and the remote end is not shut down.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-5-IF_DOWN_NO_TRUNK_OPER_VSANS_ISOLATION: Interface [chars] is down(Isolation due to no common VSANs with peer on trunk).Explanation The TE port is isolated because there are no common VSANs to be brought up with the peer port.
Recommended Action Check that there are common VSANs configured and allowed to come up between the ports.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline).Explanation The interface has been placed into the offline state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_OHMS_EXTERNAL_LB_TEST: Interface [chars] is down(External loopback test).Explanation The interface is down because it is running external loopback tests.
Recommended Action Wait until the tests complete.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_OLS_RCVD: Interface [chars] is down (OLS received).Explanation The physical link has gone down.
Recommended Action Verify that the cable is connected and the remote end is not shut down.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down).Explanation Parent interface is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. closed by peer).Explanation The FCIP peer connected to this interface closed the TCP connection.
Recommended Action Enter the show interface command or use a similar Fabric Manager procedure to provide the peer IP address of this FCIP interface. Check to see why the peer closed the TCP connection.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. reset by peer).Explanation TCP connection to the FCIP peer got reset.
Recommended Action Enter the show interface and show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Check to see why the peer reset the TCP connection.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_PORT_ACT_LICENSE_NOT_AVAILABLE: Interface [chars] is not allowed to come up (port activation license not available.Explanation Assign a port activation license to this port or install additional port activation licenses as needed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message PORT-5-IF_DOWN_PORT_BIND_FAILURE: Interface [chars] is down(Isolation due to port bind failure).Explanation Port binding failed on this port.
Recommended Action Check the port binding database to ensure that the remote port is allowed to connect to this port.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_PORT_BLOCKED: Interface [chars] is down(Port blocked due to FICON).Explanation The port has been blocked by the FICON configuration.
Recommended Action Unblock the port in the FICON configuration.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down (No operational members).Explanation This is a PortChannel interface and all its members are operationally down.
Recommended Action Enable at least one of the PortChannel members.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to port VSAN mismatch).Explanation The interface is isolated because of a mismatch in the configured port VSAN of the local and remote ends.
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and enter the shutdown and no shutdown CLI commands or use a similar Fabric Manager/Device Manager procedure to bring up the ports.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in progress).Explanation There is an RCF in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port software failure).Explanation The software servicing the data path on the port has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is down(Tunnel source module not online).Explanation The module that has the source port of this FCIP interface is not online.
Recommended Action The module that has the source port for the FCIP link is coming online. Enter the show module CLI command or use a similar Fabric Manager/Device Manager procedure to find the module status.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down (Tunnel port src interface unbound).Explanation The FCIP link port source interface is not bound.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel src port removed).Explanation The link source port of this FCIP interface has been removed. The source interface with the IP address that matches the IP address of the bound entity is removed. This happens normally because the module on which the source interface exists is removed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended).Explanation This interface belongs to a PortChannel and has been suspended because of an error while bringing it up.
Recommended Action In most cases, you can recover by entering the shutdown and no shutdown CLI commands or by using a similar Fabric Manager/Device Manager procedure. If this happens again, enter the show port internal all interface command or use a similar Fabric Manager procedure on the interface to gather more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode).Explanation This interface belongs to a PortChannel and the operational mode of the interface is different from that of the PortChannel.
Recommended Action Change the mode and the trunking mode of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed).Explanation This interface belongs to a PortChannel and the operational speed of the interface is different from that of the PortChannel.
Recommended Action Change the speed of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down (Suspended due to incompatible remote switch WWN).Explanation This interface belongs to a PortChannel and the remote switch WWN of the interface is different from that of the PortChannel.
Recommended Action Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is down(TCP conn. closed - Keep alive expired).Explanation The TCP session to the FCIP peer was closed because of the loss of the TCP keep alive.
Recommended Action You may have lost IP connection. Enter the show interface and show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter the traceries ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connectivity to the peer.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP conn. closed - retransmit failure).Explanation Interface is down buckeye it reached the maximum allowed retransmission failures.
Recommended Action This may be because of a loss of IP connectivity. Enter the show interface, show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter the traceroute ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connectivity to the peer.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is down(TCP conn. closed - Persist timer expired).Explanation TCP session to the FCIP peer closed because the TCP persist timer expired.
Recommended Action You may have lost IP connection. Enter the show interface, show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FC IP peer. Enter the traceroute ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connection to the peer.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_TOO_MANY_INVALID_FLOGIS: Interface [chars] is down(Suspended due to too many invalid flogis.Explanation The port is suspended because of receiving a large number of invalid FLOGIs.
Recommended Action Check the host bus adapter (HBA) and enter the shutdown and no shutdown CLI commands or use a similar Fabric Manager/Device Manager procedure on the port.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message PORT-5-IF_DOWN_TOO_MANY_INTR: Interface [chars] is down (Error disabled - too many interrupts).Explanation The port has received too many hardware interrupts.
Recommended Action Check the device attached to the port and replace it if needed.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message PORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down (Linecard upgrade in progress).Explanation Upgrade of the line card software is in progress.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_VIRTUAL_IVR_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to virtual IVR domain overlap).Explanation Isolated because of a virtual IVR domain overlap.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message PORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to VSAN mismatch).Explanation This is a trunking interface and the VSANs configured do not match the VSANs configured on the remote end.
Recommended Action Check the VSANs configured on the local end with the remote end.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to zone merge failure).Explanation The interface was isolated because of a failure during zone merge.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is down (Isolation due to remote zone server not responding).Explanation The interface was isolated because of a remote zone server not responding.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_REINITED_ON_COMPAT_FAILURE: Interface [chars] reinited as one or more configurations changed during compatibility check.Explanation Interface has been re-initialized due to rollback failure. In Generation 2 line cards, compatibility checking involves reserving required resources in a line card. When a compatibility check fails, a rollback is performed to restore the resources of the interface. Rollback failures require modification of the current configuration of the interface and reinitializing the interface.
Recommended Action Modify interface configurations and retry compatibility check.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PORT-5-IF_TRUNK_DOWN: Interface [chars], VSAN [chars] is down ([chars]).Explanation The interface is trunking. The VSAN is down because of the reason shown in the error message.
Recommended Action Enter the show interface, show port internal info interface vsan and show port internal event-history interface vsan CLI commands or use a similar Fabric Manager/Device Manager procedure to determine why this VSAN is down on this interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_TRUNK_UP: Interface [chars], VSAN [chars] is up.Explanation The interface is trunking, and the VSAN is up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-IF_UP: Interface [chars] is up [chars].Explanation Interface is up in the mode specified, if applicable.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT-5-MODULE_BRINGUP_NOT_ALLOWED: Not allowing module [dec] to come up for reason: [chars] ([hex]).Explanation Module is not allowed to be operational due to the current system state.
Recommended Action Check the global index allocation using the show port index-allocation CLI command. Also, check the module.'
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message PORT-5-MODULE_INDEX_RESTORE_ERROR: Error in restoring indices for module [dec]: reason [chars] ([hex]).Explanation Restore of module index may fail due to overlap of indices.
Recommended Action No action is required.
Error Message PORT-5-MODULE_UNLIMITED_OSM_SEQ_FAILED: Enable/Disable of unlimited oversubscription failed for module [dec].Explanation Interfaces of the module may be in an indeterminate state.
Recommended Action Reload the module.
Introduced Cisco MDS SAN-OS Release 3.1(1).
PORT-Resources Messages
This section contains the port resources (PORT-RESOURCES) messages.
Error Message PORT-RESOURCES-3-PRM_MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars].Explanation An attempt to send a message failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message PORT-RESOURCES-5-INVALID_PORT_ACTIV_PKG_LICENSE_FILE_INSTALLED: Invalid on demand port activation license file is installed for module [dec].Explanation Interfaces may not acquire port activation licenses during installation.
Recommended Action Install a valid port activation license file.
Introduced Cisco MDS SAN-OS Release 3.1(1).
PORT-SECURITY Messages (Deprecated)
This section contains the port security (PORT-SECURITY) messages. These messages were deprecated in Cisco MDS SAN-OS Release 1.3(4a). They were replaced by the "PORT_SECURITY Messages" section.
PORT-SECURITY-2
Error Message PORT-SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for [chars].Explanation Memory allocation failed for the entity and size shown in the error message.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to [chars].Explanation The feature is unavailable and will be disabled.
Recommended Action Install the correct license and reenable.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
PORT-SECURITY-3
Error Message PORT-SECURITY-3-BINDING_CONFLICT: [chars] in VSAN [dec].Explanation An already logged in device is in conflict with the port security manager (PSM) active binding configurations. The error message indicates the WWN of the login entity, interface and VSAN.
Recommended Action Use the autolearn feature with activation. This message is informational in nature, and the device will not be logged out. However, it will be denied login when it attempts to log in the next time.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-BINDING_VIOLATION: [chars] in VSAN [dec].Explanation A login occurred that violates the port security manager (PSM) binding configurations. The error message indicates the WWN of the login entity and the VSAN.
Recommended Action Only entries in the activated database of PSM can log in. Change the configuration and activate it again.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-3-CFS_NOTIF_ERR: [chars].Explanation An error occurred during the processing of a CFS notification. [chars] indicates the actual cause for the error.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message PORT-SECURITY-3-DB_ERR: [chars].Explanation An error occurred during a port security manager (PSM) database operation. The error message indicates the reason for the error.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-EFMD_FC2_OPER_FAILED: [chars].Explanation The exchange fabric membership data (EFMD) Fibre Channel Layer 2 (FC-2) operation 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 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-EFMD_INIT_FAILED: [chars].Explanation The exchange fabric membership data (EFMD) initialization 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 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars].Explanation Received a corrupted exchange fabric membership data (EFMD) request packet.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-INIT_FAIL: [chars].Explanation An error happened during port security manager initialization. The error message indicates the reason for failure.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-LEARNT_BINDING_CONFLICT: [chars] in VSAN [dec].Explanation An already logged in device that is learned during activation is in conflict with the port security manager active binding configurations. The error message indicates the WWN of the login entity, interface, and VSAN.
Recommended Action Copy the active database to the configuration database and reactivate. Not doing so could result in unexpected login rejects later with this interface.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-MTS_ERR: [chars].Explanation An error occurred in processing a messaging and transaction services (MTS) message. The error message indicates the error that occurred.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-PSS_ERR: [chars].Explanation An error occurred during a port security manager persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation that caused the error.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT-SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].Explanation There was a mismatch in the persistent storage service (PSS) version. The error message indicates the PSS service, its current version number, and the expected version.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
PORT-SECURITY-4
Error Message PORT-SECURITY-4-ACTIVATION_FAIL: [chars] in VSAN [dec].Explanation Activation of bindings failed because of the reason shown in the error message in the VSAN.
Recommended Action Correct the error and reactivate it.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
PORT-SECURITY-6
Error Message PORT-SECURITY-6-INFO: [chars].Explanation An event happened that affects the port security manager. The error message indicates the event.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 1.3(4a).
PORT_CHANNEL Messages
This section contains the PortChannel (PORT_CHANNEL) messages.
PORT_CHANNEL-1
Error Message PORT_CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed [[chars]].Explanation Module configuration failed.
Recommended Action The module is automatically reset. If the problem persists, contact your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec]).Explanation There is not enough memory.
Recommended Action Check if the system is low on memory and reset the switch if necessary.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for [chars] [[chars]].Explanation Parameter mapping failed.
Recommended Action The specified service is misbehaving. Check its status.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [chars]: [chars].Explanation Failed to send a multicast message to all modules, usually because some module went down.
Recommended Action Enter the show port-channel consistency CLI command or use a similar Fabric Manager/Device Manager procedure to check consistency.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-2
Error Message PORT_CHANNEL-2-RESET_MODULE: reset module [dec] for not responding or returning error.Explanation A module is reset for not responding or returning an error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-3
Error Message PORT_CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible.Explanation Compatibility check failed when adding ports to a PortChannel.
Recommended Action Make sure the compatibility parameters are consistent while adding ports to a PortChannel, or use the force option.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-3-GENERAL_ERROR: [chars].Explanation General error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars].Explanation Failed to send a message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found.Explanation Cannot find a PortChannel in its database, which indicates an inconsistency with an external component.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], state [chars]].Explanation Some operation timed out.
Recommended Action Execute the show port-channel consistency CLI command or use a similar Fabric Manager/Device Manager procedure to check all module connectivity and consistency.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-4
Error Message PORT_CHANNEL-4-PORT_CFG_DELETED: [chars] removed from PortChannel [dec] (different module inserted).Explanation Port is removed from a PortChannel because a different module was inserted to the same slot.
Recommended Action The system has lost some ports from the PortChannel. Add ports in the new module to the same PortChannel.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally individual.Explanation The port is operating as an individual link even though it is locally or remotely configured to be part of a PortChannel.
Recommended Action Check the configuration of the port locally and remotely to ensure that it can operate as part of a PortChannel.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message PORT_CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of PortChannel.Explanation Cannot find the port in the PortChannel database, which indicates an inconsistency with an external component.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-4-RACE_WARN: [chars].Explanation Warning of a possible race condition.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from [chars].Explanation Received an unexpected response and discarded it.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-5
Error Message PORT_CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars].Explanation The autocreate process on the port failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message PORT_CHANNEL-5-CREATED: [chars] created.Explanation A PortChannel was created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-5-DELETED: [chars] deleted.Explanation A PortChannel was deleted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-5-FOP_CHANGED: [chars]: first operational port changed from [chars] to [chars].Explanation The first operational port in a PortChannel was changed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come online because port channel interface <port-channel numberExplanation The port-channel number configured on the switch is larger than 128.
Recommended Action Delete the set of port channel interface <port-channel interface
Error Message PORT_CHANNEL-5-PORT_ADDED: [chars] added to [chars].Explanation Ports were added to a PortChannel.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-5-PORT_REMOVED: [chars] removed from [chars].Explanation Ports were removed from a PortChannel.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-6
Error Message PORT_CHANNEL-6-PORT_DOWN: [chars]: [chars] is down.Explanation Port went down in a PortChannel.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-6-PORT_UP: [chars]: [chars] is up.Explanation Port came up in a PortChannel.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-6-RESYNC: resyncing [chars] with all modules.Explanation Resynchronizing modules with the supervisor module after an error or switchover.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PORT_CHANNEL-7
Error Message PORT_CHANNEL-7-GSYNC_DONE: global synchronization is done.Explanation PortChannel manager finished global synchronization.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-GSYNC_REQ: requesting global synchronization.Explanation PortChannel manager requested a global synchronization from the active supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-START_ACTIVE: started in active mode.Explanation PortChannel manager started in active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-START_DEFAULT: started with default configuration.Explanation PortChannel manager started with the default configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-START_STANDBY: started in standby mode.Explanation PortChannel manager started in standby mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-START_STATEFUL: started statefully.Explanation PortChannel manager started with the running configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PORT_CHANNEL-7-START_STATELESS: started statelessly.Explanation PortChannel manager started with the startup configuration.
Recommended Action No action is required.
PORT_SECURITY Messages
This section contains the port security (PORT_SECURITY) messages.
PORT_SECURITY-2
Error Message PORT_SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for [chars].Explanation Memory allocation failed for the entity and size shown in the error message.
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(4a).
Error Message PORT_SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to [chars].Explanation The feature is unavailable and will be disabled now.
Recommended Action Install the correct license and reenable.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-3-BINDING_CONFLICT: [chars] in VSAN [dec].Explanation An already logged in device is in conflict with the port security manager active binding configuration. The error message indicates the WWN of the login entity, interface and the VSAN.
Recommended Action For port security, the autolearn feature can be used with activation to prevent this. This violating device or switch will be logged out.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-3-BINDING_VIOLATION: [chars] in VSAN [dec].Explanation A login occurred that violates the port security manager (PSM) binding configuration. The error message indicates the WWN of the login entity and the VSAN.
Recommended Action Only entries in the activated database of PSM can log in. Change the configuration and activate it again.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-3-DB_ERR: [chars].Explanation An error occurred during a port security manager database operation. The error message indicates the reason for the error.
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(4a).
Error Message PORT_SECURITY-3-EFMD_FC2_OPER_FAILED: [chars].Explanation The exchange fabric membership data (EFMD) Fibre Channel Layer 2 (FC-2) operation 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 1.3(4a).
Error Message PORT_SECURITY-3-EFMD_INIT_FAILED: [chars].Explanation The exchange fabric membership data (EFMD) initialization 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 1.3(4a).
Error Message PORT_SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars].Explanation Received a corrupted exchange fabric membership data (EFMD) request packet.
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(4a).
Error Message PORT_SECURITY-3-INIT_FAIL: [chars].Explanation An error happened during the port security manager initialization. The error message indicates the reason for failure.
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(4a).
Error Message PORT_SECURITY-3-LEARNT_BINDING_CONFLICT: [chars] in VSAN [dec].Explanation An already logged in device that is learned during activation is in conflict with the port security manager active binding configuration. The error message indicates the WWN of the login entity, interface, and VSAN.
Recommended Action Copy the active database to the configuration database and reactivate. Not doing so could result in unexpected login rejects later in that interface.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-3-MTS_ERR: [chars].Explanation An error occurred in processing of a message transaction service (MTS) message. The error message indicates the error that occurred.
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(4a).
Error Message PORT_SECURITY-3-PSS_ERR: [chars].Explanation An error occurred during a port security manager persistent storage service (PSS) operation. The error message indicates the PSS operation that caused the error.
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(4a).
Error Message PORT_SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].Explanation There was a mismatch in the persistent storage service (PSS) version. The error message indicates the PSS service, its current version number, and the expected version.
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(4a).
Error Message PORT_SECURITY-4-ACTIVATION_FAIL: [chars] in VSAN [dec].Explanation Activation of bindings failed in the VSAN because of the reason shown in the error message.
Recommended Action Correct the error and reactivate it.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message PORT_SECURITY-6-INFO: [chars].Explanation An event happened that affects the port security manager. The error message indicates the event.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
PROC_MGR Messages
This section contains the process manager (PROC_MGR) messages.
PROC_MGR-SLOT#-2
Error Message PROC_MGR-SLOT#-2-PROC_MGR_APP_CRIT_ERROR: ERROR: Critical error determined for app ([chars]) status=[dec] signal=[dec].Explanation Application caused critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_APP_EXITED: ERROR: Application ([chars]) exited with status=[dec] signal=[dec].Explanation Application exited.
Recommended Action Check the application.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error and linecard will be rebooted.Explanation Component caused critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_CRIT_ERROR: ERROR: Critical error determined for component ([chars]) errno=[dec].Explanation Critical error for component.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_DEP_FAIL: ERROR: Dependency failure - Component ([chars]) depends on ([chars]).Explanation Component dependency failure.
Recommended Action Check whether the component exists.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_NOT_INSTALLED: ERROR: Component ([chars]) could not be installed errno=[dec].Explanation Component not installed.
Recommended Action Check whether the component exists.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_TIMEOUT: ERROR: Component ([chars]) did not exit and time out occurred.Explanation Component initialization timed out.
Recommended Action Check the component.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_ERROR: [chars].Explanation Process manager error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_INFO: [chars].Explanation Process manager informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_MTS_CORE_CLIENT_FAIL: ERROR: MTS message to core_client FAILED errno=[dec].Explanation Message to core client failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_QUIT: Process manager quitting because: [chars].Explanation Process manager is quitting.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_RM_KLM_SCRIPT: Removed: KLM/Script [[chars]] in [dec] sec [dec] usec...Explanation Removed the kernel-loadable module (KLM) script.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_STOP_PROC: Process [[chars]] exited in [dec] sec [dec] usec...Explanation Process stopped.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_TERM_TIME: * Termination took [dec] sec [dec] usec *.Explanation Process manager termination time.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_PEEK_FAIL: ERROR: Unable to peek on utaker queue.Explanation Peek at utaker queue failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_ALLOC_FAIL: ERROR:Failed to allocate utaker semaphore: [dec].Explanation Utaker semaphore allocation failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_GET_FAIL: ERROR:[chars] [dec]: Failed to get utaker semaphore: [dec].Explanation Utaker semaphore get failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_GIVE_FAIL: ERROR:[chars] [dec]: Failed to give utaker semaphore: [dec].Explanation Utaker semaphore give failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_TAKE_FAIL: ERROR:[chars] [dec]: Failed to take utaker semaphore: [dec].Explanation Utaker semaphore take failed.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PROC_MGR-SLOT#-4
Error Message PROC_MGR-SLOT#-4-PROC_MGR_APP_NOT_RESP: ERROR: Process ([chars]) is not responding, it will be terminated.Explanation Application is not sending a heartbeat.
Recommended Action Check the application.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PSS Messages
This section contains the persistent storage service (PSS )messages.
PSS-0
Error Message PSS-0-PSS_NO_MORE_PAGES: [chars]: needs more working pages.Explanation Service needs more working page buffers.
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.2(2a).
Error Message PSS-0-PSS_READ_DATA_FAILURE: [chars]: failed to read data to [chars] block [dec]: [chars].Explanation The persistent storage service cannot read data.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-0-PSS_SYNC_DATA_FAILURE: [chars]: failed to sync data to [chars]: [chars].Explanation The persistent storage service cannot synchronize data because of a file system or disk error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-0-PSS_SYNC_LOG_FAILURE: [chars]: failed to sync log: [chars].Explanation The persistent storage service cannot synchronize the log because of a file system or disk error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-0-PSS_UNKNOWN_LOG: [chars]: unknown log type [hex] at offset [dec].Explanation Unknown logging entry found.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-0-PSS_WRITE_DATA_FAILURE: [chars]: failed to write data to [chars] block [dec]: [chars].Explanation The persistent storage service cannot write data because of a file system or disk error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-0-PSS_WRITE_LOG_FAILURE: [chars]: failed to write log: [chars].Explanation The persistent storage service cannot write the log because of a file system or disk error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PSS-1
Error Message PSS-1-PSS_INVALID_MAGIC: [chars]: database [chars] has invalid magic number [hex].Explanation The persistent storage service found a corrupted database with an invalid magic number.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-1-PSS_META_READ_ERROR: [chars]: cannot read meta page from [chars]: [chars].Explanation The persistent storage service cannot read the meta page of a database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-1-PSS_STAT_ERROR: [chars]: cannot stat [chars]: [chars].Explanation The persistent storage service cannot do FSTAT on a database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-1-PSS_VERSION_MISMATCH: [chars]: found version mismatch in [chars].Explanation The persistent storage service found a database whose format it cannot interpret because of a version mismatch.
Recommended Action The image upgrade was not done properly. Enter the write erase command or use a similar Fabric Manager procedure as a last recourse to clear this problem.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PSS-2
Error Message PSS-2-PSS_INVALID_SIZE: [chars]: database [chars] ([chars]) has invalid size [dec] (block size [dec]).Explanation The persistent storage service found a database with invalid size, probably because of a crash.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-2-PSS_MISSING_FILE: [chars]: database [chars] missing [chars] file.Explanation The persistent storage service database is incomplete, probably because of a crash.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-2-PSS_RECOVERY_FAILED: [chars]: failed to recover [chars].Explanation The persistent storage service recovery failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PSS-4
Error Message PSS-4-PSS_CLEANUP: [chars]: cleaning up [chars].Explanation The persistent storage service removed a leftover or corrupted file.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-4-PSS_RECOVERY_ENDED: [chars]: recovered [chars] successfully.Explanation The persistent storage service recovery finished.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-4-PSS_RECOVERY_STARTED: [chars]: recovering [chars]: [dec] valid transactional records.Explanation The persistent storage service started recovery of previous aborted transaction.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
PSS-5
Error Message PSS-5-PSS_CONVERT_FORMAT: [chars]: converting pss format: [chars].Explanation The persistent storage service format is being converted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-5-PSS_CONVERT_LAYOUT: [chars]: converting pss layout: [chars] (params [dec]/[dec]/[dec] -] [dec]/[dec]/[dec]).Explanation The persistent storage service layout is being converted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message PSS-5-PSS_SHRINK: [chars]: shrinking pss: [chars].Explanation The persistent storage service is being reduced to remove free space.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
QOS Messages
This section contains the quality of service (QOS) messages.
QOS-2
Error Message QOS-2-EXITING: Exit reason: [chars].Explanation The QoS manager process has exited. The process has probably been restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-2-GENERAL_ERROR: [chars].Explanation The QoS manager has encountered a critical error. The description of error is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-2-INITFAIL: QoS Manager Initialization failed: [chars].Explanation QoS manager initialization failed. The error message explains the reason for the failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-2-MALLOC_ERROR: Size [dec] bytes.Explanation The QoS manager could not allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.2(2a).
Error Message QOS-2-PSS_ERROR: [chars]: PSS returned value=[dec].Explanation The QoS manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars].Explanation The QoS manager has failed to rotate its current standard output file with the file name shown in the error message. The file size could grow beyond its maximum limit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
QOS-3
Error Message QOS-3-ALLOCFAIL: Heap Memory allocation failed: [chars].Explanation QoS manager is out of dynamic memory. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-DBERROR: [chars].Explanation QoS manager encountered a database error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-E_PORT_ACL_FAILURE: Failed to [chars] QOS ACL for interface [chars] (ACL return code=[hex]).Explanation The QoS manager failed to program or erase a QoS related ACL when an E port came up or went down for the interface. The error code returned by ACL module is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-3-FAILURE_RESPONSE: [chars] [hex].Explanation QoS manager failed to get a response. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-GENERROR: [chars].Explanation QoS manager encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-LICERR: [chars].Explanation QoS manager failed to get license.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-MTSERROR: [chars].Explanation QoS manager encountered a messaging and transaction service (MTS) error. The error message specifies the context where the error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-PSSERROR: [chars].Explanation QoS manager encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-QOS_PSS_CORRUPTED: [chars] PSS found corrupted.Explanation The QoS manager has detected corruption in one of its persistent information databases. The database will be recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-3-TIMEOUT_ERROR: [chars] [hex].Explanation QoS manager encountered a timeout. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec].Explanation The QoS manager has received an unknown message from the node and sap shown in the error message.This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
QOS-4
Error Message QOS-4-LICEXP: [chars].Explanation QoS manager license is going to expire. The error message gives the expected time of expiry.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec].Explanation There was a version mismatch between the QoS manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
QOS-6
Error Message QOS-6-BECAME_ACTIVE: Became ACTIVE from standby mode.Explanation The QoS manager on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-BECAME_STDBY: Became STANDBY from active mode.Explanation The QoS manager became standby from active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-DISABLED_UP_MARKING: [chars].Explanation The QoS manager has disabled marking of time-critical control traffic as high-priority traffic. Priority of such traffic is now not altered by QoS manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-E_PORT_ACL_SUCCESS: Successfully [chars] QOS ACL for interface [chars].Explanation The QoS manager has successfully programmed or erased QoS related ACL when an E port came up or went down for the interface shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-ENABLED_UP_MARKING: [chars].Explanation The QoS manager has enabled marking of time-critical control traffic as high-priority traffic.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-EXCESSIVE_DELAY: [chars].Explanation Excessive time taken for a processing event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars].Explanation The QoS manager was unable to send a heartbeat to the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-GENERAL_EVENT: [chars].Explanation The QoS manager has generated an important event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-MGRCREATED: QoS Manager created.Explanation QoS manager was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-6-MGREXIT: QoS Manager shutting down gracefully.Explanation QoS manager is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message QOS-6-PSS_CREATED: [chars] PSS Created.Explanation One of the persistent information database of QoS manager has been recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-PSS_DESTROYED: [chars] PSS Destroyed.Explanation One of the persistent information databases of QoS manager was intentionally destroyed and will be recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-SERVICE_UP: Initialized [chars].Explanation The QoS manager is up and ready to accept client requests The service was initialized in the mode shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release .
Error Message QOS-6-SWITCHOVER: Switching Over to other Supervisor.Explanation The QoS manager has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message QOS-6-UNKNOWNMTS: QoS Manager received an unexpected message.Explanation QoS Manager received an unexpected message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
RADIUS Messages
This section contains the Remote Authentication Dial-In User Service (RADIUS) messages.
RADIUS-2
Error Message RADIUS-2-RADIUS_NO_AUTHEN_INFO: ASCII authentication not supported.Explanation ASCII authentication not supported.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message RADIUS-2-RADIUS_PROGRAM_EXIT: RADIUS daemon exiting: [chars].Explanation RADIUS daemon is exiting.
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).
RADIUS-3
Error Message RADIUS-3-RADIUS_ERROR_MESSAGE: [chars].Explanation RADIUS error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
RADIUS-6
Error Message RADIUS-6-RADIUS_ACCOUNTING_MESSAGE: [chars].Explanation Accounting message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RADIUS-6-RADIUS_MESSAGE: [chars].Explanation RADIUS message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
RDL Messages
This section contains the remote domain lookup (RDL) messages.
RDL-3
Error Message RDL-3-SYSLOG_ALLOC_FAIL: : [chars].Explanation The remote domain lookup (RDL) memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec].Explanation The remote domain lookup (RDL) context error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-3-SYSLOG_ERR: : [chars].Explanation The remote domain lookup (RDL) syslog errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-3-SYSLOG_EXIT: : [chars].Explanation The remote domain lookup (RDL) exiting on errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars].Explanation The remote domain lookup (RDL) initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-3-SYSLOG_MTS_ERR: : [chars].Explanation The remote domain lookup (RDL) messaging and transaction service (MTS) errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RDL-6
Error Message RDL-6-SYSLOG_DEBUG_1: : [chars] [hex].Explanation The remote domain lookup (RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-6-SYSLOG_DEBUG_2: : [chars] [hex].Explanation The remote domain lookup (RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-6-SYSLOG_INFO: : [chars].Explanation The remote domain lookup (RDL) debug logs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec].Explanation The remote domain lookup (RDL) context error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RIB Messages
This section contains the Routing Information Base (RIB) messages.
RIB-0
Error Message RIB-0-EMERG: [chars].Explanation The Routing Information Base (RIB) caused a system failure.
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.2(2a).
RIB-1
Error Message RIB-1-ALERT: [chars].Explanation The Routing Information Base (RIB) caused failures in other services.
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.2(2a).
RIB-2
Error Message RIB-2-CRIT: [chars].Explanation The Routing Information Base (RIB) encountered a catastrophic error.
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.2(2a).
RIB-3
Error Message RIB-3-ERR: [chars].Explanation The Routing Information Base (RIB) encountered an error.
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.2(2a).
Error Message RIB-3-FIB_EXIT: fib exited.Explanation The Forwarding Information Base (FIB) had exited and may not continue operation.
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.2(2a).
Error Message RIB-3-MISS_APPS: Missing response from service.Explanation Service not responding to the Routing Information Base (RIB).
Recommended Action Enter the debug rib error command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RIB-3-NO_MEM: Out of memory.Explanation The Routing Information Base (RIB) does not have enough memory to continue proper operation.
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.2(2a).
Error Message RIB-3-SEND_FIB: Cannot talk to fib.Explanation The Routing Information Base (RIB) to the Forwarding Information Base (FIB) interprocess communication (IPC) failure.
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.2(2a).
Error Message RIB-3-SEND_SNMP: Cannot respond to snmp.Explanation The Routing Information Base (RIB) to SNMP interprocess communication failure.
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.2(2a).
Error Message RIB-3-SEND_STANDBY: Cannot talk to standby rib.Explanation Lost a Routing Information Base (RIB) to Forwarding Information Base (FIB) transaction log due to an interprocess communications (IPC) failure.
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.2(2a).
RIB-4
Error Message RIB-4-CPU_HOG: Inactive or busy.Explanation Either the Routing Information Base (RIB) was not scheduled to run, or RIB was busy, and RIB did not service the message or timer queue for an extended period.
Recommended Action Enter the debug rib error command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RIB-4-DUP_FIB: Duplicate response from fib.Explanation The Routing Information Base (RIB) ignored duplicate response from the Forwarding Information Base (FIB).
Recommended Action Enter the debug rib error command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RIB-4-LATE_FIB: Late response from fib.Explanation The Routing Information Base (RIB) ignored late response from the Forwarding Information Base (FIB).
Recommended Action Enter the debug rib error command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RIB-4-PC_LIMIT: PC number greater than 128 (ignored by RIB).Explanation The Routing Information Base (RIB) ignored the PC because the PC number was greater than 128.
Recommended Action Use a PC number less than 128.
Introduced Cisco MDS SAN-OS Release 3.1(2).
Error Message RIB-4-WARN: [chars].Explanation The Routing Information Base (RIB) ignored the unexpected condition.
Recommended Action Enter the debug rib all command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RIB-5
Error Message RIB-5-NOTE: [chars].Explanation The Routing Information Base (RIB) does not support this operation.
Recommended Action Enter the debug rib all command, or use a similar Fabric Manager procedure, then recreate the operation scenario to find out more details.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RIB-6
Error Message RIB-6-INFO: [chars].Explanation The Routing Information Base (RIB) event occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RLIR Messages
This section contains the Registered Link Incident Record (RLIR) messages.
RLIR-2
Error Message RLIR-2-DRLIR_REJECT: DRLIR rejected: [chars]: fcid [chars], reason code [dec].Explanation Distributed Registered Link Incident Record (DRLIR) was rejected. The FC ID and reason code are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-2-FC2_FAILED: RLIR FC2 operation failed: [chars]: [chars].Explanation Registered Link Incident Record (RLIR) Fibre Channel Layer 2 (FC-2) operation failed: [chars] [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-2-INIT_FAILED: RLIR Init failed: [chars].Explanation Registered Link Incident Record (RLIR) initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-2-LINK_INCIDENT: Interface [chars] [Port [hex]], Link Status: [chars], Link Status Reason: [chars].Explanation Registered Link Incident Record (RLIR) module detected an unintentional link incident.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message RLIR-2-MALLOC_FAILED: RLIR Malloc failed: [chars].Explanation Registered Link Incident Record (RLIR) memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-2-MTS_FAILED: RLIR MTS operation failed: [chars]: [chars].Explanation Registered Link Incident Record (RLIR) messaging and transaction service (MTS) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-2-PSS_FAILED: RLIR PSS operation failed: [chars]: [chars].Explanation Registered Link Incident Record (RLIR) persistent storage service (PSS) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
RLIR-6
Error Message RLIR-6-SYSLOG_INFO: RLIR Syslog info: [chars].Explanation Registered Link Incident Record (RLIR) syslog info.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message RLIR-6-SYSLOG_STATUS: RLIR Syslog status: [chars]: [chars].Explanation Registered Link Incident Record (RLIR) syslog status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
RM Messages
This section contains the resource manager (RM) messages.
RM-6
Error Message RM-6-RMGR_INFO: [chars].Explanation This is a resource manager informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message RM-6-STARTING: deamon started.Explanation The resource manager daemon successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
RM-SLOT# Messages
This section contains the resource manager slot (RM-SLOT#) messages.
RM-SLOT#-2
Error Message RM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error SSM will be rebooted.Explanation The listed component caused a critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message RM-SLOT#-2-RM_CPP_RELOAD_TMOUT: ERROR: Component ([chars]) timedout for critical error response reloading ILC.Explanation The listed component had a critical error timeout.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message RM-SLOT#-2-RM_VICPP_RECREATE_ERROR: All the fast path resources are down VICPP connectivity lost.Explanation The listed component caused a critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
RSCN Messages
This section contains the Registered State Change Notification (RSCN) messages.
RSCN-2
Error Message RSCN-2-FC2_FAILED: RSCN FC2 operation failed: [chars]: [chars].Explanation The Registered State Change Notification (RSCN) Fibre Channel Layer 2 (FC-2) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-INIT_FAILED: RSCN Init failed: [chars].Explanation The Registered State Change Notification (RSCN) initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-MALLOC_FAILED: RSCN Malloc failed: [chars].Explanation The Registered State Change Notification (RSCN) memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-MTS_FAILED: RSCN MTS operation failed: [chars]: [chars].Explanation The Registered State Change Notification (RSCN) messaging and transactional services (MTS) operation failed
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-PSS_FAILED: RSCN PSS operation failed: [chars]: [chars].Explanation The Registered State Change Notification (RSCN) persistent storage service (PSS) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-RSCN_REJECT: RSCN rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars].Explanation The Registered State Change Notification (RSCN) was rejected. The FC ID and reason code are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-SCR_REJECT: SCR rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars].Explanation The Registered State Change Notification (RSCN) was rejected. The FC ID and reason code are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-2-SWRSCN_REJECT: SW-RSCN rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars].Explanation The Registered State Change Notification (RSCN) was rejected. The FC ID and reason code are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
RSCN-4
Error Message RSCN-4-SWRSCN_REJECT: SW-RSCN rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars].Explanation SW-RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release3.2(1).
RSCN-6
Error Message RSCN-6-SYSLOG_INFO: RSCN Syslog info: [chars].Explanation The Registered State Change Notification (RSCN) syslog info.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message RSCN-6-SYSLOG_STATUS: RSCN Syslog status: [chars]: [chars].Explanation The Registered State Change Notification (RSCN) syslog status.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SAN_EXT_TUNER Messages
This section contains the SAN extension tuner (SAN_EXT_TUNER) messages.
SAN_EXT_TUNER-3
Error Message SAN_EXT_TUNER-3-SAN_EXT_TUNER_LICENSE_EXPIRED: SAN Extension Licence expired - Disabling SAN Extension Tuner.Explanation The SAN extension license expired or is not present. The SAN extension tuner will be disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCHEDULER Messages
This section contains the scheduler messages.
SCHEDULER-2
Error Message SCHEDULER-2-SCH_SYSLOG_MALLOC_ERR: Out of memory: [chars].Explanation Process memory exhausted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCHEDULER-2-SCH_SYSLOG_MTS_ERR: MTS error: [chars].Explanation Messaging and Transaction Service (MTS) operation failure.
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.0(1b).
Error Message SCHEDULER-2-SCH_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec].Explanation Persistent storage service (PSS) snapshot error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCHEDULER-2-SCH_SYSLOG_SDWRAP_ERR: Debug infrastructure initialization failed: [chars].Explanation Debug infrastructure failed to initialize.
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.0(1b).
SCHEDULER-3
Error Message SCHEDULER-3-SCH_ERR: [chars].Explanation Scheduler error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCHEDULER-3-SCH_SYSLOG_FILE_ERR: [chars] Error:[chars].Explanation File handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCHEDULER-3-SCH_SYSLOG_MTS_ERR: message [chars].Explanation Messaging and transaction service (MTS) message handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCHEDULER-3-SCH_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] Error:[dec].Explanation Error while performing input/output to the persistent storage service (PSS).
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.0(1b).
Error Message SCHEDULER-3-SCH_SYSLOG_USER_ERR: Description: Failed to execute job for user id [chars] Error:[dec].Explanation Error while attempting to execute job for user. The user maybe removed from the system.
Recommended Action Ensure that the user exists. Make sure the user is not remotely authenticated.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCHEDULER-4
Error Message SCHEDULER-4-SCH_WARN: [chars].Explanation Scheduler warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCHEDULER-6
Error Message SCHEDULER-6-SCH_MSG: [chars].Explanation Scheduler informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCSI target Messages
This section contains the SCSI target (SCSI target) messages.
SCSI target-2
Error Message SCSI target-2-PROC_ADD_NPORT_FAIL: Failed to set local nport with SCSI target driver error: [hex].Explanation SCSI target process added an N port with its peer kernel driver listed. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-2-PROC_OPEN_VHBA_DEVICE_FAIL: Failed to communicate with SCSI target driver error: [hex].Explanation SCSI target process failed to communicate with its peer kernel driver listed in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-2-PROC_SET_SCSI_INDEX_FAIL: Failed to set SCSI index SCSI target driver error: [hex].Explanation SCSI target process failed to set SCSI index with its peer kernel driver. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-2-PROC_WWNM_GET_WWN_FAIL: Failed to get local controller pwwn from WWN Manager error: [hex] response: [hex].Explanation SCSI target process used the wwnm_bwt_get_local_controller_wwn() API for the port WWN and it failed because of the error and response code listed. No SCSI discovery can be performed.
Recommended Action Enter the show process cpu and show system internal sysmgr service all commands or use a similar Fabric Manager/Device Manager procedure to collect further information. See WWN Manager system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) initialization failed due to the error listed. No SCSI discovery can be performed.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCSI target-3
Error Message SCSI target-3-PROC_VSAN_GET_RATOV_FAIL: Failed to get vsan attribute RATOV from VSAN Manager, error: [hex].Explanation SCSI target process used the vsan_get_global_value() API for RATOV and it failed because of the error listed.
Recommended Action This is a non-fatal error. The default value for RATOV is used. Enter the show process cpu and show system internal sysmgr service all commands or use a similar Fabric Manager/Device Manager procedure to collect more information. See the VSAN Manager system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_CREATE_FAIL: pss create runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) had a create runtime database failure because of the error listed. No SCSI discovery can be performed.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) delete runtime entry key failed because of the error shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) set runtime max key failed because of the error listed. No SCSI discovery can be performed.
Recommended Action Enter the show flash command or use a similar Fabric Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) set runtime max value failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash command or similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) open runtime database failed because of the error listed. No SCSI discovery can be performed.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) reload runtime database failed because of the error listed.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to uri:[chars] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) snapshot of runtime debug to uri failed because of the error listed.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) snapshot of runtime to uri failed because of the error shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SCSI target-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) store runtime entry key failed because of the error shown in the error message.
Recommended Action Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SCSI target-7
Error Message SCSI target-7-SCSI_TARGET_DISCOVERED: SCSI target discovered VSAN:[dec] FCID:[hex] prlisparm:[hex].Explanation SCSI target process discovered a VSAN with the FC ID and PRLI service parameter shown in the error message
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SAN Device Virtualization Messages
This section contains SAN Device Virtualization (SDV) messages.
SDV-6
Error Message SDV-6-BCAST_NOT_SUPPORTED: Broadcast attribute will be ignored for SDV devices.Explanation A broadcast attribute will be ignored for SAN Device Virtualization (SDV) devices.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(2).
SECURITYD Messages
This section contains the security and accounting daemon (SECURITYD) messages.
SECURITYD-2
Error Message SECURITYD-2-FIPS_BYPASS_SELF_TEST_STATUS: FIPS Bypass self-test status : [chars].Explanation Status of the FIPS self-test.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-FIPS_CRNG_SELF_TEST_STATUS: FIPS CRNG self-test status : [chars].Explanation Status of the FIPS self-test.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-FIPS_CRYPTO_SELF_TEST_STATUS: FIPS [chars] Crypto self-test status : [chars].Explanation Status of the FIPS self-test.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-FIPS_IMAGE_INTEGRITY_SELF_TEST_STATUS: FIPS Image Integrity self-test status : [chars].Explanation Status of the FIPS self-test.
Recommended Action No action is required.
Error Message SECURITYD-2-FIPS_POWERUP_SELF_TEST_STATUS: FIPS [chars] power-up self-test status : [chars].Explanation Status of the FIPS power-up self-test.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-FIPS_POWERUP_SELF_TESTS_STATUS: FIPS power-up self-test status: [chars].Explanation Status of the FIPS self-test.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-FIPS_SELF_TEST_FAILED: FIPS self-test failure : [chars] : [chars].Explanation The FIPS self-test failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-2-PROGRAM_EXIT: security/accounting daemon exiting: [chars].Explanation Security and accounting daemon is exiting.
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.2(2a).
SECURITYD-3
Error Message SECURITYD-3-NVRAMFAILURE: nvram failure.Explanation NVRAM cannot be read or written to. The accounting log cannot be stored.
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.2(2a).
SECURITYD-6
Error Message SECURITYD-6-ACCOUNTING_MESSAGE: [chars].Explanation Accounting message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SECURITYD-6-CHANGE_PASSWD: changing passwd for [chars].Explanation Changing password for the entity listed in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SECURITYD-6-DELETE_STALE_USER_ACCOUNT: deleting expired user account:[chars].Explanation Deleting expired user account.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SECURITYD-6-FIPS_MODE_SET: FIPS mode is [chars] for service [chars].Explanation FIPS mode is changed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SECURITYD-6-FIPS_MODE_SET_FAILED: Error when setting FIPS mode : [chars].Explanation FIPS mode failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
SENSOR Messages
This section contains the sensor messages.
SENSOR-2
Error Message SENSOR-2-SNSM_SYSLOG_INIT_FAILED: Sensor Mgr Initialization failed. Component [chars].Explanation Sensor Manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down: [chars].Explanation Sensor Manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation failed.Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SENSOR-3
Error Message SENSOR-3-MSG_SNSM_SYS_MEM_ALOC_FAILURE: Sensor Mgr Error in allocing mem: [dec], Error code = [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-3-SNSM_SYS_DEQUE_PENDING_QUE_FAILURE: Sensor Mgr Error in Dequing pend Que: [dec], Error code = [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-3-SNSM_SYS_ENQUE_PENDING_QUE_FAILED: Sensor Mgr Error in queuing to pending queue: [dec], Error code = [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-3-SNSM_SYS_MTS_RECV_FAILURE: Sensor Mgr Error in receving MTS mesg: [dec], Error code = [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-3-SNSM_SYSLOG_BAD_MTS_MSG: Sensor Mgr Received bad MTS message: [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SENSOR-3-SNSM_SYSLOG_MTS_PROCESS_ERROR: Sensor Mgr Error in processing MTS message: [dec], Error code = [dec].Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SENSOR-5
Error Message SENSOR-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started.Explanation Sensor manager syslog message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SENSOR_USD Messages
This section contains the Sensor Manager messages.
SENSOR_USD-2
Error Message SENSOR_USD-2-SNSM_SYSLOG_INIT_FAILED: Sensor Mgr Initialization failed. Component [chars].Explanation This is an informational message indicating that the Sensor Manager initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down: [chars].Explanation This is an informational message indicating that the Sensor Manager is shutting down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation failed.Explanation This is an informational message indicating that the Sensor Manager memory allocation is shutting down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
SENSOR_USD-3
Error Message SENSOR_USD-3-MSG_SNSM_SYS_MEM_ALOC_FAILURE: Sensor Mgr Error in allocing mem: [dec], Error code = [dec].Explanation This is an informational message identifying an error in allocating memory.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-3-SNSM_SYS_DEQUE_PENDING_QUE_FAILURE: Sensor Mgr Error in Dequing pend Que: [dec], Error code = [dec].Explanation This is an informational message indicating an error in the dequeuing process.
Recommended Action No action is required.
Error Message SENSOR_USD-3-SNSM_SYS_ENQUE_PENDING_QUE_FAILED: Sensor Mgr Error in queuing to pending queue: [dec], Error code = [dec].Explanation This is an informational message indicating an error in the queuing process.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-3-SNSM_SYS_MTS_RECV_FAILURE: Sensor Mgr Error in receving MTS mesg: [dec], Error code = [dec].Explanation This is an informational message indicating a receiving error from the messaging and transaction service (MTS).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-3-SNSM_SYSLOG_BAD_MTS_MSG: Sensor Mgr Received bad MTS message: [dec].Explanation This is an informational message indicating a bad message was received from the messaging and transaction service (MTS).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SENSOR_USD-3-SNSM_SYSLOG_MTS_PROCESS_ERROR: Sensor Mgr Error in processing MTS message: [dec], Error code = [dec].Explanation This is an informational message indicating an error occurred while processing a message from the messaging and transaction service (MTS).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
SENSOR_USD-5
Error Message SENSOR_USD-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started.Explanation This is an informational message indicating the Sensor Manager process began.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
SFC Messages
This section contains the SCSI flow control (SFC) messages.
SFC-3
Error Message SFC-3-ERROR: [chars].Explanation SCSI flow client encountered the listed error.
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.0(1b).
SFM Messages
This section contains the SCSI Flow Manager (SFM) messages.
SFM-2
Error Message SFM-2-NO_LICENSE_WARNING: SCSI Flow Manager is shutting down as no license is available.Explanation License required for continued SCSI flow manager operation is not available.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SFM-6
Error Message SFM-6-LICENSE_VALID: A valid license for SCSI FLow Manager has been obtained.Explanation A valid license for SCSI flow manager has been obtained.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
SME_CPP Messages
This section contains the StorageMedia Encryption License (SME) messages.
SME_CPP-2
Error Message SME_CPP-2-LOG_ERR_SME_LICENSE_EXPIRED: SME Licence expired - Disabling [chars].Explanation Storage Media Encryption License expired or is not present. SME is disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-2-LOG_WARN_SME_LICENSE_GRACE: No SME License. Feature will be shut down after a grace period of approximately [dec] days.Explanation SME feature is on grace period. Acquire an actual license.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-2-SME_INIT_FAILED: Initialization failed for SME: [chars], Reason: [hex].Explanation Initialization failed for SME.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SME_CPP-3
Error Message SME_CPP-3-LOG_ERR_SME_DBSYBC_REJECT_CLUSTER_ALREADY_EXISTS: Database Synchronization for a new cluster (id %llx) rejected because another SME cluster (name , id %llx) already exists.Explanation A switch can be part of only one SME cluster.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CLUSTER_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] and security mode [dec], but the DPP has state from a previous instance of a cluster [chars] with ID [chars] and security mode [dec].Explanation DPP has persistent state about a previous cluster membership incarnation, but the interface is part of a different cluster.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars], but the DPP is identified as [chars].Explanation DPP has persistent state about a previous cluster membership on a different switch or module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SME_CPP-4
Error Message SME_CPP-4-LOG_ERR_SME_INTF_MISMATCH_NOT_PART_OF_ANY_CLUSTER: SME interface [chars] not part of any cluster, but the DPP has state from a previous instance of a cluster [chars] with ID [chars].Explanation DPP has persistent state about a previous cluster membership incarnation, but the interface is not part of any cluster.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-4-LOG_ERR_SME_INTF_MISMATCH_NOT_PROVISIONED: SME interface [chars] not provisioned, but the DPP has state from a previous instance of a cluster [chars] with ID [chars].Explanation DPP has persistent state about a previous cluster membership incarnation, but the switch has not provisioned the interface for SME.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_ITL_MISCONFIG: Different physical LUNs under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:[chars] Serial Num:[chars] Serial Num:[chars].Explanation Different physical LogicalUnit numbers exist or occur on the same tape device.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SME_CPP-5
Error Message SME_CPP-5-SME_DISABLED: SME Disabled.Explanation SME service is Disabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-5-SME_ENABLED: SME Enabled.Explanation SME service is enabled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SME_CPP-SLOT#-2
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_ITL_MISCONFIG: Different physical LUNs under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Ld Serial Num:[chars] Serial Num:[chars].Explanation Different physical Logical unit numbers are on the same tape device.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_LUN_MISCONFIG: Different physical LUNs under same ITL - Old Serial Num:[chars] New Serial Num:[chars].Explanation Different physical Logical unit numbers are on the same ITL.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SME_CPP-SLOT#-3
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_TAPE_MISCONFIG: A disk misconfigured under tape config - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Ld.Explanation A disk is misconfigured in the tape configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(2).
SKSD Message
Error Message SKSD-5-SKSD_MKEY_INSTALL: Installing a Master Key on the smartcard(s).Explanation Installing a new Master Key on the smart card(s).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
SPAN Messages
This section contains the switched port analyzer (SPAN) messages.
SPAN-2
Error Message SPAN-2-MEM_FULL: Memory allocation failed.Explanation Memory allocation 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 1.2(2a).
SPAN-3
Error Message SPAN-3-IPC_FAIL: IPC Error.Explanation Internal interprocess communications (IPC) error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-3-STATELESS_RESTART: Span is restarting stateless.Explanation Because of an unrecoverable error, the switched port analyzer (SPAN) is starting stateless. The currently active sessions will not be preserved. You will have to reenter the entire configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message SPAN-3-STATELESS_RESTART_ON_ACTIVE: Span is restarting as Span on active sup was restarted stateless.Explanation Because of an unrecoverable error, the switched port analyzer (SPAN) on the active supervisor was restarted stateless. The standby SPAN restarts to get in sync with the stateless SPAN on the active supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message SPAN-3-SYSINFO_TIMEOUT: Span timed out waiting for response from port manager for sys info.Explanation The switched port analyzer (SPAN) request for critical system information from the port manager has timed out. SPAN is exiting and the system manager will restart SPAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SPAN-3-SYSINFO_TIMEOUT: Span timed out waiting for response from port manager for sys info.Explanation The switched port analyzer (SPAN) request for critical system information from the port manager timed out. SPAN is exiting and the system manager will restart SPAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SPAN-5
Error Message SPAN-5-ATL_VSAN_DEFAULT_ALL: Default to all VSANs for SPAN egress session.Explanation Generation 2 fabric switches support only one VSAN filter for an egress SPAN session. If a VSAN is specified, SPAN will default to use all VSANs for the egress SPAN session.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SPAN-5-SPAN_CFG_REJECT_SRC_VSAN_FILTER_NOT_SUPPORTED: Source interface [[chars]] in dir [[chars]] removed from session [[dec]].Explanation Interface level VSAN filters are not supported.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-5-SPAN_CFG_REJECT_VSAN_SRC_PRESENT: Source VSAN [[dec]] removed from session [[dec]].Explanation Source VSANs were removed from the session because mixing of the interface and VSANs is not supported.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-5-SPAN_PSS_CORRUPTION: Span is starting stateless due to pss corruption.Explanation Because of an unrecoverable persistent storage service (PSS) corruption error, the switched port analyzer (SPAN) starts stateless without any configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-5-STATELESS_RESTART: Span is restarting stateless.Explanation Because of an unrecoverable error, the switched port analyzer (SPAN) is starting stateless. The currently active sessions will not be preserved. You will have to reenter the entire configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SPAN-5-STATELESS_RESTART_ON_ACTIVE: Span is restarting as Span on active sup was restarted stateless.Explanation Because of an unrecoverable error, the switched port analyzer (SPAN) on the active supervisor was restarted stateless. So, the standby SPAN restarts to get in sync with the stateless SPAN on the active supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SPAN-6
Error Message SPAN-6-SESSION_DOWN: Session [dec] is inactive ([chars]).Explanation Session is inactive now. Traffic for this session is no longer spanned.
Recommended Action Check the reason for session inactivity by entering the show span session CLI command or by using a similar Fabric Manager/Device Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-6-SESSION_UP: Session [dec] is active, destination SD port [chars].Explanation Session is active now. You can monitor spanned traffic at the destination SD port.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SPAN-6-STATELESS_SWITCHOVER: Span is starting stateless after switchover.Explanation Active sessions are not preserved across switchover. The switched port analyzer (SPAN) is starting stateless and the configuration will be reapplied to get back the active configuration.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SPI Messages
This section contains the SPI messages.
SPI_SLOT#-2
Error Message SPI-SLOT#-2-SPI_INFO: [chars]Explanation SPI Informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
SVC Messages
This section contains the SAN Volume Controller (SVC) messages.
SVC-0
Error Message SVC-0-NODE_EMERG_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-1
Error Message SVC-1-NODE_ALERT_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-2
Error Message SVC-2-NODE_CRIT_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-2-SVC_SYSLOG_INIT_FAILED: Initialization failed for SVC: [chars], Reason: [hex].Explanation Initialization failed for the SAN Volume Controller (SVC).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SVC-2-SVC_SYSLOG_NO_PORT_CHAN: Too many PortChannels allocated by user for interface [chars].Explanation The SAN Volume Controller (SVC) interface needs PortChannels to operate. Too many PortChannels have been allocated by the user for the interface to operate correctly.
Recommended Action Delete unneeded user configured PortChannels and shut down the SVC interface. Then bring the SVC interface back up.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SVC-2-SVC_SYSLOG_PATH_FAILURE: System Health detected SVC packet path failure for [chars].Explanation The Caching Services Module (CSM) has been brought down by the System Health monitor. System health has detected a failure in the packet path between the SAN Volume Controller (SVC) interface on the CSM and the backplane. This system health test is run periodically.
Recommended Action Enter the no shutdown command or use a similar Fabric Manager/Device Manager procedure on the SVC interface to bring the node back online. If a subsequent packet path failure occurs, replace the CSM module.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SVC-2-SVC_SYSLOG_PORT_FAILURE: System Health indicated port loopback failure for [chars].Explanation The SAN Volume Controller (SVC) interface has been brought down because of a port loopback failure.
Recommended Action Bring the port back up using either the CLI or Cisco Fabric Manager/Device Manager. Using the CLI, enter the no shutdown command on the SVC interface to bring the port back up. If a subsequent port loopback failure occurs, replace the SVC module.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SVC-2-SVC_SYSLOG_URIFS_FAILURE: [chars] is unreachable for reason: [chars].Explanation The SAN Volume Controller (SVC) interface modflash is not accessible. Modflash is the name of the file system local to the SVC interface and is typically used for core dumps and temporary file transfers.
Recommended Action Shut down then bring up the SVC interface in question to regain access to the modflash file system.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
SVC-3
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_ACTIVATE_CLUSTER_IP_FAILED ) Activate cluster IP failed [chars].Explanation Unable to activate the cluster IP for the config node.It will not be possible to execute configuration commands.
Recommended Action 1. Shutting the interfaces of the node will force this node out of the cluster and cause another node to become the config node, which should restore the ability to execute configuration commands. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_FAILURE ) Battery Failed [chars].Explanation The battery module on the Caching Services Module (CSM) has failed. The nodes on the CSM shut down. Other log entries may accompany this error.
Recommended Action Reload the CSM. If the error persists, replace the CSM.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DISK_FAILURE ) Internal Disk Drive Failed [chars].Explanation The internal disk drive for the node on the Caching Services Module (CSM) has failed.The node shut down. Other log entries may accompany this error.
Recommended Action Reload the CSM. If the error persists, replace the CSM.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DUMP_RESTORE_FAILED ) Restore of hardened data failed [chars].Explanation Restore of customer data failed. This error will be accompanied by other log entries.
Recommended Action Examine the log for other error entries and follow the actions recommended. If no other entries are found: 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask your support representative for assistance. It may be necessary to replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INVALID_BATT_CAPACITY ) Get battery capacity failed [chars].Explanation The process cannot get the battery capacity, possibly because of communication failures with the control plane processor (CPP) in the line card. The node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps:1. Reinstall the code on the line card. The node(s) will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. Replace the Caching Services Module, if the error persists.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_OPEN_COMMITTED_FILE_FAILED ) Error attempting to open file [chars].Explanation Process cannot open the committed file. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps:1. Reinstall the code on the line card. The node(s) will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. Replace the Caching Services Module, if the error persists.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_SET_BATT_THRESHOLD_FAILED ) Set battery threshold failed [chars].Explanation The process cannot set the battery threshold, possibly because of fatal communication failures with the power management module in the line card or the power management module has crashed. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps:1. Reinstall the code on the line card. The node(s) will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. Replace the Caching Services Module, if the error persists.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_NODE_DISENFRANCHISED ) Node missing [chars].Explanation A node is missing from the cluster.
Recommended Action 1. Check the status of the nodes and find the node with a status of offline. 2. Repair the failing node. When the repair has been completed, this error will automatically be marked as fixed. 3. Check the node status. If all the nodes in the cluster are now online, but the error in the log has not been marked as fixed, manually mark the error as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_CLUSTER_PATH_FAILURE ) Cluster path failure [chars].Explanation A cluster path has failed. The node cannot communicate with all the other nodes in the cluster.
Recommended Action 1. Repair the Fibre Channel network fabric. 2. Check the status of the node port. If the status of the port shows as online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_CPU_QUANTITY ) Processor change detected [chars].Explanation The Caching Services Module (CSM) is failing.
Recommended Action 1. Replace the CSM. 2. Check node status. If all nodes show a status of online, mark the error you have just repaired fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_DISK_FULL ) Node hard disk full [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. Delete files from the /dumps directory. 3. Run a configuration dump and a logged data dump. Save the dump data. 4. Ask your customer support representative for assistance. 5. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_FAIL ) Logical Fibre Channel port reported failed [chars].Explanation No active and functioning logical Fibre Channel port was detected by the software.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_QUANTITY ) Logical Fibre Channel port missing [chars].Explanation No active and functioning Fibre Channel port was detected by the software.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_PORT_QUANTITY ) Logical Fibre Channel port reported not operational [chars].Explanation No active and functioning logical Fibre Channel port was detected by the software.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(2a).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_NODE_WARMSTART ) Node warmstarted due to 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. Ask your customer support representative for assistance. 4. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_POWER_DOMAIN ) Power domain error [chars].Explanation The two nodes in an I/O group are on the same Caching Services Module.
Recommended Action Determine what the configuration should be. Remove one of the nodes and add a node to the I/O group that is not on the same Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MDISK_GROUP_OFFLINE ) A Managed Disk group is offline [chars].Explanation A managed disk group is offline.
Recommended Action 1. Repair the enclosure or disk controller. 2. Start a cluster discovery operation. 3. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
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. Add the managed disk into the cluster. 3. Check the managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
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. Ask your customer support representative for assistance. 4. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
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.
Introduced Cisco MDS SAN-OS Release 1.3(1).
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.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_DEVICE_RESOURCE_RAN_OUT ) Too many controllers were presented to the cluster [chars].Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.
Recommended Action 1. Remove unwanted devices from the Fibre Channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERP ) Error Recovery Procedure occurred [chars].Explanation A managed disk error recovery procedure (ERP) has occurred. This error has been reported because a large number of disk error recovery procedures have been performed by the disk controller. The problem is probably caused by a failure of some other component on the SAN.
Recommended Action 1. View the error log entry and determine the managed disk that was being accessed when the problem was detected. 2. Perform the disk controller problem determination and repair procedures for the managed disk determined in Step 1. 3. Perform Fibre Channel switch problem determination and repair procedures for the Fibre Channel switches containing the node, and connected to the disk controller that is managing the managed disk, and any Fibre Channel switches in the Fibre Channel path between those switches. 4. Mark resolved errors from Steps 2 and 3 as fixed. 5. Take an error log dump if no switch or disk controller failures were resolved in Steps 2 and 3. Call your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERROR ) Managed Disk I/O error [chars].Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.
Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, include the managed disks and then mark the error as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD ) Managed Disk error count threshold exceeded [chars].Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.
Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, include the managed disks and then mark the error as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_TIMEOUT_OVERALL ) Timeout due to excessive processing time [chars].Explanation A managed disk has timed out. This error has been reported because a large number of disk timeout conditions have been detected. The problem is probably caused by a failure of some other component on the SAN.
Recommended Action 1. Repair problems on all disk controllers and switches on the same SAN as this cluster. 2. If problems are found, mark this error as fixed. 3. If no switch or disk controller failures can be found, take an error log dump and call your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LOCAL_PORT_EXCLUDED ) Local FC port excluded [chars].Explanation A local Fibre Channel port has been excluded.
Recommended Action 1. Repair the Fibre Channel network fabric. 2. Check the status of the disk controller. If all disk controllers show good status, mark the error you have just repaired fixed. 3. If the error persists and no other cause can be determined, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LOGIN_EXCLUDED ) Login excluded [chars].Explanation Login has been excluded.
Recommended Action 1. In the sequence shown, exchange the field-replaceable units (FRUs) for new FRUs: Fibre Channel cable, switch to remote port. 2. Start a cluster discovery operation to recover the login. 3. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LUN_RESOURCE_RAN_OUT ) Too many LUNs were presented to a node [chars].Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.
Recommended Action 1. Remove unwanted devices from the Fibre Channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check that the configuration is as expected. Mark the error you have just repaired fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_ACCESS_INVALID ) Access beyond end of disk, or Managed Disk missing [chars].Explanation The error that is logged in the cluster error log indicates a software problem in the cluster, or in a disk enclosure or disk controller that is connected to the node.
Recommended Action 1. Ensure that the software is at the latest level on the cluster and on the disk controllers. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask your customer support representative for assistance. 4. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_DEVICE_PORT_EXCLUDED ) Remote Port excluded for a specific Managed Disk and Node [chars].Explanation A remote Fibre Channel port has been excluded.
Recommended Action 1. View the error log. Note the managed disk ID associated with the error code. 2. Using the managed disk ID, determine the failing disk controller. 3. Refer to the service documentation for the disk enclosure or disk controller and the Fibre Channel network fabric to resolve the reported problem. 4. Start a cluster discovery operation to recover the excluded Fibre Channel port. 5. Include the managed disk that you noted in Step 1. 6. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 7. If all disk controllers do not show a good status, contact the customer support representative to resolve the problem with the disk controller.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec]Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.
Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If all managed disks show a status of excluded, include the managed disks and then mark the error as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_INITIALISE_INVALID ) Invalid blocksize, capacity or LUN identity has changed during Managed Disk initialization [chars].Explanation Access beyond end of disk. The initialization of the managed disk has failed.
Recommended Action 1. Check the status of the managed disk and of the managed-disk group. 2. Include the managed disk into the cluster. 3. Check the managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed. 4. If not all managed disks show a status of online, check the status of the disk controller.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_RESOURCE_RAN_OUT ) Too many Managed Disks were presented to the cluster [chars].Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.
Recommended Action 1. Remove unwanted devices from the Fibre Channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check that the configuration is as expected. Mark the error you have just repaired fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_CREATION_FAILURE ) A suitable Managed Disk for use as a Quorum Disk was not found [chars].Explanation No managed disk is suitable for use as a quorum disk. When a cluster is created, three disks are automatically selected as quorum disks. A quorum disk is needed to enable a tie-break when some cluster members are missing. To become a quorum disk: The managed disk must be accessible by all nodes in the cluster and the managed disk must have free extents. This error code is produced when at least one quorum disk is not accessible by all nodes in the cluster. A quorum disk might not be available because of a Fibre Channel network failure or because of a Fibre Channel switch zoning problem.
Recommended Action 1. Resolve any known Fibre Channel network problems. 2. Confirm that managed disks have been created and that those managed disks have free extents. 3. List the manage disks. If at least one managed disk shows a mode of managed, mark the error you have just repaired as fixed. 4. If you are unable to make the appropriate changes, ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_NOT_AVAILABLE ) Quorum Disk not available [chars].Explanation One or more quorum disks were not discovered by the node.
Recommended Action 1. Resolve any known Fibre Channel network problems. 2. Check managed disk status.If any managed disks are offline or excluded perform the disk controller problem determination and repair procedures for the managed disks. 3. Start a cluster discovery operation. 4. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ALL_SSH_KEYS_REMOVED ) Attempt to delete SSH keys (no effect) [chars].Explanation The svctask rmallsshkeys command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEPARTNERSHIP ) Remote Copy partnership created [chars].Explanation The svctask mkpartnership or equivalent GUI or Cisco CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEPARTNERSHIP ) Remote Copy partnership deleted [chars].Explanation The svctask rmpartnership or equivalent GUI or CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYPARTNERSHIP ) Remote Copy partnership modified [chars].Explanation The svctask chpartnership or equivalent GUI or CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_ADDED ) Attempt to add SSH key (no effect) [chars].Explanation The svctask addsshkey command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_REMOVED ) Attempt to delete SSH key (no effect) [chars].Explanation The svctask rmsshkey command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_CR_START ) Cluster recovery required [chars].Explanation The node has detected that cluster recovery is required and is waiting for human intervention to continue.
Recommended Action Contact your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_CORRUPT ) Node data corrupted - node rejected from cluster [chars].Explanation Node data is readable but corrupted. The node has been rejected from the cluster.
Recommended Action 1. Reinstall the code on the node. The node will have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. If the error continues, ask your customer service representative for assistance. It may be necessary to replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_UNREADABLE ) Node data unreadable - node rejected from cluster [chars].Explanation Node data could not be read. The node has been rejected from the cluster.
Recommended Action 1. Reinstall the code on the node. The node will have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. If the error continues, ask your customer support representative for assistance. It may be necessary to replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_HDW_CONFIG ) Processor not valid [chars].Explanation The node has detected unexpected differences in the processor vital data.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MEM_SIZE ) Memory size error [chars].Explanation The detected memory size does not match the expected memory size for the cluster.
Recommended Action A memory module on the Caching Services Module is probably faulty. Reload the node. If the error persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MISSING_RES ) Unable to form a cluster due to lack of cluster resources [chars].Explanation The node is unable to locate sufficient other nodes in the cluster or the quorum disk controller needed in order to form a cluster.
Recommended Action Check the status of the quorum disk controller and the other nodes in the cluster. If the quorum disk has failed, perform the problem determination procedures for the disk controller. Otherwise perform problem determination on the missing nodes and network.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_NO_FABRIC ) The node is unable to see the FC fabric [chars].Explanation No active or functioning logical Fibre Channel port was detected by the software.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_PWR_DMN_ERR ) Power domain error [chars].Explanation The two nodes in an I/O group are on the same Caching Services Module.
Recommended Action Determine if both nodes on the Caching Services Module are in fact in the same I/O group. If so, determine what the configuration should be. Remove one of the nodes and add a node to the I/O group which is not on the same Caching Services Module. If both nodes are not in the same I/O group, ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_REPEATED_ASSERTS ) Node repeatedly crashing due to a software fault [chars].Explanation The number of software faults has exceeded the maximum allowed for the time period.
Recommended Action 1. Delete the node from the cluster. 2. Add the node back into the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 4. If the error continues, ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_RESET_AND_REJECT ) Node data not found - node rejected from cluster [chars].Explanation Node data was not found. The node has been rejected from the cluster.
Recommended Action Examine error logs to determine if another recorded error caused the loss of the node data and, if so, follow the actions for that error. If no other error was recorded, the node may have lost power without saving data or been reset. Attempt to determine the cause of the power loss or reset. If no cause can be determined, then follow these steps: 1. Reinstall the code on the node. The node will have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. If the error continues, ask your customer support representative for assistance. It may be necessary to replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-NODE_ERR_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-SVC_SYSLOG_IF_INTERNAL_ERROR: Interface [chars] internal error: [chars].Explanation SAN Volume Controller (SVC) interface internal error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-SVC_SYSLOG_LC_INTERNAL_ERROR: Unable to send MTS to linecard in slot [dec]: [chars].Explanation Line card messaging and transaction service (MTS) failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-3-SVC_SYSLOG_NPORT_INTERNAL_ERROR: [chars] N-port for Interface [chars], VSAN [dec] internal error: [chars].Explanation N port internal error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-4
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_FIRST_DATA_PINNED ) Customer data pinned [chars].Explanation There is pinned customer data. This warning is given when data is pinned and there were not already pinned data. Error log entries will exist for the underlying cause of the pinned data.
Recommended Action Perform problem determination on the error log to determine the cause of the pinned data and correct.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_SYNCHRONOUS ) Cache in write through mode due to pinned data [chars].Explanation The cache must operate in write through mode because of the amount of pinned data.
Recommended Action Perform problem determination on the error log to determine the cause of the pinned data and correct.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_BELOW_CAPACITY ) Battery is below threshold capacity [chars].Explanation Battery capacity is below threshold. The node will remain offline until the battery charge is sufficient to come up.
Recommended Action Wait for the battery to recharge. This may take many hours. If after several hours have passed and the node has not yet come up, follow these steps: 1. Reload the node. 2. If the error persists, reinstall the code on the line card. The node(s) will then have to be removed and added back to the cluster. 3. If the error persists, replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_CANNOT_OPEN_IO_PROCESS_Q ) Internal error - IO process queue [chars].Explanation The process was unable to open the needed message queue. The node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 1 with the latest level of code. 3. If the error continues, ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DEACTIVATE_CLUSTER_IP_FAILED ) Deactivate cluster IP failed [chars].Explanation Unable to deactivate the cluster IP for the config node. The cluster IP should be deactivated by other checks. If that is not the case, it may not be possible to execute configuration commands.
Recommended Action If there is a problem executing configuration commands, follow these steps: 1. Shut down the interfaces of the node. This will force the node out of the cluster and should cause the switch to deactivate the IP address associated with the node. This should restore the ability to execute configuration commands. 2. If the error persists, reinstall the code on the node. The node will then have to be removed and added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat Step 2 with the latest level of code. 4. Ask your customer support representative for assistance if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DUMP_METADATA_FAILED ) Node assert dump failed [chars].Explanation A failure occurred writing out a node assert dump. Other log entries may accompany this error.
Recommended Action An initial error will have caused the node assert dump. Examine the log for that error and follow the recommended actions for that error. In addition, examine the log for errors related to the internal disk drive. If errors are found, follow the recommended actions. If no entries explain the failure to write the dump, then perform the following steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues. It may be necessary to replace the Caching Services Module.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_EXECVE_FAILED ) Internal error - program launch [chars].Explanation The process cannot launch the I/O program. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_FORK_FAILED ) Internal error - fork failed [chars].Explanation The process cannot launch the I/O program. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_EXIT_LOGIC_ERR ) Internal error - bad exit code [chars].Explanation Node was warmstarted because of an internal logic error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_UNKNOWN_EXEC_MODE ) Internal error - run mode [chars].Explanation Node was rebooted because of an internal logic error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_EXITED_DUE_TO_SIGNAL ) Internal error - signal caused exit [chars].Explanation The I/O process exited because of a signal that was not caught. Node was warm started because of this error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster.2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_STOPPED_DUE_TO_SIGNAL ) Internal error - signal caused stop [chars].Explanation The I/O process stopped because of a signal received. Node was warm started because of this error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster.2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_TERMINATED_ABNORMALLY ) Internal error - abnormal exit [chars].Explanation The I/O process exited abnormally. Node was warm started because of this error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_OPEN_MSG_QUEUE_FAILED ) Internal error - message queue [chars].Explanation The process cannot open the needed message queue. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_PTHREAD_CREATE_FAILED ) Internal error - threads [chars].Explanation The process cannot create the needed threads. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_UNKNOWN_MESSAGE_TYPE ) Internal error - message type [chars].Explanation Node was rebooted because of an internal logic error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_WAITPID_FAILED ) Internal error - waitpid failed [chars].Explanation The process cannot launch the I/O program properly. Node was warm started because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec]Explanation The process cannot warm start the memory device. Node was rebooted because of this error.
Recommended Action If this error is repeated continuously, follow these steps: 1. Reinstall the code on the node. The node will then have to be removed and added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. Ask your customer support representative for assistance, if the error continues.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_MAPPING_STOPPED ) FlashCopy has been stopped [chars].Explanation A flash copy mapping task stopped because of an error. A stopped flash copy may affect the status of other vdisks in the same I/O group. Preparing the stopped flash copies as soon as possible is advised.
Recommended Action 1. Correct higher priority errors and then start the flash copy task again. 2. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_FAILED ) FlashCopy prepare failed due to cache flush failure [chars].Explanation A flash copy prepare task failed because a cache flush has failed.
Recommended Action 1. Correct higher priority errors, and then retry the prepare tasks. 2. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_STOP_COMPLETED ) Flash Copy Stopped [chars].Explanation The flash copy mapping or consistency group has entered the stopped state as a result of a user request to stop.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_DIRECTORY_LIST_FAILED ) Failed to obtain directory listing from remote node [chars].Explanation An attempt to clean or retrieve files from the dumps directory has failed because of a failure to get a listing of the directory from the remote node.
Recommended Action Determine if the remote node is still online. If not, determine the problem on the remote node. If it is online, retry the command. Contact your customer support representative for assistance if it still fails. Cisco CLI commands or Fabric Manager procedures may be used to access the node directly as an alternative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_FEATURISATION_VIOLATION ) Featurisation violation [chars].Explanation The user has allocated more virtualized storage than licensed for or established a flash copy mapping or remote copy relationship when these have not been licensed.
Recommended Action Look in the featurisation log for log "error" entries to determine the type of violation. Then you can either reduce virtualized storage, or remove the flash copy mapping or remote copy relationship. This will put you in compliance with your license. You can also update the license information if that is incorrect or arrange with your customer support representative to purchase a license for the desired features.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_TRANSFER_FILE_FAILED ) Failed to transfer file from remote node [chars].Explanation An attempt to retrieve a file from the dumps directory has failed.
Recommended Action Determine if the remote node is still online. If not, determine the problem on the remote node. If it is online, retry the CLI command or use a similar Fabric Manager procedure. Contact your customer service representative for assistance if it still fails. Cisco CLI commands may be used to access the node directly as an alternative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_NONE_OK ) Both nodes in the IO group are not available [chars].Explanation After the user removes the node, there were no nodes left in the I/O group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_NODE_PENDED ) Software upgrade process failed [chars].Explanation A software upgrade has failed. The cause might be hardware error or it might be because of a failure in the new version of the software. An automatic software downgrade is performed to restore the nodes to their previous software version.This is indicated in the log by a "software downgrade complete" entry. If the downgrade operation fails to downgrade a node, for example because it is offline, the download operation stops and waits for the offline SAN Volume Controller to be repaired or deleted from the cluster. While the downgrade operation is in progress, configuration commands sent to the cluster fail with a message indicating that a software upgrade operation is still in progress. The downgrade operation might take up to three hours.
Recommended Action 1. Display the status of the nodes on the cluster. 2. Delete any offline node from the cluster if any node is offline. If the deletion fails with a message indicating that a software upgrade is in progress, this means that the downgrade process is still active. Wait for this operation to either complete or stop on the offline node and then retry the delete. If the downgrade operation had stopped, it now continues. 3. Solve all logged hardware problems. 4. Ask the user to retry the software installation. 5. If the installation fails again, report the problem to your customer support representative. 6. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_PCK_DELIVERY_FAILED ) Software install package cannot be delivered to all nodes [chars].Explanation An error occurred while sending the software package to the nodes.
Recommended Action 1. Display the status of the nodes on the cluster. 2. If any node is offline, perform problem determination on the node and bring the node back online. Or, alternatively, delete the offline node from the cluster. 3. Retry the software upgrade command. 4. If the installation fails again, report the problem to your customer support representative.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_PLIC_LINK ) Connection to a configured remote cluster has been lost [chars].Explanation This cluster can no longer communicate with the remote copy partner cluster.
Recommended Action Perform problem determination on the network and the other cluster.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_LSYNC ) Remote Copy suffered loss of synchronization [chars].Explanation In a remote-copy operation, the relationship has stopped and lost synchronization, for a reason other than a continuous I/O error.
Recommended Action 1. Correct higher priority errors, and then restart the remote copy. 2. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_PERS ) Remote Copy suffered persistent error [chars].Explanation A remote copy relationship has been stopped because of a continuous I/O error.
Recommended Action 1. Correct the higher priority errors, and then retry the remote copy task. 2. Mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_TIMEOUT ) Remote Copy retry timeout [chars].Explanation Remote copy cannot find a path to the device in the remote cluster within the timeout period.
Recommended Action Perform problem determination on the node.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_COPIED_MEDIUM_ERROR ) I/O media error copied [chars].Explanation During a copy or a migrate process, a media error was copied to the destination disk.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_INSUFFICIENT_VIRTUAL_EXTENTS ) Insufficient extents to create Virtual Disk [chars].Explanation There are not enough extents contained within the managed disk group to create the required virtual disk. This error can be logged if a migration is started and then a virtual disk is created that uses the extents that were to be used for the migration.
Recommended Action Add additional managed disks to the managed disk group or reduce the size of virtual disk to be created.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_STOPPED ) Migration stopped [chars].Explanation The specific migration has been stopped because of errors occurring during migration. These errors have been logged.
Recommended Action Analyze the error log. Perform problem determination and correct any errors which have occurred. Migrate any specific extents which were not migrated because of the errors.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_SUSPENDED ) Migration suspended [chars].Explanation Migration suspended.
Recommended Action 1. Verify that all error codes of a higher priority have already been fixed. 2. Ensure that all managed disk groups that are the destination of suspended migrate operations have free extents available. 3. Mark this error as fixed. This will cause the migrate operation to restart. If the restart fails, a new error will be logged.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_MEDIUM_ERROR ) A media error has occurred during I/O to a Managed Disk [chars].Explanation A disk I/O medium error has occurred.
Recommended Action 1. Rewrite the bad data to the LBA block reported in the host systems SCSI sense data. Note: If this error has occurred during a migration, the host system does not notice the error until the target device is accessed. 2. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_MEDIUM_ERROR ) A media error has occurred during I/O to a Managed Disk [chars].Explanation A disk I/O medium error has occurred.
Recommended Action 1. Ask the customer to rewrite the bad data to the LBA block reported in the host systems SCSI sense data. Note: If this error has occurred during a migration, the host system does not notice the error until the target device is accessed. 2. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD_WARNING ) Managed Disk error count warning threshold met [chars].Explanation I/O to the managed disk has experienced sufficient errors to generate this warning. If the managed disk continues to experience I/O errors, the managed disk may be excluded.
Recommended Action Perform problem determination on the affected managed disk.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LUN_DISCOVERY_FAILED ) Discovery of LUN failed [chars].Explanation The cluster has a connection to the device on the SAN through this node, but the device has not responded to the node in a manner consistent with a functional device LUN.
Recommended Action If there are device LUNs that should have been discovered by the node, follow these steps: 1. Perform a manual discovery. 2. Perform problem determination on the device.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_PORT_PREFERENCE_IGNORED ) Preferred port is not being used for Managed Disk access [chars].Explanation The preferred port designated by the back end controller is not being used for managed disk access. A port error or excluded port has prevented the use of the preferred port.
Recommended Action Perform problem determination on the controller and network to determine the cause of the port error or exclusion.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_NODERR_CR_FAILED ) Cluster recovery failed [chars].Explanation Cluster recovery has failed, and a software dump has been created.
Recommended Action Contact your customer support representative for assistance.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-NODE_WARNING_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-SVC_SYSLOG_IF_INTERNAL_WARN: Interface [chars] internal warning: [chars].Explanation SAN Volume Controller (SVC) interface internal warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-4-SVC_SYSLOG_NPORT_INTERNAL_WARN: [chars] N-port for Interface [chars], VSAN [dec] internal warning: [chars].Explanation SAN Volume Controller (SVC) interface internal warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-5
Error Message SVC-5-NODE_NOTICE_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-5-SVC_SYSLOG_IF_CONFIG_DELETED: Interface [chars] configuration was deleted[chars].Explanation SAN Volume Controller (SVC) interface configuration was deleted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-5-SVC_SYSLOG_IF_DOWN: Interface [chars] is down.Explanation SAN Volume Controller (SVC) interface is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-5-SVC_SYSLOG_IF_UP: Interface [chars] is up.Explanation SAN Volume Controller (SVC) interface is up.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-6
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_ALL_DATA_UNPINNED ) All data now unpinned [chars].Explanation All the customer data in the I/O group is now unpinned.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_ASYNCHRONOUS ) Pinned data reduced; cache can operate normally [chars].Explanation Enough customer data has been unpinned that the cache is no longer required to operate in write through mode because of the pinned data. Note that the cache may still operate in write through mode for other reasons.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_OK ) Battery recharged [chars].Explanation Battery capacity has been restored to above the threshold value. The node will now come online.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_POWER_DOWN ) Poweroff or power failure detected [chars].Explanation The process has received a poweroff or power failure indication. The node is shutting down.
Recommended Action Restore power. If power was not removed and this occurs, follow these steps: 1. Reload the node. 2. Reinstall the code on the line card, if the error persists. The node(s) then has to be removed and added back to the cluster. 3. Replace the Caching Services Module, if the error persists.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_PWR_BUTTON ) Power withdrawn [chars].Explanation Node software was notified that AC power was being shut off, or the Caching Services Module was being reset.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_COPY_COMPLETED ) Flash Copy Copied [chars].Explanation The flash copy mapping or consistency group has entered the "idle_copied" state.The target disk now contains a complete copy and is no longer dependent on the source.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_COMPLETED ) Flash Copy Prepared [chars].Explanation The flash copy mapping or consistency group has entered the prepared state. It is now possible to start or stop the mapping or group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_CLUSTER_RECOVERY_COMPLETE ) Cluster recovery completed [chars].Explanation Cluster recovery has completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_ONE_OK ) One node in the IO group is not available [chars].Explanation Following node remove by the user, there is only one node left in the IO group.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_SECURE_DELETE_COMPLETE ) Virtual Disk format completed [chars].Explanation The formatting (writing all zeros) to new extents of the virtual disk has completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_COLDSTART ) Node software started [chars].Explanation The node software has been started (cold start).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_COPY_COMP ) Remote Copy complete [chars].Explanation Background copy complete. The standalone relationship or consistency group has transitioned from inconsistent copying to consistent synchronized. This will only be logged on the cluster of the primary virtual disk(s).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_READY_TO_START ) Remote Copy ready to start [chars].Explanation The remote copy relationship or consistency group, which had previously been stopped because of an error, is ready to be restarted. All resources are now online.
Recommended Action Restart the relationship or consistency group.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VG_EV_MIGRATE_COMPLETE ) Migration complete [chars].Explanation Migration has completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_CLUSTER_FABRIC_VIEW_CHANGE ) Cluster fabric view has been updated. [chars].Explanation The node is in the process of discovering devices on the fabric.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_MAPPING ) Virtual Disk to Host SCSI mapping created [chars].Explanation The svctask mkvdiskhostmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_WWPN ) Port added to a Host [chars].Explanation The svctask addhostport IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_CLUSTER_TIME ) Attempt to change cluster time (no effect) [chars].Explanation The svctask setclustertime IBM command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_TIMEZONE ) Attempt to change time zone (no effect) [chars].Explanation The svctask settimezone IBM command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DISCOVERY ) Manual Managed Disk discovery invoked [chars].Explanation The svctask detectmdisk IBM command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DUMP_CONFIG ) Cluster config dumped to file [chars].Explanation The svctask dumpconfig IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_MODIFY ) Cluster attributes modified [chars].Explanation The svctask chcluster IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_SHUTDOWN ) Node or Cluster shutdown [chars].Explanation The svctask stopcluster IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_FC_MAPPING ) Flash Copy mapping created [chars].Explanation The svctask mkfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_HOST ) Host created [chars].Explanation The svctask mkhost IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_FC_MAPPING ) Flash Copy mapping deleted [chars].Explanation The svctask rmfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_HOST ) Hosts deleted [chars].Explanation The svctask rmhost IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_MAPPING ) Virtual Disk to Host SCSI mapping deleted [chars].Explanation The svctask rmvdiskhostmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_PORT_HOST_LIST ) Ports deleted from a Host [chars].Explanation The svctask rmhostport IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_WWPN ) Port deleted from a Host [chars].Explanation The svctask rmhostport IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DEVICE_SET_NAME ) Controller attributes modified [chars].Explanation The svctask chcontroller IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_ANALYSE ) Error log analyzed [chars].Explanation The svctask finderr IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_CLEARLOG ) Error log cleared [chars].Explanation The svctask clearerrlog IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_DUMPLOG ) Error log dumped [chars].Explanation The svctask dumperrlog IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_FIX ) Error log entry marked fixed [chars].Explanation The svctask cherrstate IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CONSIST_GRP_SET_NAME ) Flash Copy consistency group name modified [chars].Explanation The svctask chfcconsistgrp -name IBM command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CREATE_CONSIST_GRP ) Flash Copy consistency group created [chars].Explanation The svctask mkfcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_DELETE_CONSIST_GRP ) Flash Copy consistency group deleted [chars].Explanation The svctask rmconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_SET_NAME ) Flash Copy mapping name modified [chars].Explanation The svctask chfcmap -name IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FEATURISATION_CHANGED ) Licensed settings modified [chars].Explanation The svctask chlicense IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_PREPARE_CG ) Flash Copy consistency group prepared [chars].Explanation The svctask prestartfcconsistgrp IBM o CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_START_CG ) Flash Copy consistency group started [chars].Explanation The svctask startfcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_STOP_CG ) Flash Copy consistency group stopped [chars].Explanation The svctask stopfcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_DELETE ) Host deleted [chars].Explanation The svctask rmhost IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_SET_NAME ) Host attributes modified [chars].Explanation The svctask chhost IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HWS_SET_NAME ) IO Group name modified [chars].Explanation The svctask chiogrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_IO_TRACE_FINISHED ) IO Tracing stopped [chars].Explanation The svctask stoptrace IBM CLI command has been invoked.
Recommended Action Analyze the traces.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_ADD_MDISK ) Managed Disk added to Managed Disk group [chars].Explanation The svctask addmdisk IBM command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_CREATE ) Managed Disk Group created [chars].Explanation The svctask mkmdiskgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(3c).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE ) Managed Disk Group deleted [chars].Explanation The svctask rmmdiskgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE_MDISK ) Managed Disk deleted from Managed Disk group [chars].Explanation The svctask rmmdisk IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_SET_NAME ) Managed Disk Group attributes modified [chars].Explanation The svctask chmdiskgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_SET_NAME ) Managed Disk attributes modified [chars].Explanation The svctask chmdisk IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_UNSLANDER ) Managed Disk online [chars].Explanation The managed disk that was excluded is now online.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MIGRATE ) Virtual Disk migration to new Managed Disk group started [chars].Explanation The svctask migratevdisk IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MODIFY_FC_MAPPING ) Flash Copy mapping modified [chars].Explanation The svctask chfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_ADD ) Node added [chars].Explanation The svctask addnode IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_CREATE_CLUSTER ) Cluster created [chars].Explanation The cluster add IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_DELETE ) Node deleted from cluster [chars].Explanation The svctask rmnode IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_PEND ) Node Pend [chars].Explanation The node has gone into the pending state. It will shortly go into the online or offline state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_REMOVE ) Node leaving cluster (expected) [chars].Explanation The node has gone offline as expected because of a shutdown, upgrade or deletion.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SET_NAME ) Node attributes modified [chars].Explanation The svctask chnode IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SHUTDOWN ) Node shutdown [chars].Explanation The svctask stopcluster -node IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_UNPEND ) Node Unpend [chars].Explanation The node has gone online.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PLANAR_SN_CHANGE ) Attempt to change the Planar Serial Number (no effect) [chars].Explanation The svctask writesernum IBM CLI command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS 9000, but is retained for compatibility.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PRETRIGGER_FC_MAPPING ) Flash Copy mapping prepared [chars].Explanation The svctask prestartfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_QUORUM_CREATE ) Quorum disk set [chars].Explanation The svctask setquorum IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATECONSTGRP ) Remote Copy consistency group created [chars].Explanation The svctask mkrcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEREL ) Remote Copy relationship created [chars].Explanation The svctask mkrcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETECONSTGRP ) Remote Copy consistency group deleted [chars].Explanation The svctask rmconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEREL ) Remote Copy relationship deleted [chars].Explanation The svctask rmrcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYCONSTGRP ) Remote Copy consistency group modified [chars].Explanation The svctask chrcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYREL ) Remote Copy relationship modified [chars].Explanation The svctask chrcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START ) Remote Copy relationship started [chars].Explanation The svctask startrcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START_CG ) Remote Copy consistency group started [chars].Explanation The svctask startrcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP ) Remote Copy relationship stopped [chars].Explanation The svctask stoprcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP_CG ) Remote Copy consistency group stopped [chars].Explanation The svctask stoprcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH ) Remote Copy relationship switched [chars].Explanation The svctask switchrcrelationship IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH_CG ) Remote Copy consistency group switched [chars].Explanation The svctask switchrcconsistgrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SERVICE_APPLY_SOFTWARE ) Software upgrade command accepted [chars].Explanation The cluster upgrade svc-system IBM CLI command has been invoked. The command has been accepted. Additional log entries will track the progress of the upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_STOP_FC_MAPPING ) Flash Copy mapping stopped [chars].Explanation The svctask stopfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_TRIGGER_FC_MAPPING ) Flash Copy mapping started [chars].Explanation The svctask startfcmap IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_BACKED_OFF ) Software downgrade complete [chars].Explanation The software upgrade process failed, and all nodes have been restored to the previous level of code.
Recommended Action Perform problem determination on the cause of the upgrade failure and take corrective action before retrying the upgrade.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_COMPLETED ) Software upgrade complete [chars].Explanation All nodes have successfully moved to the new code level, which will now be committed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_STARTED ) Software upgrade started [chars].Explanation The software upgrade process has started (the first node is about to be upgraded).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_CREATE ) Virtual Disk created [chars].Explanation The svctask mkvdisk IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_DELETE ) Virtual Disk deleted [chars].Explanation The svctask rmvdisk IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND ) Virtual Disk expanded [chars].Explanation The svctask expandvdisksizeIBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND_SINGLE_EXT ) Virtual Disk expanded by single extent [chars].Explanation The svctask addvdiskext IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENT ) Extent migration started [chars].Explanation The svctask migrateexts IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENTS ) Extent migration started [chars].Explanation The svctask migrateexts IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MODIFY_GOVERN ) Virtual Disk throttling rate modified [chars].Explanation The svctask chvdisk -rate IBM o CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MOVE_HWS ) Virtual Disk IO Group changed [chars].Explanation The svctask chvdisk -iogrp IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SET_NAME ) Virtual Disk name modified [chars].Explanation The svctask chvdisk -name IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SHRINK ) Virtual Disk shrunk [chars].Explanation The svctask shrinkvdisksize IBM CLI command has been invoked.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-NODE_INFO_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-SVC_SYSLOG_CL_CONFIG: Node [chars] has become config node of cluster [chars].Explanation SAN Volume Controller (SVC) interface has become cluster configuration node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-SVC_SYSLOG_CL_JOIN: Node [chars] has joined cluster [chars].Explanation SAN Volume Controller (SVC) interface has joined cluster.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-SVC_SYSLOG_CL_UNJOIN: Node [chars] has left cluster [chars].Explanation SAN Volume Controller (SVC) interface has left cluster.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-SVC_SYSLOG_LC_WWN_PURGE: All WWNs for module [dec] have been purged[chars].Explanation SAN Volume Controller (SVC) line card has purged all WWNs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC-6-SVC_SYSLOG_VSAN_INACTIVE: VSAN [dec] suspended.Explanation VSAN was suspended. This can cause other warnings.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC-7
Error Message SVC-7-NODE_DEBUG_MSG: [chars].Explanation Syslog message from a SAN Volume Controller (SVC) interface node.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC_BATTERY Messages
This section contains the SAN Volume Controller battery (SVC_BATTERY) messages.
SVC_BATTERY-SLOT#-2
Error Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_OPERATIONAL: Battery [dec] temperature [dec] C is outside the operational range (-10C to 65C).Explanation The battery temperature is outside the operational range (-10 to 650C).
Recommended Action Enter the show environment fan CLI command or use an equivalent Fabric Manager/Device Manager procedure to determine fan operation and take action to cool down the switch.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_PRESENT: Battery [dec] is not present.Explanation The module does not have a sufficient number of batteries. Two batteries are needed.
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 SVC_BATTERY-SLOT#-2-CHARGING_DISABLED: Temperature outside permitted range for battery charging (5C-40C).Explanation The temperature of the module is not within the range to permit battery charging.
Recommended Action Make sure the temperature of the module is between 5 and 400C.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SVC_BATTERY-SLOT#-2-CHARGING_FAILURE: Charging failure in battery [dec] ([hex]).Explanation The module encountered failures while charging a battery.
Recommended Action Replace the battery.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC_BATTERY-SLOT#-2-CLOCK_INCORRECT: System clock is running behind, battery conditioning will be affected.Explanation The system clock is running behind the actual time. This will affect the battery conditioning.
Recommended Action Enter the clock set CLI command or use an equivalent Fabric Manager/Device Manager procedure to set the correct time.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SVC_BATTERY-SLOT#-2-COMMUNICATION_FAILURE: Communication failure with battery [dec].Explanation The module encountered failures while communicating with a battery.
Recommended Action Replace the battery. 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 SVC_BATTERY-SLOT#-2-CONDITIONING_DISABLED: Temperature outside permitted range for battery conditioning (5C-40C).Explanation The temperature of the line card is not within the range to permit battery conditioning.
Recommended Action Make sure the temperature of the line card is between 5 and 400C.
Error Message SVC_BATTERY-SLOT#-2-DISCHARGING_FAILURE: Discharging failure in battery [dec] ([hex]).Explanation The module encountered failures while discharging a battery.
Recommended Action Replace the battery. 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(4a).
SVC_BATTERY-SLOT#-4
Error Message SVC_BATTERY-SLOT#-4-BATTERY_CAPACITY_LOW: Battery capacity is below the required threshold.Explanation The battery is lower than the required threshold.
Recommended Action Make sure the temperature is within the range to allow charging.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SVC_BATTERY-SLOT#-6
Error Message SVC_BATTERY-SLOT#-6-BATTERY_CAPACITY_OK: Battery capacity is above the required threshold.Explanation The battery is above the required threshold.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_CANCELLED: Temperature outside permitted range for battery conditioning (5C-40C). Battery [dec] conditioning cancelled.Explanation The temperature of the module is not within the range to permit battery conditioning.
Recommended Action Make sure the temperature of the line card is between 5 and 400C.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_COMPLETED: Conditioning of battery [dec] completed successfully.Explanation Conditioning process started for a battery is completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_RESUMED: Conditioning of battery [dec] resumed.Explanation Conditioning process for a battery is resumed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_STARTED: Conditioning of battery [dec] started.Explanation Conditioning process started for a battery.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SYSMGR Messages
This section contains the system manager (SYSMGR) messages.
SYSMGR-2
Error Message SYSMGR-2-BOOTSCOPE_HANDSHAKE: Service [chars] is in the boot scope, but tried a regular handshake. Discarding request.Explanation A service is trying to take actions that belong to a different class of services.
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.2(2a).
Error Message SYSMGR-2-CFGERASE_ABORTED: Write erase aborted.Explanation Write erase has failed.
Recommended Action Use the other system messages to verify that the problem has been corrected, and try again.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED: Configuration snapshot aborted.Explanation An attempt to save a snapshot of the startup configuration has failed.
Recommended Action Use the other syslog messages to verify that the problem has been corrected, and then try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED_DIR: Unable to open the configuration directory. Aborting configuration snapshot.Explanation The destination location for the snapshot configuration could not be found.
Recommended Action If the problem persists, use the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration snapshot.Explanation An attempt to copy the startup configuration to the snapshot configuration has failed because the old data could not be removed.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CFGSYNC_FAILURE: Syncing of the configuration to the standby failed.Explanation A synchronization of the configuration to the standby has failed.
Recommended Action Use the other system messages to verify that the problem has been corrected, and try again.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.Explanation A configuration copy has failed.
Recommended Action Use the other syslog messages to verify that the problem has been corrected, and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CFGWRITE_ABORTED_DIR: Unable to open the configuration directory. Aborting configuration copy.Explanation The destination location for the startup configuration could not be found.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CFGWRITE_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration copy.Explanation An attempt to copy the running configuration to startup configuration has failed because the old data could not be removed.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.3(1)
Error Message SYSMGR-2-CFGWRITE_ABORTED_LABEL: Unable to label the new configuration (error-id [hex]). Aborting configuration copy.Explanation An attempt to copy the running configuration to startup configuration has failed because the new startup configuration could not be stamped.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOCK: Unable to lock the configuration (error-id [hex]). Aborting configuration copy.Explanation An attempt to copy the running configuration to startup configuration has failed because the system could not lock the required configuration items.
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.2(2a).
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOG: Unable to open a log file for the new configuration: [chars] (error-id [hex]). Aborting configuration copy.Explanation An attempt to copy the running configuration to startup configuration has failed because a log file could not be created.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-2-CFGWRITE_TIMEOUT_ABORT: Configuration copy aborted by timeout.Explanation A service failed to store its configuration in the time-out period. The configuration save operation was terminated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SYSMGR-2-CFGWRITE_USER_ABORT: Configuration copy aborted by the user.Explanation The user typed CTRL+C while the configuration was being saved. The configuration save operation was terminated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CONVERT_FUNC_FAILED: Conversion function failed for service "[chars]" (error-id [hex]).Explanation The conversion function failed for this service.
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.2(2a).
Error Message SYSMGR-2-CONVERT_FUNC_NOTFOUND: Conversion function not found for service "[chars]".Explanation The system could not find an appropriate conversion function for this service.
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.2(2a).
Error Message SYSMGR-2-CONVERT_LIB_NOTFOUND: Conversion library not found for service "[chars]".Explanation The system could not find the conversion library for this service.
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.2(2a).
Error Message SYSMGR-2-CONVERT_STARTUP_ABORTED: Conversion of startup-config failed.Explanation The conversion of the startup configuration was terminated.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-CONVERT_ZIPPING_FAILED: Failed to zip the converted startup configuration.Explanation Conversion of the startup configuration failed when system was trying to zip the converted configuration.
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.2(2a).
Error Message SYSMGR-2-CREATE_DONEFILE_FAILED: Creating /var/run/sysmgr.initdone failed with return value: ([dec]).Explanation The initialization of the system could not complete.
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.2(2a).
Error Message SYSMGR-2-DELETE_BINARY_STARTUP_FAILED: Deletion of binary startup config failed during boot (error-id [hex]).Explanation T deletion of the binary startup configuration failed during boot.
Recommended Action If the problem persists, issue the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note: This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SYSMGR-2-FORMAT_FAILURE_SUP_RESET: Failure to format a partition successfully causing sup to reset.Explanation The partition used to store nonvolatile persistent storage service (PSS) files could not be formatted successfully. The supervisor will be reset.
Recommended Action If the problem persists, contact customer support. 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-GSYNC_ABORT: Global sync aborted by signal.Explanation The initial synchronization of the services was terminated. The synchronization will be attempted again later.
Recommended Action Enter the reload module CLI command or use an equivalent Fabric Manager/Device Manager procedure to reset the standby supervisor.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-GSYNC_GET_TIMEOUT: Request for global sync for UUID [hex] not completed in specified time.Explanation Service failed to complete global sync in specified time. The standby will no longer act as a high availability standby.
Recommended Action If the problem persists, contact customer support. 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-GSYNC_READY_SRVFAILED: Service "[chars]" on standby supervisor failed to restore its snapshot (error-id [hex]).Explanation The initial synchronization of service 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 1.3(1).
Error Message SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service "[chars]" on active supervisor failed to store its snapshot (error-id [hex]).Explanation The initial synchronization of service 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 1.2(2a).
Error Message SYSMGR-2-HASWITCHOVER_START: This supervisor is becoming active.Explanation A cold switchover has started.
Recommended Action When the other supervisor is back online, enter the show system reset-reason CLI command or use the equivalent Fabric Manager/Device Manager procedure to find out what caused the switchover.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-IMPROPER_CLEANUP: Service "[chars]" exited without replying to swover request.Explanation A conditional service exited without replying to a switchover request.
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).
Deprecated Cisco MDS SAN-OS Release 1.3(3c).
Error Message SYSMGR-2-INVALID_HANDSHAKE: Invalid secret ([dec]) received from service [chars]. Expected [dec].Explanation A service cannot be started.
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.2(2a).
Error Message SYSMGR-2-INVALID_SYSMGRCONF: [chars]: invalid configuration file "[chars]": [chars] (error-id [hex]).Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-INVALID_VERSIONMSG: The remote System Manager ([chars]) declares itself in the same state as this System Manager ([chars]).Explanation The redundancy state negotiation between the two supervisors 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 1.2(2a).
Error Message SYSMGR-2-ISSU_FAILED: The ISSU has failed: [chars] (error-id [hex]).Explanation The nondisruptive upgrade has failed.
Recommended Action The switch needs to be rebooted.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SYSMGR-2-MSG_SEND_FAILURE_STANDBY_RESET: Failure in sending message to standby causing standby to reset.Explanation Resetting the standby supervisor module because message transaction services (MTS) on the active supervisor module cannot send a message to the standby supervisor module.
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.0(1b).
Error Message SYSMGR-2-PARSEERR_DEPENDCYCLE: Dependency cycle found among [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUP_UGRPENTRY: [chars]: service [chars] duplicated in the current upgrade group. Previous use in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDCONFIG: [chars]: duplicated definition for service config. Previous definition in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDDEPEND: [chars]: duplicated dependency from [chars] for service [chars]. Previous use in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDNAME: [chars]: short name [chars] used by service [chars] is also used by service "[chars]" in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDOPTION: [chars]: duplicated definition for option [chars]-Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDSERVICE: [chars]: duplicated definition for service [chars]. Previous definition in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_DUPLICATEDVERDB: [chars]: duplicated definition for service version_db. Previous definition in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_GLOBAL_SYNC: [chars]: mts unaware service may not request for a global sync.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.0(1).
Error Message SYSMGR-2-PARSEERR_INVALIDCONDDEPEND: [chars] (in dependency list of ASAP service [chars]): conditional service "[chars]" not allowed.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALIDDEPEND: [chars] (in dependency list of service [chars]): service [chars] not defined for scope "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALIDEXEC: [chars]: invalid executable [chars] for service [chars]: [chars] ([dec]).Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a)
Error Message SYSMGR-2-PARSEERR_INVALIDHANDSHAKEDEPEND: [chars] (in handshake dependency list of service [chars]): service "[chars]" is MTS unaware or not defined for scope "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALIDIDENT: [chars]: [chars] "[chars]" not found for service "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a)
Error Message SYSMGR-2-PARSEERR_INVALIDOPTION: [chars]: option [chars]-][chars] cannot be set to "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_DIR: [chars]: "[chars]" is not a valid [chars]: [chars] ([dec]).Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_HB: [chars]: "[dec]" is not a valid heartbeat timeout.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_SHELLTREE: [chars]: invalid shell parser tree [chars] for service [chars]: [chars] ([dec]).Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE: [chars]: standby_mode should be run.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALIDSTDBYDEPEND: [chars]: service [chars] cannot be dependent on service [chars] due to the standby mode wait for that service.Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed.
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-PARSEERR_INVALID_TRANSL: [chars]: invalid translator [chars] for service [chars]: [chars] ([dec]).Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_INVALID_UGRPENTRY: [chars]: service "[chars]" is not defined.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_MISSINGOPTION: [chars]: option [chars]-][chars] missing from service definition for service "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND: [chars]: service [chars] is MTS unaware and cannot have handshake dependencies.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_NORESTART: [chars]: option [chars]-][chars] cannot be set without setting option [chars]-][chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_NOTCONFIG: [chars]: [chars] implemented only for service config.Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_REP_UGRPENTRY: [chars]: service [chars] is used in more than one upgrade group. First use in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS: [chars]: too many dependencies ([dec]) for service "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_UGRPDUPLICATEDNAME: [chars]: upgrade group name "[chars]" already used in [chars].Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARSEERR_UGRPNAMEREDEFINED: [chars]: the upgrade group is already called "[chars]".Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.
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.2(2a).
Error Message SYSMGR-2-PARTIAL_CFGWRITE_ABORTED: Partial configuration copy aborted.Explanation A partial configuration copy has failed.
Recommended Action Use the other syslog messages to verify that the problem has been corrected, and try again.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-REDSTATE_GETFAILED: Failed to request redundancy state: [chars] (error-id [hex]).Explanation The local supervisor is unable to get the redundancy state.
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.2(2a).
Error Message SYSMGR-2-REDSTATE_SETFAILED: Failed to set redundancy state: ret_val ([dec]).Explanation The local supervisor is unable to get the redundancy state.
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.2(2a).
Error Message SYSMGR-2-REDUNDANCY_CHANNEL_FAILURE: Remote sup will be rebooted since its coming up as active when local sup is still active.Explanation Remote supervisor is becoming active although local supervisor is still active. As a result, the local supervisor will cause the remote supervisor to reset itself.
Recommended Action If the problem persists, contact customer support. 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.2(2a).
Error Message SYSMGR-2-REDUNDANCY_HEARTBEAT_FAILURE: Heartbeat between active and standby on the redundancy channel not working for last [dec] minutes.Explanation This supervisor is not receiving a heartbeat on the redundancy channel from the other supervisor. This can result in problems during switchover and switchover may fail.
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.2(2a).
Error Message SYSMGR-2-RESTART_SYSTEM_LOG: We will be restarting system soon.Explanation The system will restart because it was trying to do a hot switchover before all the state was transferred to this supervisor. A cold switchover has begun.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-RESTORE_RUNTIME_DB_FAILED: Restoring of runtime database for fabric switch upgrade failed during boot (error-id [hex]).Explanation The runtime database cannot be restored during the boot process 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 2.1(1a).
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.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-STARTUP_CONVERSION_FAILED: Startup config conversion failed during boot (error-id [hex]).Explanation The conversion of the startup configuration failed during boot.
Recommended Action If the problem persists, Use the init system CLI command from the switch(boot)# prompt to initialize the configuration partition. Note:This is a disruptive command. This command will initialize the switch, reset the entire internal disk, and reformat the bootflash: partition.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-2-START_SCRIPT_FAILED: Start script (/isan/etc/rc.sysmgr start) failed with return value: ([dec]).Explanation The initialization of the system could not complete.
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.2(2a).
Error Message SYSMGR-2-SWITCHOVER_OVER: Switchover completed.Explanation The switchover is completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-SYNC_FAILURE_STANDBY_RESET: Failure in syncing messages to standby causing standby to reset.Explanation Resetting the standby because messaging and transaction service (MTS) on the active is unable to synchronize messages to the standby.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-UNEXPECTED_GSYNC_RESTART_STANDBY: Sending a message to restart system on standby.Explanation Activity occurred on the active supervisor that is incompatible with the state of standby. System will be restarted on standby.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is unexpectedly high at [dec]%Explanation System volatile database space is almost full.
Recommended Action Issue the system pss shrink CLI command. If this message continues, contact your technical support representative.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSMGR-2-WARMSWITCHOVER_START: This supervisor is becoming active.Explanation A cold switchover has started.
Recommended Action When the other supervisor is back online, enter the show system reset-reason CLI command or use a similar Fabric Manager/Device Manager procedure to find out what caused the switchover.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-2-WDT_KGDB: System watchdog kgdb has been [chars] for slot [dec].Explanation System watchdog kgdb has been [chars]. If the command has been enabled, the system will go into kgdb if there is a watchdog timeout.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
SYSMGR-3
Error Message SYSMGR-3-CAPABILITY_REDUN_CHANGE: Redundancy mode changed to [chars] due to configuration change.Explanation Some configuration changes have occurred causing the administrative redundancy mode to change.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-CFGERASE_FAILED: Configuration erase failed (error-id [hex]).Explanation The requested configuration erase 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-CFGSNAPSHOT_FAILED: Configuration snapshot failed (error-id [hex]).Explanation The requested configuration snapshot 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-CFGWRITE_FAILED: 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-CFGWRITE_REJECT: Discarding request for configuration [chars]: configuration action already in progress.Explanation Another instance of the CLI command copy running-config startup-config is in progress.
Recommended Action Wait for the other instance to complete.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-CFGWRITE_SRVFAILED: Service "[chars]" failed to store its configuration (error-id [hex]).Explanation A required service has failed to store its configuration into the startup configuration. The overall configuration copy is considered failed.
Recommended Action Enter the show process CLI command or use a similar Fabric Manager/Device Manager procedure to verify that the system is running properly and the service is behaving correctly.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-CFGWRITE_SRVTIMEOUT: Service [chars] failed to store its configuration in the timeout period.Explanation The listed service failed to respond to a request to store its configuration into the startup-configuration. The overall configuration copy has 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.0(1b).
Error Message SYSMGR-3-COPY_CORES_FAILED: Copying cores failed ([dec]).Explanation Copying cores to the destination failed because of an error specified in the log.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-COREDUMP_TIMEOUT: Failed to store the core in the specified time. The supervisor will be reset.Explanation Failed to store a core dump in the specified time. The supervisor will be reset.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message SYSMGR-3-CORE_CLIENT_INIT_FAILED: Core client will not be started due to some internal error.Explanation Core client will not be started because of some internal error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-CORE_SERVER_INIT_FAILED: Core server will not be started due to some internal error.Explanation Core server will not be started because of some internal error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-DAEMONIZE_FAILED: Unable to daemonize service "[chars]": [chars] ([dec]).Explanation A service could not be started.
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.2(2a).
Error Message SYSMGR-3-FAILED_PFM_HANDSHAKE: PFM-handshake from service "[chars]" failed (error-id [hex]).Explanation The platform manager handshake has failed. The system cannot proceed with the initialization.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-GSYNC_TIMEOUT_FAILED: Failed to set timeout for global sync for an application ([dec]).Explanation Failed to set the time-out for global synchronization for an application. Global synchronization may be stuck permanently if the application never completes global synchronization.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-HEARTBEAT_FAILURE: Service "[chars]" sent SIGABRT for not setting heartbeat for last [dec] periods.Explanation A service is not setting proper heartbeats to the system manager. The system manager has terminated this service and if this service has restartability set to TRUE, the service will restart automatically.
Recommended Action If the problem persists, contact your customer support representative. 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.2(2a).
Error Message SYSMGR-3-INVALID_BOOT_HANDSHAKE: Boot-scope-handshake received from service [chars], that is in scope [dec] (not the boot scope).Explanation A service is trying to take actions that belong to a different class of services.
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.2(2a).
Error Message SYSMGR-3-INVALID_PFM_HANDSHAKE: PFM-handshake received from service [chars], that is in scope [dec] (not the boot scope).Explanation A service is trying to take actions that belong to the platform manager service.
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.2(2a).
Error Message SYSMGR-3-INVALID_TRANSITION: Transition from state [chars] to state [chars] is not allowed.Explanation Unexpected transition in the system manager state machine.
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.2(2a).
Error Message SYSMGR-3-INVALID_UUID: Service [chars] is configured with UUID [hex], but uses UUID [hex].Explanation The identity of a service is inconsistent in the image file.
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.2(2a).
Error Message SYSMGR-3-ISSU_BEGIN_FAILED: ISSU cannot proceed (error-id [hex]).Explanation This message indicates that a service has blocked the nondisruptive upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SYSMGR-3-MISSING_OPTIONAL_CAPABILITY: Incomplete support for the current running-config on standby supervisor.Explanation Loose configuration incompatibilities exist between active and standby supervisors. Operational redundancy mode is still set to high availability.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-MODULE_LOCK_FAILED: Failed to lock the local module to avoid reset (error-id [hex]).Explanation Locking the local module has failed. Reloading the local module may now cause switchover to fail.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-OPERATIONAL_MODE_WARM: Operational redundancy mode set to warm (error-id [hex]).Explanation Operational redundancy mode will be set to warm. The error message shows the error ID representing the reason.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
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).
Error Message SYSMGR-3-SERVICE_TERMINATED: Service [chars] (PID [dec]) has finished with error code [chars] ([dec]).Explanation A service has terminated its execution normally. Depending on the value of the error code and the high availability policies implemented for the service, the service might be restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-SHUTDOWN_OVER: The System Manager is shutting down now.Explanation The system manager has shut down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-SHUTDOWN_START: The System Manager has started the shutdown procedure.Explanation The system manager is starting a shutdown.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-SWITCHOVER_SRVFAILED: Service "[chars]" failed in performing its switchover actions (error-id [hex]).Explanation The switchover failed because a service could not transition to the active state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-TFTP_CORES_FAILED: TFTPing cores failed ([chars]).Explanation Sending cores to the destination using TFTP failed because of an error specified in the log.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-3-UNACCEPTABLE_WAIT: Service [chars], no response from System Manager after [dec] seconds. Terminating.Explanation A spawned service could not handshake with the system manager and was terminated.
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.2(2a).
Error Message SYSMGR-3-URIFS_APPLY_FAILED: Applying URI filesystem database failed (error-id [hex]).Explanation The application of URI file system database 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).
SYSMGR-4
Error Message SYSMGR-4-CFGWRITE_PARTIALFORCED: Some services are missing; partial configuration write forced.Explanation The system is not fully operational, but a configuration copy has been forced. The services that are not running will not save their configurations, and the next time they will restart with a default configuration.
Recommended Action Enter the show process CLI command or use a similar Fabric Manager/Device Manager procedure to find out which required services are not running.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-INVALID_GSYNC_GET: Service "[chars]" requesting gsync without setting proper flag in its conf file.Explanation Service is requesting global synchronization without setting the proper flag in its configuration file.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-ON_DEMAND_STOP: On-demand service "[chars]" stopped.Explanation The service start type is specified as type on-demand in its configuration file and an external request asked to terminate it.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-ON_DEMAND_STOP_UID_KNOWN: On-demand service "[chars]" stopped by uid ([dec]).Explanation The service start type is specified as type on-demand in its configuration file and an external request asked to stop it.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-PARSEWARN_INVALID_CFGFILE: [chars]: unable to find "[chars]": [chars] ([dec]).Explanation An error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-PARSEWARN_RESTART_CNT_TOO_BIG: Service "[chars]": [chars] restart count of [dec] too big, needs to be set to [dec].Explanation This is an internal debug message.
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.0(1b).
Error Message SYSMGR-4-PARSEWARN_VALUE_TOO_SMALL: [chars]: [chars] is too small, replaced with [dec].Explanation An error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-READCONF_REJECT: Discarding configuration update request: [chars].Explanation The system manager rejected the configuration update request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-READCONF_STARTED: Configuration update started (PID [dec]).Explanation A configuration update has started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-SRVSCOPE_COMPLETED: Completed execution for scope [chars].Explanation Execution completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-SRVSCOPE_DELAYED: Waiting for redundancy state; termination delayed for scope [chars].Explanation The system manager is waiting for the redundancy state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-SRVSCOPE_STARTED: Started execution for scope [chars].Explanation Execution started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-4-UGRP_ALL_COMPLETED: Upgrade completed for all the groups.Explanation The system manager completed a full upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SYSMGR-5
Error Message SYSMGR-5-ALL_SCOPES_STARTED: System services have completely started at this time.Explanation System services have started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGERASE_DONE: Configuration erase successful.Explanation The requested configuration erase has completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGERASE_STARTED: Configuration erase started (PID [dec]).Explanation The requested configuration erase has started. The error message shows the process ID of the process servicing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGINIT_STARTED: Initialization of the startup configuration started (PID [dec]).Explanation The requested initialization of the startup configuration has started. The Process-ID of the process servicing the request is listed in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSMGR-5-CFGSNAPSHOT_DONE: Configuration snapshot successful.Explanation The requested configuration snapshot has completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGSNAPSHOT_STARTED: Configuration snapshot started (PID [dec]).Explanation The requested configuration snapshot has started. The error message shows the process ID of the process servicing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGWRITE_DONE: Configuration copy successful.Explanation The requested configuration copy has completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CFGWRITE_STARTED: Configuration copy started (PID [dec]).Explanation On the active supervisor, this message indicates that the system has started to service a copy running-config startup-config CLI command requested by the user. On the standby supervisor, this message indicates that the system is synchronizing the startup configuration from the active supervisor.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-CONVERT_STARTUP_STARTED: Configuration conversion started (PID [dec]).Explanation The system has started conversion of the startup configuration. This occurs either on system boot or during the course of an upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-DELETE_BINARY_STARTUP_STARTED: Deletion of binary startup configuration started (PID [dec]).Explanation The system is the binary startup configuration, because of an error in the conversion of the startup conversion.
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.0(1b).
Error Message SYSMGR-5-HANDSHAKE_DONE: Handshake with service "[chars]" successfully performed.Explanation Handshake with the listed service was successful.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-HANDSHAKE_FAILED: Handshake with service "[chars]" failed since send failed: [chars] (error-id [hex]).Explanation Handshake with a service failed because system manager could not send handshake response to it.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-HANDSHAKE_VERIFYING_DONE: Handshake verification done from service "[chars]".Explanation Handshake verified for the listed service.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-5-IMPROPER_CLEANUP: Service "[chars]" exited without replying to swover request.Explanation A conditional service exited without replying to the switchover request.
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(3).
Error Message SYSMGR-5-ISSU_ABORT: Notifying services of aborted ISSU (PID [dec]).Explanation This message indicates that the nondisruptive upgrade has been aborted and the services have been asked to rollback any changes.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SYSMGR-5-ISSU_BEGIN_STARTED: Notifying services of ISSU (PID [dec]).Explanation This message indicates that the system has started notifying services for the nondisruptive upgrade. Services can block the upgrade at this point.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message SYSMGR-5-MODULE_ONLINE: System Manager has received notification of local module becoming online.Explanation The system manager has received notification of a local module going online.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-PARTIAL_CFGWRITE_ASCII_CONFIG: Startup-config version not present.Explanation Startup configuration version not present. ASCII configuration is applied automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-5-PARTIAL_CFGWRITE_DONE: Partial configuration copy successful.Explanation The requested configuration copy has completed successfully.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-PARTIAL_CFGWRITE_STARTED: Partial configuration copy started by UUID [hex] (PID [dec]).Explanation This message is printed only on active supervisor, and indicates that service with mentioned UUID has requested a partial write mem CLI command. The error message shows the process ID of the process servicing the request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-RECOVERY_FAILED: Stateful recovery failed, system manager will now start stateless.Explanation Stateful recovery failed; system manager will now restart system and start stateless.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-RUNTIME_DB_RESTORE_STARTED: Runtime database controller started (PID [dec]).Explanation The system started the restoration of the runtime database. This happens during the nondisruptive fabric switch upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-5-RUNTIME_DB_RESTORE_SUCCESS: Runtime database successfully restored.Explanation The runtime database was successfully restored for the nondisruptive fabric switch upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-5-RUNTIME_DB_SAVE_STARTED: Runtime database save has started (PID [dec]).Explanation The system has started to save the runtime database. This happens during the nondisruptive fabric switch upgrade.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
Error Message SYSMGR-5-SERVICE_DELETED: Service [chars] has been removed from the System Manager database.Explanation The service has been removed from the system manager database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-SERVICE_SUCCESS_EXIT: Service [chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]).Explanation A service has successfully exited its execution.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-SRV_ENQUEUED_FOR_START: Conditional service "[chars]" started by sap "[dec]" has been enqueued for start.Explanation The conditional service has been queued for start.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-5-STATE_CHANGED: System Manager state changed from [chars] to [chars].Explanation The system manager has experienced the listed state change.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-STATEFUL_STATE: System Manager is in state [chars] after stateful restart.Explanation The system manager is in the listed state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-SUBPROC_KILLED: "[chars]" (PID [dec]) hasn't caught signal [dec][chars].Explanation This is an internal debugging message. This is not a problem or malfunction.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSMGR-5-SUBPROC_TERMINATED: "[chars]" (PID [dec]) has finished with error code [chars] ([dec]).Explanation The listed process has terminated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-5-SUPERSTATE_CHANGED: System Manager super state changed from [chars] to [chars].Explanation The system manager has experienced a state change.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSMGR-5-UGRP_COMPLETED: Upgrade completed for group [dec].Explanation Upgrade completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SYSMGR-6
Error Message SYSMGR-6-SERVICE_STARTED: Service "[chars]" started with PID([dec]).Explanation The system manager is starting a service. This message is for debugging purposes only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-6-SRVSTATE_CHANGED: State for service "[chars]" changed from [chars] to [chars].Explanation The service has changed state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
SYSMGR-7
Error Message SYSMGR-7-CFGWRITE_UNEXPECTEDRSP: Discarding unexpected response from service "[chars]".Explanation The system manager discarded an unexpected response from a service.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-DUPLICATED_PFM_HANDSHAKE: PFM-handshake received from service [chars], but information already available.Explanation Platform Manager (PFM) handshake received.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-LIBCDB_FAILURE: Conversion for service "[chars]" failed in libcdb.Explanation Either the system could not find conversion tarball or there is no conversion library needed for this service.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-LIBVDB_FAILURE: Conversion for service "[chars]" failed in libvdb.Explanation The system could not find package information for this service in the version database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-NO_STARTUP_CONFIG: No startup-config to convert.Explanation The system tried to convert startup configuration but it found no configuration to convert.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-SWITCHOVER_SRVSUCCEDED: Service "[chars]" completed its switchover actions.Explanation The service has completed switchover.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-UNEXPECTEDMSG: Opcode [dec] not expected at this time from service "[chars]" ([chars]).Explanation Unexpected opcode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-UNKNOWNADDR: Opcode [dec] received from unknown source [chars]. Discarding.Explanation Received opcode from an unknown source.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-UNKNOWNMSG: Unknown opcode [dec] received from [chars].Explanation The system manager has received an unrecognized message with the specified opcode. The error message shows the source of the message. This message is for debugging purposes only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message SYSMGR-7-UNKNOWNPID: Opcode [dec] received from [chars] with unknown PID [dec]. Discarding.Explanation The system manager has received a message from an unknown process. The error message shows the source of the message. This message is for debugging purposes only.
Recommended Action No action is required.
Error Message SYSMGR-7-UNKNOWNUUID: Opcode [dec] received from [chars] with unknown UUID [dec]. Discarding.Explanation The system manager has received an unrecognized message from the specified UUID. [chars] is the source of the message. This message is for debugging purposes only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
SYSTEMHEALTH Messages
This section contains the system health (SYSTEMHEALTH) messages.
SYSTEMHEALTH-2
Error Message SYSTEMHEALTH-2-OHMS_BATTERY_FAILED: Battery [dec] failed for module [dec]. Reason: [chars].Explanation Battery failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED: Bootflash test maximum failures reached for module [dec]. Reason: [chars].Explanation Bootflash failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module [dec]. Reason: [chars].Explanation Compact flash test errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_DAY: Bootflash hard resets for module [dec] has reached threshold limit in 24 hours.Explanation The number of bootflash hard resets reached the threshold limit in 24 hours.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_LIFE: Bootflash hard resets for module [dec] has reached the maximum threshold limit.Explanation The number of bootflash hard resets reached the maximum threshold limit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(2).
Error Message SYSTEMHEALTH-2-OHMS_CACHE_DISK_FAILED: Cache disk [dec] failed for module [dec].Explanation Cache disk failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_EMGMT_FAILED: Management port failed for module [dec].Explanation Ethernet management port failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_EOBC_FAILED: EOBC test failed for module [dec].Explanation Ethernet out-of-band channel (EOBC) test failed for the module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_FIPS_FAILURE: FIPS compliance error during random number generation.Explanation FIPS compliance error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_FREE_DISK_FAILED: Free Disk Space on partition [chars] is below threshold for module [dec].Explanation System Health Free Disk Space below threshold.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-2-OHMS_INBAND_FAILED: Inband test maximum failures reached for module [dec].Explanation Inband failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_LC_CF_INIT_ERRORS: Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec] Reason: [chars].Explanation Compact Flash CRC checksum initializations failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module [dec] Port [dec] has failed loop back tests.Explanation Port loop-back test failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_NVRAM_FAILED: Nvram test maximum failures reached for module [dec] for blocks 0x%llx.Explanation NVRAM failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-2-OHMS_MOD_RELOAD_REQ: Module [dec] reload being requested due to errors found by [chars] test.Explanation System Health module reload request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_MOD_SNAKE_TEST_FAILED: Module [dec] has failed snake loopback tests.Explanation Snake test failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_FAILED: Compact Flash firmware CRC checksum on module[dec] is corrupted.Explanation Compact Flash firmware corrupted.
Recommended Action Replace the compact flash on this module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_REFLASH_FAILED: Compact Flash firmware refresh procedure failed, replace the compact flash on module [dec]. Reason: [char].Explanation Compact Flash firmware corrupted.
Recommended Action Schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_INIT_ERRORS: Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec]. Reason: [chars].Explanation Compact flash CRC checksum initializations failed.
Recommended Action Check the compact flash on the board and any relevant system (mis)configurations.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_SWITCH_RELOAD_REQ: Switch reload request due to errors found [chars] test.Explanation System Health switch reload request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_SWITCHOVER_REQ: Supervisor switch over being requested due to errors found [chars] test.Explanation System Health switchover request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_FAILED: TCAM test failed for module [dec].Explanation TCAM test failed for module as uncorrectable parity errors detected.
Recommended Action Schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_OFLOW: Too many TCAM parity errors detected on module [dec].Explanation More parity errors than that can be corrected were detected on the affected module.
Recommended Action Schedule a downtime and reload the compact flash on the affected module. If errors continue after module reload, replace the module.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
SYSTEMHEALTH-4
Error Message SYSTEMHEALTH-4-ACT_ARB_MAX_FAIL: Active Arbiter test MAX failures reached.Explanation Active arbiter test maximum failures reached.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-ACT_CF_MAX_FAIL: Active Bootflash test MAX failures reached.Explanation Active bootflash test maximum failures reached.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_BATTERY_ERRORS: Battery test on module [dec] has been suspended due to internal errors.Explanation Battery test internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-4-OHMS_BATTERY_FAILING: Battery [dec] starting to fail on module [dec]. Reason: [chars].Explanation System Health battery failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_BOOTFLASH_FAILING: Bootflash starting to fail on module [dec].Explanation System Health bootflash failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_BOOTFLASH_TEST_ERRORS: Bootflash test cannot proceed due to internal errors on module [dec].Explanation Compact Flash test internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_CACHE_DISK_ERRORS: Cache disk test on module [dec] dpp [dec] has been suspended due to internal errors.Explanation Cache disk test internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-4-OHMS_CF_CRC_PASSED: Compact Flash firmware on module [dec] is healthy at this time.Explanation Compact Flash modeland Cache disk test internal errors.
Recommended Action Schedule a downtime and replace the Compact Flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_CF_REPLASH_PASSED: Compact Flash firmware was sucessfully refreshed on module [dec].Explanation Compact Flash model has data retention issues and needs to be replaced.
Recommended Action Schedule a downtime and replace the Compact Flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_CDISK_FAILING: Cache disk [dec] starting to fail on module [dec].Explanation System Health cache disk failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_EMGMT_ERRORS: Management port test cannot proceed due to internal errors on module [dec].Explanation Ethernet management port internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_EMGMT_FAILING: Management port on module [dec] starting to show signs of failures.Explanation System Health Ethernet management failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_EOBC_ERRORS: EOBC test on module [dec] has been suspended due to internal errors.Explanation Ethernet out-of-band channel (EOBC) test internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_EOBC_FAILING: EOBC starting to fail on module [dec].Explanation System Health Ethernet out-of-band channel failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_EXIT: Online System Health exiting due to internal errors. Reason [dec].Explanation Online system health exiting because of internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_FAIL_ACTION_NOTICE: Failure action not taken, failure action is disabled.Explanation System Health SERDES test failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_FREE_DISK_ERRORS: Too many errors on module [dec] while running the Free Disk Space test for partition [chars].Explanation System Health Free Disk Space test has too many errors while running.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-4-OHMS_INBAND_FAILING: Inband starting to fail on module [dec].Explanation System Health inband failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_INBAND_TEST_ERRORS: Too many errors while running the inband test.Explanation Inband test has had too many errors while running.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_EXITED: System Health process running on module [dec] exited due to internal errors. Will attempt to restart.Explanation Online system health line card (OHMS LC) daemon exited.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_FAILED: System Health process running on module [dec] failed due to fatal errors.Explanation Online system health line card (OHMS LC) daemon failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_RESTARTED: System Health process running on module [dec] restarted.Explanation Online system health line card (OHMS LC) daemon restarted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_TEST_ERRORS: Snake Loopback test cannot proceed due to internal errors for module [dec].Explanation Snake test internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_PATH_FAILURE: Snake Loopback data path failure on module [dec].Explanation Snake data path only error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-4-OHMS_NVRAM_ERRORS: Too many errors on module [dec] while running the Nvram test.Explanation NVRAM test has had too many errors while running.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-4-OHMS_SERDES_FAILED: Serdes loopback test on interface fc[dec]/[dec] failed.Explanation System Health SERDES test failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module [dec]. Reason: [chars].Explanation Compact flash test errors on supervisor module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_TEST_FAILING: Compact Flash firmware CRC checksum validation starting to fail on module [dec].Explanation Compact flash firmware CRC checksum may be bad on this module.
Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless upgrades or downgrades.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_TEST_FAILING: Compact Flash firmware refresh procedure starting to fail on module [dec].Explanation Compact flash may be bad on this module.
Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless upgrades or downgrades.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_INIT_ERRORS: Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec] Reason: [chars].Explanation Compact Flash CRC checksum initializations failed.
Recommended Action Check the compact flash on the board and any relevant system(mis) configurations.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_INTERN_ERRORS: Compact Flash firmware CRC checksum procedure cannot proceed due to internal errors on module [dec].Explanation Compact Flash CRC checksum procedure was terminated due to internal errors.
Recommended Action Restarting the cf-crc-check using system health clear-errors module <x> cf-crc-check. If the condition persists, schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_RECALLED: Compact Flash on module [dec] is healthy at this time. But this has been identified a recalled part. Please replace it soon since it can go bad anytime.Explanation Compact Flash model has data retention issues and needs to be replaced.
Recommended Action Schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_UNRESPONSIVE: Recalled Compact Flash on module [dec] is unresponsive.Explanation The compact flash model has data retention issues and needs to be replaced.
Recommended Action Schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.1(3).
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_INTERN_ERRORS: Compact Flash firmware re-flash procedure cannot proceed due to internal errors on module [dec].Explanation Compact Flash firmware reflash procedure terminated due to internal errors.
Recommended Action Restarting the test using system health clear-errors module <x> cf-re-flash. If the condition persists, schedule a downtime and replace the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-4-OHMS_SVC_DAEMON_FAILED: System Health process running on module [dec] SVC node [dec] exited due to errors.Explanation Online system health San Volume Controller (OHMS SVC) daemon exited.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ERRORS: TCAM test on module [dec] has been suspended due to internal errors.Explanation TCAM test suspended due to internal errors.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_UPDATE_FAILING: TCAM test failed as ACL/FIB failed to update TCAM on module [dec].Explanation ACL/FIB failed to update TCAM after soft parity errors were encountered.
Recommended Action If significant packet drops are encountered in the forwarding engine, schedule a downtime and reload the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_TIMEOUT: TCAM test timeout waiting for ACL/FIB to update TCAM on module [dec].Explanation System Health TCAM test timeout occured while waiting for response from ACL/FIB.
Recommended Action If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the compact flash on the affected module.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-4-OHMS_TEST_FAILING: [chars] test starting to fail on module [dec].Explanation System Health test failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-4-STB_ARB_MAX_FAIL: Standby Arbiter test MAX failures reached.Explanation Standby arbiter test maximum failures reached.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-4-STB_CF_MAX_FAIL: Standby Bootflash test MAX failures reached.Explanation Standby bootflash test maximum failures reached.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
SYSTEMHEALTH-5
Error Message SYSTEMHEALTH-5-OHMS_BATTERY_FAILING: Battery [dec] starting to fail on module [dec]. Reason: [chars].Explanation System Health battery failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_BOOTFLASH_FAILING: Bootflash starting to fail on module [dec].Explanation System Health bootflash failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_CDISK_FAILING: Cache disk [dec] starting to fail on module [dec].Explanation System Health cache disk failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_EMGMT_FAILING: Management port on module [dec] starting to show signs of failures.Explanation System Health Ethernet management failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_EOBC_FAILING: EOBC starting to fail on module [dec].Explanation System Health Ethernet out-of-band channel (EOBC) failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_FREE_DISK_FAILING: Free Disk Space on partition [chars] is staring to go below threshold for module [dec].Explanation System Health Free Disk Space going below threshold.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-5-OHMS_INBAND_FAILING: Inband starting to fail on module [dec].Explanation System Health inband failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4b).
Error Message SYSTEMHEALTH-5-OHMS_NVRAM_FAILING: Nvram starting to fail on module [dec].Explanation System Health NVRAM failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_FAILING: TCAM starting to fail on module [dec].Explanation System Health Tcam failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_CLEARED: Failing conditions for TCAM on module [dec] have been cleared.Explanation System Health TCAM failures cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.3(1a).
Error Message SYSTEMHEALTH-5-OHMS_TEST_FAILING: [chars] test starting to fail on module [dec].Explanation System Health test failing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-5-OHMS_SUP_CF_ERRORS_CLEARED: Compact flash failing conditions on module [dec] has been cleared.Explanation Compact Flash may be bad on this module.
Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless upgrades/downgrades.
Introduced Cisco MDS SAN-OS Release 3.1(3).
SYSTEMHEALTH-6
Error Message SYSTEMHEALTH-6-OHMS_ASIC_FAILURE_INFO: Module [dec] Asic [chars] instance [dec] probable cause of failure.Explanation Hardware failure analysis findings.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-6-OHMS_BATTERY_CLEARED: Failing conditions for battery [dec] on module [dec] have been cleared.Explanation System Health battery failure cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_BOOTFLASH_CLEARED: Failing conditions for bootflash on module [dec] have been cleared.Explanation System Health bootflash failures cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_CDISK_CLEARED: Failing conditions for cache disk [dec] on module [dec] have been cleared.Explanation System Health cache disk failure cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_EMGMT_CLEARED: Failing conditions for management port on module [dec] have been cleared.Explanation System Health Ethernet management port failure cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_EOBC_CLEARED: Failing conditions for EOBC on module [dec] have been cleared.Explanation System Health Ethernet out-of-band channel (EOBC) failures cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_FAILURE_CLEARED: Failing conditions for test [chars] has been cleared on module [dec].Explanation System Health failure cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_INBAND_CLEARED: Failing conditions for inband on module [dec] have been cleared.Explanation System Health inband failures cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_INBAND_DROP: Inband Dropping frames from module [dec] due to unknown reasons.Explanation System Health inband non-timeout drop.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_INBAND_TO_ERR: Inband Dropping frames from module [dec] due to timeout errors.Explanation System Health inband timeout drop.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message SYSTEMHEALTH-6-OHMS_INBAND_TX_CONGESTION: Inband Unable to transmit due to TX path congestion on module [dec].Explanation System Health Inband TX congestion.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-6-OHMS_NVRAM_CLEARED: Failing conditions for Nvram on module [dec] have been cleared.Explanation System Health NVRAM failures cleared.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message SYSTEMHEALTH-6-OHMS_STARTED: Online System Health started.Explanation Online System Health started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message SYSTEMHEALTH-6-STARTED: Online Health Manager started.Explanation Online health manager started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(1).
TACACS Messages
This section contains the Terminal Access Controller Access Control System Plus (TACACS+) messages.
TACACS-2
Error Message TACACS-2-TACACS_PROGRAM_EXIT: TACACS+ daemon exiting: [chars].Explanation Terminal Access Controller Access Control System Plus (TACACS+) daemon is exiting.
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).
TACACS-3
Error Message TACACS-3-TACACS_ERROR_MESSAGE: [chars].Explanation Terminal Access Controller Access Control System Plus (TACACS+) error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
TACACS-6
Error Message TACACS-6-TACACS_ACCOUNTING_MESSAGE: [chars].Explanation Accounting message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message TACACS-6-TACACS_MESSAGE: [chars].Explanation Terminal Access Controller Access Control System Plus (TACACS+) message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
TCAP Messages
This section contains the terminal capture (TCAP) messages.
TCAP-2
Error Message TCAP-2-MEM_FULL: Memory allocation failed.Explanation Terminal capture process has failed to allocate memory.
Recommended Action Enter the show tcap event-history CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TCAP-2-PROC_DN: Process is shutting down: [chars].Explanation Terminal capture process is exiting.
Recommended Action Enter the show tcap event-history CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TCAP-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation Terminal capture process has failed initialization.
Recommended Action Enter the show tcap event-history CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TLPORT Messages
This section contains the translation port (TLPORT) messages.
TLPORT-2
Error Message TLPORT-2-INITFAIL: TL Port Manager Initialization failed: [chars].Explanation TL port manager initialization failed. The error message explains the reason for the failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TLPORT-3
Error Message TLPORT-3-ALLOCFAIL: Heap Memory allocation failed: [chars].Explanation TL port manager is out of dynamic memory.The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-3-FC2ERROR: [chars].Explanation TL port manager encountered a Fibre Channel Layer 2 (FC-2) error. The error message specifies the context where the error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-3-GENERROR: [chars].Explanation TL port manager encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-3-MTSERROR: [chars].Explanation TL port manager encountered a messaging and transaction service (MTS) error. The error message specifies the context where the error occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-3-PSSERROR: [chars].Explanation TL port manager encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TLPORT-6
Error Message TLPORT-4-TLPM_ALPA_CACHE_FULL: Translation Port ALPA cache is full. Some new entries may not be cached.Explanation TL port cache is currently fully populated with active entries. There is no available cache space to be assigned any newly created Arbitrated Loop Physical Address (ALPA) entry on a TL port. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release1.3(5).
TLPORT-6
Error Message TLPORT-6-MGRCREATED: Translation port manager created.Explanation TL port manager was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-6-MGREXIT: Translation port manager shutting down gracefully.Explanation TL port manager is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-6-PORTDOWN: Translation Port [chars] DOWN.Explanation A port configured as a TL port is down and out of operation. The error message shows the Interface-ID string that identifies the TL port. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TLPORT-6-PORTUP: Translation Port [chars] UP.Explanation A port configured as a TL port is up and operational. The error message shows the Interface-ID string that identifies the TL port. This is an informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TP C Messages
TPC stands for Third Party Copy. It is for the feature Network Accelerated Serverless Backup (NASB).
Error Message TPC-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN :[dec] VT pWWN :[chars] DPP died.Explanation The data path processor (DPP) associated with the virtual target has crashed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars] VT Activate failed.Explanation The activate step for a virtual target has failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN :[dec] VT pWWN :[chars] VT and NPort creation FAILED !!!.Explanation The virtual target and nport creation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target : [chars] Deleted.Explanation The virtual target in the associated VSAN is being destroyed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars] VSAN down.Explanation The VSAN where the virtual target is configured is down.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
TTYD Messages
This section contains the TTY daemon (TTYD) messages.
TTYD-2
Error Message TTYD-2-TTYD_ERROR: TTYD Error [chars].Explanation Critical TTY daemon (TTYD) problems.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars].Explanation Miscellaneous TTY daemon (TTYD) message problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars].Explanation Miscellaneous TTY daemon (TTYD) debug facility problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TTYD-3
Error Message TTYD-3-TTYD_MISC_ERROR: Error [chars] with error [chars]([hex]).Explanation Miscellaneous TTY daemon (TTYD) problems.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
TTYD-6
Error Message TTYD-6-TTYD_MISC: TTYD [chars].Explanation The TTY daemon miscellaneous message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars].Explanation The TTY daemon configuration storage related message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VEC Messages
This section contains the virtual enclosure client (VEC) messages. These messages report errors that occur when accessing the backend disks.
VEC-SLOT#-3
Error Message VEC-SLOT#-3-LOG_DPP_EXCEPTION: DPP Exception DPP [dec].Explanation A data path processor (DPP) exception has been logged. The error message shows which DPP encountered this problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-3-LOG_ERR_DISK: VSAN [chars] SENSE_KEY([chars] ASC([chars].Explanation An error occurred. SENSE_KEY and ASC refer to the ANSI T10 SP3 SCSI specification at http://www.t10.org
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 1.3(4b).
Error Message VEC-SLOT#-3-LOG_GUID_MISMATCH: GUID Mismatch DPP [dec] PWWN [chars] lun [chars] Expected [chars] Read [chars].Explanation The disk GUID verification performed by the data path processor (DPP) failed. Access to the disk is denied.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VEC-SLOT#-4
Error Message VEC-SLOT#-4-LOG_DPP_REBOOTED: DPP [dec] Rebooted.Explanation The data path processor (DPP) has been rebooted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VEC-SLOT#-5
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DISK: SCSI STATUS([hex]) [chars] SENSE_KEY([hex]) [chars] ASC([hex]) ASCQ([hex]) [chars].Explanation An error has occurred. SCSI STATUS, SENSE_KEY, ASC, and ASCQ refer to the ANSI T10 SP3 SCSI specification at http://www.t10.org.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DPP_MON_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) data path processor (DPP) monitor finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DPRLI_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) distributed process login (DPRLI) finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_GID_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) GUID ID finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST: Host VSAN :[dec] Host pWWN :[chars] access denied to VEP pWWN :[chars] due to licensing.Explanation The host bus adapter (HBA) is denied access to the virtual enclosure port (VEP) because of licensing.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LMAP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars].Explanation An event is received for a state in the virtual enclosure client (VEC) HOST LMAP XP finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LOGO: Logging out Host [VSAN :[dec] pWWN :[chars]] logged in to VEP [pWWN :[chars]]. Reason: Host not responding.Explanation The host bus adapter (HBA) is logged out from the virtual enclosure port (VEP) as it is not responding to address discovery (ADISCs) initiated from the VEP.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_XP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars].Explanation An event is received for a state in the virtual enclosure client (VEC) HOST XP finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_NPORT_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) N port finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_PID_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) process ID finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TARGET_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) TARGET initialization state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TCAM_MON_FSM: Illegal Event [chars] in State [chars] DPP :[dec].Explanation An event is received for a state in the virtual enclosure client (VEC) ternary content addressable memory (TCAM) MON finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] TP nWWN :[chars] TP pWWN :[chars].Explanation An event is received for a state in the virtual enclosure client (VEC) TP finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP nWWN :[chars] VEP pWWN :[chars].Explanation An event is received for a state in the virtual enclosure client (VEC) virtual enclosure port (VEP) finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_ILC_LIMIT: VEP [VSAN :[dec] pWWN :[chars]] could not be created. Reason : ILC VEP limit [dec] reached.Explanation The virtual enclosure port (VEP) could not be created as the intelligent line card (ILC) limit of VEPs has been reached.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VLUN_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) virtual LUN finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VO_FSM: Illegal Event [chars] in State [chars] FSM [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) VO finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_FSM: Illegal Event [chars] in State [chars] VSAN [dec].Explanation An event is received for a state in the virtual enclosure client (VEC) VSAN finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_XCHG_FSM: Illegal Event [chars] in State [chars] VES IP Addr [chars].Explanation An event is received for a state in the virtual enclosure client (VEC) VSAN XCHG finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_NOTICE_VEC_SLEEP_THRESH: VEC not scheduled for [dec] seconds.Explanation The virtual enclosure client (VEC) process sleep threshold was exceeded, which should not have occurred. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEC-SLOT#-5-LOG_NOTICE_VEC_WORK_THRESH: VEC did not yield the cpu for [dec] seconds.Explanation The virtual enclosure client (VEC) process work threshold was exceeded, which should not have occurred. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VEDB_MGR Messages
This section contains the virtual enclosure database (VEDB_MGR) messages.
VEDB_MGR-2
Error Message VEDB_MGR-2-MALLOC_ERROR: Size [dec] bytes.Explanation The virtual enclosure database (VEDB) library could not allocate memory.
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.2(2a).
VEDB_MGR-6
Error Message VEDB_MGR-6-EXITING: Exited due to [chars].Explanation The virtual enclosure database (VEDB) library has exited. The process has probably been restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VEDB_MGR-6-SERVICE_UP: Initialized [chars].Explanation The virtual enclosure database (VEDB) library is up and ready to accept client requests The service was initialized in the mode shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VES Messages
This section contains the virtual enclosure server (VES) messages.
VES-SLOT#-4
Error Message VES-SLOT#-4-LOG_WARNING_VES_CONFIG_TOO_BIG: Volume [chars] configuration too large to virtualize.Explanation The VES maximum volume configuration was exceeded. The volume listed in the error message will be virtualized by the control plane processor (CPP).
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(2b).
VES-SLOT#-5
Error Message VES-SLOT#-5-LOG_ERR_VES_PATH_FSM: disk guids dont match - received verify_mismatch for pid [dec] from vec [dec].Explanation A VERIFY MISMATCH event was received for a state in the virtual enclosure server (VES) path finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VES-SLOT#-5-LOG_ERR_VES_VEP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP pWWN :[chars].Explanation An event is received for a state in the virtual enclosure server (VES) virtual enclosure port (VEP) finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_FSM: Illegal Event [chars] in State [chars] VSAN [dec].Explanation An event is received for a state in the virtual enclosure server (VES) VSAN finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_XCHG_FSM: Illegal Event [chars] in State [chars] VEC IP Addr [chars].Explanation An event is received for a state in the virtual enclosure server (VES)VSAN XCHG finite state machine (FSM) that should not have occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VES-SLOT#-5-LOG_NOTICE_VES_SLEEP_THRESH: VES not scheduled for [dec] seconds.Explanation The virtual enclosure server (VES) process sleep threshold was exceeded, which should not have occurred. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VES-SLOT#-5-LOG_NOTICE_VES_WORK_THRESH: VES did not yield the cpu for [dec] seconds.Explanation The virtual enclosure server (VES) process work threshold was exceeded, which should not have occurred. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VFC Messages
This section contains the virtual Fibre Channel (VFC) messages.
VFC-3
Error Message VFC-3-VFC_MEM_ERROR: Memory consistency problem.Explanation Miscellaneous target error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VFC-3-VFC_TGT_ERROR: Target error:[chars] 0x%llx.Explanation Miscellaneous target error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VFC-6-STARTING: deamon started.Explanation The virtual Fibre Channel (VFC) daemon successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
VHBAD Messages
This section contains the virtual host bus adapter daemon (VHBAD) messages.
VHBAD-2
Error Message VHBAD-2-PROC_ADD_NPORT_FAIL: Failed to set local nport with SCSI target driver error: [hex].Explanation SCSI target process tried to add N port with its peer kernel driver. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-2-PROC_OPEN_VHBA_DEVICE_FAIL: Failed to communicate with SCSI target driver error: [hex].Explanation SCSI target process failed to communicate with its peer kernel driver. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-2-PROC_SET_SCSI_INDEX_FAIL: Failed to set SCSI index SCSI target driver error: [hex].Explanation SCSI target process failed to set SCSI index with its peer kernel driver. No SCSI discovery can be performed.
Recommended Action Enter the show SCSI target internal driver CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-2-PROC_WWNM_GET_WWN_FAIL: Failed to get local controller pwwn from WWN Manager error: [hex] response: [hex].Explanation SCSI target process used the wwnm_bwt_get_local_controller_wwn() API for the port WWN and it failed because of the error and response code shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show process cpu and show system internal sysmgr service all CLI commands or use a similar Fabric Manager/Device Manager procedure to collect more information. See the WWN manager system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VHBAD-3
Error Message VHBAD-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) initialization failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PROC_VSAN_GET_RATOV_FAIL: Failed to get VSAN attribute RATOV from VSAN Manager, error: [hex].Explanation SCSI target process used the VSAN_get_global_value() API for RATOV and it failed because of the error shown in the error message.
Recommended Action This is a non-fatal error. The default value for RATOV is used. Enter the show process cpu and show system internal sysmgr service all CLI commands or use a similar Fabric Manager/Device Manager procedure to collect more information. See the VSAN Manager system error codes for reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_CREATE_FAIL: pss create runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) create runtime database failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) delete runtime entry key failed because of the error shown in the error message.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) set runtime max key failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) set runtime max value failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) open runtime database failed because of the error shown in the error message. No SCSI discovery can be performed.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) reload runtime database failed because of the error shown in the error message.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to uri:[chars] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) snapshot of runtime debug to URI failed because of the error shown in the error message.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) snapshot of runtime to URI failed because of the error shown in the error message.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VHBAD-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] failed due to error: [hex].Explanation SCSI target process persistent storage service (PSS) store runtime entry key failed because of the error shown in the error message.
Recommended Action Enter the show flash CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes for the reason.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VHBAD-7
Error Message VHBAD-7-SCSI_TARGET_DISCOVERED: SCSI target discovered VSAN:[dec] FCID:[hex] prlisparm:[hex].Explanation SCSI target process discovered the VSAN PRLI service parameter.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VNI Messages
This section contains the virtual network interface (VNI) messages.
VNI-2
Error Message VNI-2-ALLOC_MEMORY: Memory allocation failed.Explanation The service failed to allocate a block of dynamic memory.
Recommended Action Check the system memory. If system memory is low, reset the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VNI-3
Error Message VNI-3-INIT_FAILED: Initialization failed. Component [chars].Explanation The service failed to start.The failure occurred while initializing the component shown in the error message.
Recommended Action Enter the show processes CLI command or use a similar Fabric Manager/Device Manager procedure to check the status of the other processes. Debug the specified component.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VNI-6
Error Message VNI-6-INTERFACE_EVENT: VSAN interface [chars] [chars].Explanation The specified VSAN Interface had a successful event as shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VNI-6-STARTING: Virtual Network Interface Manager started.Explanation The service has successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VNI-6-VSAN_DELETED: VSAN [dec] has been deleted.Explanation The specified VSAN has been deleted. The service deleted all the configuration on that VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VOMD-SLOT Messages
This section contains the VOMD-SLOT messages.
VOMD-SLOT-2
Error Message VOMD-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot ILC.Explanation Component caused critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
VPM Messages
This section contains the virtual port manager (VPM) messages.
VPM-2
Error Message VPM-2-GENERAL_ERROR: [chars].Explanation The virtual port manager encountered a critical error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-2-MALLOC_ERROR: Size [dec] bytes.Explanation The virtual port manager could not allocate memory.
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.2(2a).
Error Message VPM-2-PSS_ERROR: [chars].Explanation The virtual port manager encountered an error while operating on a persistent storage database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-2-VPMON_CRIT: [chars] [dec].Explanation The virtual port manager (VPMON) daemon experienced a critical problem.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VPM-2-VPMON_DPP_DOWNLOAD: HB failure, Restarting the DPP [dec].Explanation The virtual port manager (VPMON) daemon is downloading the data path processor (DPP) again.
Recommended Action Intelligent switch application programming interface (ISAPI) users need to re-download the configuration data to the fast path.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VPM-2-VPMON_DPP_RELOAD_FORCE: Issuing of force reload to command for DPP(s) [chars] is: [chars].Explanation VPMON daemon critical action message. Reason is shown in the message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.1(1a).
VPM-3
Error Message VPM-3-PSS_SYNC_TO_STNDBY_FAILED: PSS TYPE=[chars] KEY=[chars].Explanation Could not send persistent storage service (PSS) synchronization notification to the standby supervisor. The PSS type, operation, and key are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-3-SEND_TO_ILC_FAILED: [chars].Explanation The virtual port manager could not send to the intelligent line card.(ILC for DG=%s, at slot=%d processor=%d and SAP=%d).
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.2(2a).
Error Message VPM-3-SEND_TO_SNMP_AGENT_FAILED: [chars].Explanation The virtual port manager could not send to the SNMP agent (for DG=%s).
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.2(2a).
Error Message VPM-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec].Explanation The virtual port manager has received an unknown message from the node and service access point (SAP) shown in the error message. This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-3-VPM_PSS_CORRUPTED: [chars] PSS found corrupted.Explanation The virtual port manager has detected corruption in one of its persistent information database. The database was recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VPM-4
Error Message VPM-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec].Explanation There was a version mismatch between the virtual port manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VPM-6
Error Message VPM-6-BECAME_ACTIVE: Became ACTIVE from standby mode.Explanation The virtual port manager on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-BECAME_STDBY: Became STANDBY from active mode.Explanation The virtual port manager became standby from active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-DG_DEREGISTERED: [chars].Explanation The virtual port manager has deregistered.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-DG_REGISTERED: [chars].Explanation The virtual port manager has registered.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-EXITING: Exited due to [chars].Explanation The virtual port manager process has exited because of the error shown in the error message. The process has been restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars].Explanation The virtual port manager was unable to send a heartbeat to the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-GENERAL_EVENT: [chars].Explanation The virtual port manager has generated an important event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-PSS_CREATED: [chars] PSS Created.Explanation One of the persistent information databases of the virtual port manager has been recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-PSS_DESTROYED: [chars] PSS Destroyed.Explanation One of the persistent information databases of the virtual port manager has been intentionally destroyed and was recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-SERVICE_UP: Initialized [chars].Explanation The virtual port manager is up and ready to accept client requests. The service was initialized in the mode shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VPM-6-SWITCHOVER: Switching Over to other Sup.Explanation The virtual port manager has successfully switched over to the standby supervisor module.
Recommended Action No action is required.
Error Message VPM-6-VPMON_INFO: [chars].Explanation A virtual port manager informational message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VPM-6-VPMON_STARTING: deamon started.Explanation The virtual port manager daemon successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VPM-6-VPM_MDS_LICENSE_GRACE: MDS LICENSE in grace period for feature: [chars].Explanation The feature license is in the grace period.
Recommended Action Configure a new license.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message VPM-6-VPM_MDS_LICENSE_REVOKED: MDS LICENSE REVOKED for feature : [chars].Explanation The feature license is revoked.
Recommended Action Configure a new license.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message VPM-6-VPM_MDS_TIMED_LICENSE: Timed MDS LICENSE for feature : [chars].Explanation Timed feature license.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
VPM-SLOT# Messages
This section contains the virtual port manager slot (VPM-SLOT) messages.
VPM-SLOT#-2
Error Message VPM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot ILC.Explanation The listed component caused a critical error.
Recommended Action Restart the line card.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
VRRP_CFG Messages
This section contains the Virtual Router Redundancy Protocol (VRRP_CFG) messages.
VRRP_CFG-2
Error Message VRRP_CFG-2-ALLOC_MEMORY: Memory allocation failed.Explanation The service failed to allocate a block of dynamic memory.
Recommended Action Check the system memory. If memory is low, reset the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VRRP_CFG-3
Error Message VRRP_CFG-3-INIT_FAILED: Initialization failed. Component [chars].Explanation The service failed to start. The failure occurred while initializing the component shown in the error message.
Recommended Action Enter the show processes CLI command or use a similar Fabric Manager/Device Manager procedure to check the status of the other processes and debug the specified component.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VRRP_CFG-5
Error Message VRRP_CFG-5-STARTING: VRRP Manager service started.Explanation The service successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_CFG-5-VR_ADMIN_DOWN: VR [chars]group [dec] on interface [chars] is administratively down.Explanation The specified Virtual Router Redundancy Protocol (VRRP) group is administratively down on the interface named.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_CFG-5-VR_ADMIN_UP: VR [chars]group [dec] on interface [chars] is administratively up.Explanation The specified Virtual Router Redundancy Protocol (VRRP) group is administratively up on the interface named.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_CFG-5-VR_CREATED: VR [chars]group [dec] created on interface [chars].Explanation The specified Virtual Router Redundancy Protocol (VRRP) group has been successfully created on the interface named.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_CFG-5-VR_DELETED: VR [chars]group [dec] removed from interface [chars].Explanation The specified Virtual Router Redundancy Protocol (VRRP) group has been successfully deleted on the interface named.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
VRRP_CFG-6
Error Message VRRP_CFG-6-STARTING: VRRP Manager service started.Explanation The service successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_CFG-6-VR_CREATED: VR group [dec] created on interface [chars].Explanation The specified Virtual Router Redundancy Protocol (VRRP0 group has been successfully created on the interface.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_CFG-6-VR_DELETED: VR group [dec] removed from interface [chars].Explanation The specified Virtual Router Redundancy Protocol (VRRP) group has been successfully deleted on the interface named.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VRRP_ENG Messages
This section contains the Virtual Router Redundancy Protocol (VRRP_ENG) messages.
VRRP_ENG-2
Error Message VRRP_ENG-2-ALLOC_MEMORY: Memory allocation failed.Explanation The service failed to allocate a block of dynamic memory.
Recommended Action Check if the system is low on memory and reset the switch if necessary.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-2-INVALID_CONFIG: Cannot start the VR [dec] on the interface [chars]. Invalid IP configuration. Reason: [chars].Explanation The specified virtual router on the interface is enabled, but the IP configuration is not valid because of the error shown in the error message.
Recommended Action Enter the show interface CLI command or use a similar Fabric Manager/Device Manager procedure to ensure the IP address of the interface is configured and is in the same subnet of the virtual router address.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-2-VR_FAILURE: Error in VR[chars] [dec] interface [chars]. Going to init state.Explanation The virtual router on the interface is in the initialization state because of an internal error.
Recommended Action Enter the show interface CLI command or use a similar Fabric Manager/Device Manager procedure to check the status of the interface. Check the configuration, status, and statistics of the specified virtual router and enable VRRP debug for further information. Enter shutdown and no shutdown on the specified virtual router.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VRRP_ENG-3
Error Message VRRP_ENG-3-INIT_FAILED: Initialization failed. Component [chars].Explanation The service failed to start. The failure occurred while initializing the component shown in the error message.
Recommended Action Enter the show process CLI command or use a similar Fabric Manager/Device Manager procedure to check the status of the other processes and debug the specified component.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VRRP_ENG-4
Error Message VRRP_ENG-4-BAD_ADV: VR[chars] ID [dec] on interface [chars] bad advertisement received: reason [chars].Explanation The virtual router specified has received an invalid advertisement.
Recommended Action Check that all VRRP nodes have the same configuration.
Introduced Cisco MDS SAN-OS Release 3.0(1).
VRRP_ENG-5
Error Message VRRP_ENG-5-INTERFACE_DOWN: Cannot start the VR[chars] [dec] since the interface [chars] is down.Explanation The specified VR is enabled but cannot change state from init. The specified interface is down or does not have a primary IP address configured.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed to [chars].Explanation The interface specified has changed state. This could have triggered a VRRP status change.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_ENG-5-STARTING: VRRP Engine service started.Explanation The service successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message VRRP_ENG-5-VR_STATE_CHANGE: VR[chars] ID [dec] on interface [chars] state changed to [chars].Explanation The status of the specified virtual router has changed to [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
VRRP_ENG-6
Error Message VRRP_ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change request result [chars].Explanation The virtual router specified has received an invalid advertisement.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-6-INTERFACE_DOWN: Cannot start the VR [dec] since the interface [chars] is down.Explanation The specified virtual router is enabled but cannot change state from initializing. The specified interface is down or does not have a primary IP address configured.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-6-INTERFACE_STATE_CHANGE: Interface [chars] state changed to [chars].Explanation The interface specified has changed state This could have triggered a VRRP status change.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-6-STARTING: VRRP Engine service started.Explanation The service successfully started.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-6-VR_STATE_CHANGE: VR ID [dec] on interface [chars] state changed to [chars].Explanation The status of the specified virtual router has changed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VRRP_ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change request result [chars].Explanation The result of the request for status change on the virtual router (with VSHA extension) specified is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VSAN Messages
This section contains the virtual SAN (VSAN) messages.
VSAN-2
Error Message VSAN-2-PROGRAM_EXIT: process exiting with reason: [chars].Explanation The Virtual SAN (VSAN) manager process is exiting with the reason shown in the error message.
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.2(2a).
VSAN-3
Error Message VSAN-3-CFS_OPERATION_FAILED: cfs [chars] operation failed : [chars].Explanation The Cisco Fabric Services (CFS) operation has failed.
Recommended Action Check the reason for the failure of the CFS operation and rectify the problem.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec].Explanation Memory allocation failed.
Recommended Action Enter the show process memory CLI command or use a similar Fabric Manager/Device Manager procedure to see memory usage for processes.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-3-MESSAGE_ERROR: could not handle message:[chars] of type [dec] sent by addr [dec]:[dec].Explanation Received an interprocess communications IPC message sent by a component running on the node and SAP shown in the error message.
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.2(2a).
VSAN-6
Error Message VSAN-6-ACTIVATED: VSAN:[dec] changing from suspended to active.Explanation Making VSAN (with ID shown in the error message) active from suspended state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-6-CFS_MERGE_NOT_SUPPORTED: merging of fctimer configuration data is not supported.Explanation Merging of fctimer configuration data using CFS is not supported.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VSAN-6-CREATED: Created VSAN:[dec] with name:[chars].Explanation Created VSAN with ID and name shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-6-MEMBERSHIP_UPDATE: Updated membership for interface:[chars] with VSAN:[dec].Explanation Updating membership for interface shown with the VSAN shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-6-REMOVED: Removed VSAN:[dec].Explanation Removed the VSAN with the ID shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-6-SUSPENDED: VSAN:[dec] changing from active to suspended.Explanation Suspending VSAN from active state.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSAN-6-TRUNKING_MEMBERSHIP_UPDATE: trunking membership updated for interface:[chars] with VSAN bitmap:[chars].Explanation Updated trunking membership for the interface with the allowed VSAN list.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VSHD Messages
This section contains the MDS shell (VSHD) messages.
VSHD-2
Error Message VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function [chars] from library [chars] exited due to Signal [dec].Explanation Error in CLI EOL function.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-2-VSHD_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec].Explanation Persistent storage service (PSS) snapshot error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec].Explanation Debug infrastructure error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VSHD-3
Error Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec].Explanation File handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars].Explanation Messaging and transaction service (MTS) message handling error.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars].Explanation Error while updating the parse tree in the MDS shell.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec].Explanation Persistent storage service (PSS) handling error.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VSHD-4
Error Message VSHD-4-VSHD_LICENSE_EXPIRY_WARNING: License [chars] expiry at [chars]. VSAN policy would be set default (deny) for all roles when license expires.Explanation VSAN policy will be set to default (deny) for all roles when the license expires.
Recommended Action Install the license file to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-4-VSHD_ROLE_DATABASE_OUT_OF_SYNC: Role configuration database found to be different between the switches during merge.Explanation We recommend that the role configuration database be identical among all switches in the fabric.
Recommended Action Edit the configuration on one of the switches to obtain the desired role configuration database and then commit it.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VSHD-4-VSHD_ROLE_DATABASE_VERSION_NOT_UNDERSTOOD: This switch does not understand the version of role configuration database received during merge.Explanation This is probably occurring due to different versions of system image on switches in the fabric.
Recommended Action Make sure all switches are running the same version of the system image.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message VSHD-4-VSHD_ROLE_DISTRIBUTE_FAILURE: Role distribution operation ([chars]) failed with error id [hex].Explanation This is probably occurring because of an unstable fabric.
Recommended Action Retry operation when fabric is stable.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
VSHD-5
Error Message VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from [chars] [chars].Explanation CLI configuration mode was exited.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] created.Explanation New CLI role created.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
VSHD-7
Error Message VSHD-7-VSHD_SYSLOG_PARSE_TREE_UPDATE: Parse tree [chars].Explanation Parse tree updated in shell.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN Messages
This section contains the World Wide Name (WWN) messages.
WWN-1
Error Message WWN-1-TYPE1_ALERT: [dec] (< [dec] %) Remain.Explanation The WWN manager has run out of WWNs. No new dynamically allocated WWNs are available. However, statically assigned WWNs such as switch WWN, port WWN, and so on are still available.
Recommended Action Add additional WWNs by programming a new secondary MAC address and its range.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-1-TYPES2_5_ALERT: [dec] (< [dec] %) Remain.Explanation The WWN manager has run out of WWNs of NAA (Network Address Authority) types 2 and 5.
Recommended Action Add additional WWNs by programming a new secondary MAC address and its range.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN-2
Error Message WWN-2-BKPLN_PROM_CANT_READ: Can not read backplane PROM.Explanation The WWN manager has failed to read chassis information. No dynamic WWNs could be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.2(2a).
Error Message WWN-2-EXITING: Exited due to [chars].Explanation The WWN manager process has exited because of the error shown in the error message. The process has probably been restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-GENERAL_ERROR: [chars].Explanation The WWN manager has encountered a critical error. The description of error is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-MALLOC_ERROR: Size [dec] bytes.Explanation The WWN manager could not allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.2(2a).
Error Message WWN-2-PSS_BKP_PSS_MISMATCH: Block [dec]: PSS: Not Free; BKPLN PROM: Free.Explanation This WWN manager detected a discrepancy between the information on the chassis and that in its persistent information databases. The persistent information database has been updated with the information on the chassis.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-PSS_ERROR: [chars].Explanation The WWN manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars].Explanation The WWN manager has failed to rotate its current stdout file with file name shown in the error message.The file size could grow beyond its maximum limit.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-TYPE1_CRIT: [dec] (< [dec] %) Remain.Explanation The WWN manager has only the shown percent or less of WWNs remaining.
Recommended Action Add additional WWNs by programming a new secondary MAC address and its range.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-2-TYPES2_5_CRIT: [dec] (< [dec] %) Remain.Explanation The WWN manager has only the shown percent or less of the WWNs of Network Address Authority (NAA) types 2 and 5 remaining.
Recommended Action Add additional WWNs by programming a new secondary MAC address and its range.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN-3
Error Message WWN-3-PSS_SYNC_TO_STNDBY_FAILED: PSS TYPE=[chars] KEY=[chars].Explanation Could not send persistent storage service (PSS) synchronization notification to the standby supervisor module. PSS type, operation, and key are shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-3-RELEASE_ERR: Cant Rel. WWN [chars].Explanation WWN manager received a request to release a WWN that cannot be released.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-3-RELEASE_ERR_UNKNOWN: Unknown WWN [chars] [chars].Explanation WWN manager received a request to release a WWN that could not have been allocated by this WWN manager because of the reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-3-STARTUP_COPY_TO_RUNNING_FAILED: [chars].Explanation Could not snapshot Startup-Config PSS to Running-Config. The description of error is [str.].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release.
Error Message WWN-3-TOOMANY_REQ_REL: WWNs [chars] = [dec] ]Explanation The WWN manager received a request to allocate a number of WWNs that is more than the maximum number of WWNs that can be allocated or released in a single request.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec] Opcode=[dec].Explanation The WWN manager has received an unknown message from the node and SAP with opcode shown in the error message. This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-3-WWN_PSS_CORRUPTED: [chars] PSS found corrupted.Explanation The WWN manager has detected corruption in one of its persistent information databases. The database was recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN-4
Error Message WWN-4-PSS_SUP_CNT_MISMATCH: PSS [dec] Bkpln [dec].Explanation The WWN manager has detected that some other supervisor module was plugged in earlier on this chassis. This WWN manager is making sure that newly allocated WWNs do not conflict with WWNs that could have been allocated by the previous supervisor module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec].Explanation There was a version mismatch between the WWN manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-4-TYPE1_WARN: [dec] (< [dec] %) Remain.Explanation The WWN manager has only the shown percent or less of WWNs remaining for allocation.
Recommended Action No action is required.
Error Message WWN-4-TYPES2_5_WARN: [dec] (< [dec] %) Remain.Explanation The WWN manager has only the shown percent or less of WWNs of Network Address Authority (NAA) types 2 and 5 remaining.
Recommended Action Add additional WWNs by programming a new secondary MAC address and its range.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN-5
Error Message WWN-5-VSAN_WWN_CHANGE: [chars].Explanation a VSAN-WWN has been created or deleted.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
WWN-6
Error Message WWN-6-ALLOCATED_BLOCK: Block number [dec].Explanation The WWN manager has allocated a new block of 256 WWNs for internal use.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-BECAME_ACTIVE: Became ACTIVE from standby mode.Explanation The WWN manager on the standby supervisor module became active and it is ready to serve client requests for WWNs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-BECAME_STDBY: Became STANDBY from active mode.Explanation The WWN manager became standby from active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-EXCESSIVE_DELAY: [chars].Explanation Excessive time taken for a processing event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars].Explanation The WWN manager was unable to send a heartbeat to the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-GENERAL_EVENT: [chars].Explanation The WWN manager has generated an important event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-PSS_CREATED: [chars] PSS Created.Explanation One of the persistent information databases of the WWN manager has been recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-PSS_DESTROYED: [chars] PSS Destroyed.Explanation One of the persistent information databases has been intentionally destroyed and was recreated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-RELEASED_BLOCK: Block number [dec].Explanation The WWN manager has released a block of 256 WWNs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-SEC_MAC_UPDATED: MAC=[chars] Range=[dec].Explanation The WWN manager had updated the secondary MAC address with the MAC address and range shown in the error message. This update was initiated from a management entity.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message WWN-6-SERVICE_UP: Initialized [chars].Explanation The WWN manager is up and ready to accept client requests for WWNs. The service was initialized in the mode shown in the error message.
Recommended Action No action is required.
Error Message WWN-6-SWITCHOVER: Switching Over to other Supervisor.Explanation The WWN manager has successfully switched over to the standby supervisor module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
WWN-7
Error Message WWN-7-RELEASE_ERR_FREE: Already free WWN [chars].Explanation A client of WWN manager attempted to release a WWN that is already free. This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
XBAR Messages
This section contains the crossbar (XBAR) messages.
XBAR-3
Error Message XBAR-3-MEM_FULL: Memory allocation failed.Explanation Memory allocation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
XBAR-5
Error Message XBAR-5-ARB_INIT_MOD_INTR_FAIL: Arbiter reported failure to enable interrupt for module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-ARB_INIT_MOD_REMOVE_FAIL: Arbiter reported failure to remove module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-ARB_INIT_PORT_FAIL: Arbiter reported failure to register port [dec] in group [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-ARBITER_INIT_FAILURE: Re-initializing Arbiter.Explanation The supervisor module has experienced an arbiter setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message XBAR-5-MOD_CONNECTION_REATTEMPT: Re-attempting Xbar connection with module [dec].Explanation The module has experienced a setup failure on connecting the module to the fabric.
Recommended Action Enter the show xbar internal event-history command or use a similar Fabric Manager/Device manager procedure to collect more informations about the crossbar component. Power cycling the module may fix the problem.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message XBAR-5-XBAR_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig intialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error MessageError Message XBAR-5-XBAR_INIT_FAILURE: Xbar [chars] initialization failed.Explanation The supervisor module has experienced a fabric initialization failure. The supervisor module rebooted. In case of dual supervisors, a switchover will occur.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a)
Error Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_PORT_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_PORT_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_RELEASE_ACCESS_FAIL: Slot [dec] reported failure releasing [chars] xbar access return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar access failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_SET_ACCESS_FAIL: Slot [dec] reported failure acquiring [chars] xbar access return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar access failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR-5-XBAR_STATUS_REPORT: Module [dec] reported status for component [dec] code [hex].Explanation An error status has been reported. If an error is on a supervisor module, the supervisor module is rebooted. In case of dual supervisors, a switchover occurs. If an error is on another module, the module is power cycled.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig sw intialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.0(1).
Error Message ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars].Explanation Invalid member type [dec] [chars] received from the API call.
Recommended Action Perform a manual build fabric using fcdomain's interface if you would like to remove the unused virtual domain(s) from the fcdomain list.
Introduced Cisco MDS SAN-OS Release 3.0(1).
XBAR_CLIENT Messages
This section contains the crossbar client (XBAR_CLIENT) messages.
XBAR_CLIENT-2
Error Message XBAR_CLIENT-2-MEM_FULL: Memory allocation failed.Explanation The crossbar client process has failed to allocate memory.
Recommended Action Enter the show xbar-client event-history command or use a similar Fabric Manager/Device manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message XBAR_CLIENT-2-PROC_DN: Process is shutting down: [chars].Explanation The crossbar client process is exiting.
Recommended Action Enter the show xbar-client event-history command or use a similar Fabric Manager/Device manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation The crossbar client process has failed initialization.
Recommended Action Enter the show xbar-client event-history command or use similar Fabric Manager/Device manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
XBAR_CLIENT-3
Error Message XBAR_CLIENT-3-IPC_MSGERR: Error in processing IPC message: [dec], Error code = [dec].Explanation The crossbar client process has encountered an error processing a message.
Recommended Action Enter the show xbar-client event-history command or use a similar Fabric Manager/Device manager procedure to collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message XBAR_CLIENT-3-IPC_MSGUNKN: Received unexpected IPC message: [dec].Explanation The crossbar client process has received an unknown message.
Recommended Action Perform a the show xbar-client event-history command or use a similar Fabric Manager/Device manager procedure o collect more information.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
ZONE Messages
This section contains the zone messages.
ZONE-2
Error Message ZONE-2-LZ_EXITING: LUN/Read-only Zoning Process exited. Reason: [chars].Explanation The LUN read-only zoning process has exited because of the reason shown in the error message . The process restarted automatically.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-LZ_GENERAL_ERROR: [chars].Explanation The LUN read-only zoning process has encountered a critical error. The description of error is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-LZ_INIT_FAILED: Initialization of LUN/Read-only Zoning Process failed at [chars].Explanation Initialization of LUN read-only zoning process failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-LZ_MALLOC_ERROR: Size [dec] bytes.Explanation The LUN read-only zoning process could not allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.2(2a).
Error Message ZONE-2-ZS_ALIAS_LIMIT_EXCEEDED: The limit for maximum number of aliases exceeded.Explanation The number of aliases configured has exceeded the maximum number of aliases allowed per VSAN. Because of this, a distribution or merge operation may fail.
Recommended Action Make sure the number of aliases is less than the maximum allowed in a VSAN.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_ATTR_GROUP_LIMIT_EXCEEDED: The limit for maximum number of attribute groups exceeded.Explanation The number of attribute groups configured has exceeded the maximum number of attribute groups allowed in a VSAN. Because of this, distribution or merge operation may fail.
Recommended Action Make sure the number of attribute groups is less than the maximum allowed in a VSAN.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed : [chars].Explanation The zone server cannot acquire change authorization.
Recommended Action Verify the interoperability mode on all the switches or retry later.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed on VSAN [dec].Explanation The zone server cannot acquire authorization on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failed.Explanation The zone server cannot activate the zone set.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN: Activation failed : reason [chars].Explanation The zone server cannot activate because of reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: Activation failed : reason [chars] domain [dec].Explanation The zone server cannot activate because of reason shown in the error message on the domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_APPLY_FAILED: Apply changed failed on VSAN [dec].Explanation The zone server cannot apply changes on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Dectivation failed.Explanation The zone server cannot deactivate the zone set.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN: Deactivation failed : reason [chars].Explanation The zone server cannot deactivate because of reason shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN_DOM: Deactivation failed : reason [chars] domain [dec].Explanation The zone server cannot deactivate because of reason shown in the error message on the domain.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_RELEASE_AUTH_FAILED: Release authorization failed on VSAN [dec].Explanation The zone server cannot release authorization on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed : [chars].Explanation The zone server cannot stage the zone configuration.
Recommended Action Verify the interoperability mode on all the switches.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_SFC_REJECTED: SFC received from remote domain [dec] is rejected.Explanation Received an invalid SFC from the domain. Either this switch does not understand the frame format, or the remote switch has not acquired the authorization.
Recommended Action Verify the interoperability mode on the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_BY_NAME_FAILED: Stage activate zoneset by name failed on VSAN [dec].Explanation The zone server cannot stage activate zone set by name on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_ENH_FAILED: Stage activate zone set enhanced failed on VSAN [dec].Explanation The zone server cannot stage activate zone set enhanced on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_DEACTIVATE_ZSSET_ENH_FAILED: Stage deactivate zoneset enhanced failed on VSAN [dec].Explanation The zone server cannot stage deactivate zone set enhanced on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_DFLT_ZONE_FAILED: Stage distribute default zone failed on VSAN [dec].Explanation The zone server cannot stage distribute default zone on VSAN [dec].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_ZS_DB_FAILED: Stage distribute zoneset database failed on VSAN [dec].Explanation The zone server cannot stage distribute zone set database on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_MODE_FAILED: Stage set zoning mode failed on VSAN [dec].Explanation The zone server cannot stage set zoning mode on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_POLICIES_FAILED: Stage set zoning policies failed on VSAN [dec].Explanation The zone server cannot stage set zoning policies on the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars].Explanation The database operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failed.Explanation The export or import operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_FC2_OPER_FAILED: FC2 [chars] operation failed : [chars].Explanation The zone server Fibre Channel Layer 2 (FC-2) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Deprecated Cisco MDS SAN-OS Release 3.0(1).
Error Message ZONE-2-ZS_FIPS_COMPLIANCE_FAILURE: FIPS compliance error: consecutively same random numbers.Explanation FIPS compliance error identifying the same random numbers.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message ZONE-2-ZS_INIT_FAILED: [chars].Explanation The zone server initialization failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_LICENSE_UNAVAIL: License:[chars] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs.Explanation License is unavailable. Removing LUN members and read-only attribute and reactivating active zone sets on all affected VSANs.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_LIC_FAILURE: License [chars] operation failed for license [chars].Explanation License operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ZONE-2-ZS_LUN_DISABLING_FAILED: license expiry handling failed for VSAN [dec].Explanation License expiry handling failed for the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ZONE-2-ZS_LUN_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of lun members exceeded.Explanation The number of LUN members configured has exceeded the maximum number of LUN members allowed across all VSANs. Because of this, distribution or merge operation may fail.
Recommended Action Make sure the number of LUN members is less than the maximum allowed across all VSANs.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_MALLOC_FAILURE: Memory allocation failed for size [dec].Explanation Memory allocation failed.
Recommended Action Restart the process.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of members exceeded.Explanation The number of members configured has exceeded the maximum number of members allowed across all VSANs. Because of this, distribution or merge operation may fail.
Recommended Action Make sure the number of members is less than the maximum allowed across all VSANs.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding, Isolating Interface [chars] (VSAN [dec]).Explanation Interface on the VSAN was isolated because the adjacent switch is not responding to zone server requests.
Recommended Action Flap the interface.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_MERGE_FAILED: Zone merge failure, Isolating interface [chars].Explanation Interface isolated because of a zone merge failure.
Recommended Action Compare the active zone set with the adjacent switch by entering the zone merge interface CLI command or by using a similar Fabric Manager/Device Manager procedure.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars].Explanation Full zoning databases are inconsistent between two switches connected by an interface. Databases are not merged.
Recommended Action Compare full zoning database with the adjacent switch. Correct the difference and flap the link.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars].Explanation Full zoning databases are inconsistent between two switches connected by the interface. Databases are not merged.
Recommended Action Compare full zoning database with the adjacent switch, correct the difference and flap the link.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface [chars].Explanation Interface isolated because of an unknown format in the merge request.
Recommended Action Set the interoperability mode to the same value on both switches.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed : [chars].Explanation The zone server messaging and transaction service (MTS) operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failed.Explanation A port swap operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ZONE-2-ZS_PSS_VER_MISMATCH: PSS version mismatch URL: [chars] (expected [chars], got [chars]).Explanation Configuration version mismatch. persistent storage service (PSS) URL expected the shown version, but the stored version is different.
Recommended Action Upgrade or downgrade to the expected version.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_TCAM_BROADCAST_ZONE_DISABLED: Broadcast zoning disabled : Reason: Hard zoning disabled.Explanation Broadcast zoning disabled because hard zoning was disabled because of a ternary content-addressable memory (TCAM) programming failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_TCAM_LUN_ZONING_DISABLED: LUN zoning disabled : Reason: Hard zoning disabled.Explanation LUN zoning disabled because hard zoning disabled because of a ternary content-addressable memory (TCAM) programming failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: TCAM operation failed : [chars], Reason: [chars].Explanation Ternary content-addressable memory (TCAM) programming failure has occurred.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_TCAM_READ_ONLY_ZONE_DISABLED: Read-only zoning disabled : Reason: Hard zoning disabled.Explanation Read-only zoning disabled. Hard zoning disabled because of a ternary content-addressable memory (TCAM) programming failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-2-ZS_TCAM_SWITCHED_TO_SOFT_ZONING_MODE: Switched to soft zoning : Reason: Hard zoning disabled.Explanation Switched to soft zoning. Hard zoning was disabled due to a TCAM programming failure.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message ZONE-2-ZS_VIRTUAL_DOMAIN_INCONSISTENT: IVR reporting virtual domain different from rib and domain manager in vsan [dec].Explanation IVR reporting the virtual domain is different from the Routing Information Base (RIB) and Domain Manager in the VSAN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message ZONE-2-ZS_ZONE_LIMIT_EXCEEDED: The limit for maximum number of zones exceeded.Explanation The number of zones configured has exceeded the maximum number of zones allowed across all VSANs. Because of this, the distribution or merge operation may fail.
Recommended Action Make sure the number of zones is less than the maximum allowed across all VSANs.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
Error Message ZONE-2-ZS_ZONE_SET_LIMIT_EXCEEDED: The limit for maximum number of zonesets exceeded.Explanation The number of zone sets configured has exceeded the maximum number of zone sets allowed across all VSANs. Because of this, distribution or merge operation may fail.
Recommended Action Make sure the number of zone sets is less than the maximum allowed across all VSANs.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
ZONE-3
Error Message ZONE-3-LZ_UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec].Explanation The LUN read-only zoning process has received an unknown message. This information is for debugging only.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-3-ZS_ACTIVATION_FAILED_DUE_TO_QOS_DISABLED: Activation failed due to qos not enabled.Explanation Activation of zone set failed because QoS was not enabled.
Recommended Action Make sure QoS is enabled and reactivate the zone set in the VSAN.
Introduced Cisco MDS SAN-OS Release 2.0(1b).
ZONE-4
Error Message ZONE-4-LZ_OTHER_CMD_TO_ZONED_OUT_LUN: FCP command [hex] received from SID=[chars] to DID=[chars] for LUN=[chars].Explanation The LUN read-only zoning process has received. FCP command received from the source ID to the destination ID for a zoned out LUN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ROZ_WRITE_ACCESS_TO_READ_ONLY_LUN: FCP command [hex] received from SID=[chars] to DID=[chars] for LUN=[chars].Explanation The LUN read-only zoning process has received an FCP command from the source ID to the destination ID for a zoned out LUN.
Explanation No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_BROADCAST_LUN_WARNING: LUN member(s) and Broadcast attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur for LUN members.Explanation Broadcast violations can happen in the named zone in the named VSAN because it has LUN zone members.
Recommended Action No action is required.
Error Message ZONE-4-ZS_CHANGE_LC_UPGRADE_IN_PROGRESS: Change protocol request is received from domain [dec] when linecard upgrade is in progress.Explanation A change request has been received from the domain when a line card upgrade is in progress. The change request is rejected.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_DB_WARNING: [chars].Explanation Database operation warning.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_DOMAIN_MGR_WARNING: Unable to retrieve domain info from domain mgr error: [chars] in vsan [dec].Explanation Unable to retrieve information about a domain from Domain Manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.1(1).
Error Message ZONE-4-ZS_LC_UPGRADE_CHANGE_IN_PROGRESS: Linecard upgrade request is received when change protocol is in progress.Explanation A request for line card upgrade has been received when change protocol is in progress. The line card upgrade will occur after the completion of the change protocol.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_LICENSE_EXPIRY_WARNING: Feature [chars] evaluation license [chars] expiry in [dec] days.Explanation Feature will exceed its evaluation time period in days and will be shut down unless a permanent license is installed.
Recommended Action Install the license file to continue using the feature.
Introduced Cisco MDS SAN-OS Release 1.3(1).
Error Message ZONE-4-ZS_MEMBER_CONVERSION_FAILED: Zone Member conversion failed for zoneset: [chars]. error: [chars].Explanation Zone member conversion has failed in zoneset: [chars] due to error: [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 3.2(1).
Error Message ZONE-4-ZS_NON_INTEROPERABLE_ZONE_SET: Non interoperable active zoneset present on VSAN [dec] in interoperability mode.Explanation Active zone set has non-interoperable members (FC ID, FWWN) when interoperability mode is turned on for the VSAN.
Recommended Action Turn off interoperability mode or make sure that active zone set has only interoperable members (pWWN).
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_QOS_LUN_WARNING: LUN member(s) and QoS attribute are present in zone [chars] in vsan [dec]. QoS will not be applicable for LUN members.Explanation QoS will not be applicable to LUN zone members in zone [chars] in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-4-ZS_TOO_MANY_ALIAS_IN_CURRENT_INTEROP_MODE: Too many aliases in current interoperability mode.Explanation Too many aliases configured in current interoperability mode on the VSAN. Because of this, the next zone set activation, distribution, or merge operation may fail.
Recommended Action Either set the interoperability mode to the appropriate value, or make sure the number of aliases is less than the maximum allowed in the current interoperability mode.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-4-ZS_UNSUPPORTED_MEMBER_IN_CURRENT_INTEROP_MODE: Unsupported member present in active or full zoneset in current interoperability mode.Explanation Active or full zone set has members that are not supported in the current interoperability mode set on the VSAN.
Recommended Action Either set the interoperability mode to the appropriate value, or make sure that the active or full zone set has only supported members in the current interoperability mode.
Introduced Cisco MDS SAN-OS Release 1.3(4a).
ZONE-5
Error Message ZONE-5-ZS_EXPORT_IMPORT_COMPLETE: [chars] operation completed.Explanation The export or import operation completed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-5-ZS_POLICY_CHANGE: Default zoning policy changed to [chars].Explanation Default zoning policy changed to permit or deny.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activated.Explanation Zone set activated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivated.Explanation Zone set deactivated.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
ZONE-6
Error Message ZONE-6-LZ_BECAME_ACTIVE: LUN/Read-only Zoning Process became ACTIVE from Standby mode.Explanation The LUN read-only zoning process on the standby supervisor became active.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_BECAME_STDBY: LUN/Read-only Zoning Process became STANDBY from active mode.Explanation The LUN read-only zoning process became standby from active mode.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_FAILED_TO_SEND_HEARTBEAT: LUN/Read-only zoning process failed to send heartbeat to system manager: Reason=[chars].Explanation The LUN read-only zoning process cannot send a heartbeat to the system manager.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_GENERAL_EVENT: [chars].Explanation The LUN read-only zoning process has generated an important event. The description of the event is shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_INQUIRY_TO_ZONED_OUT_LUN: INQUIRY command received from SID=[chars] to DID=[chars] for LUN=[chars].Explanation The LUN read-only zoning process has received an inquiry FCP command from SID [char.] to DID [char.] for a zoned out LUN [char.].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_REPORT_LUNS_CMD_RCVD: REPORT LUNS command received from SID=[chars] to DID=[chars] for LUN=[chars].Explanation The LUN read-only zoning process has received a report LUNs FCP command from source ID to destination ID for the LUN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_REQUEST_SENSE_TO_ZONED_OUT_LUN: REQUEST SENSE command received from SID=[chars] to DID=[chars] for LUN=[chars].Explanation The LUN read-only zoning process has received a request sense fcp command from source ID to destination ID for the LUN.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_SERVICE_UP: LUN/Read-only Zoning Process initialized [chars].Explanation The LUN read-only zoning process is up. The process was initialized in the mode shown in the error message.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-LZ_SWITCHOVER: LUN/Read-only zoning process switching over to other supervisor.Explanation The LUN read-only zoning process has successfully switched over to the standby supervisor module.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-ZS_CHANGE_ACA_REJECTED: ACA received from remote domain [dec] is rejected.Explanation Received invalid ACA from the domain. Either the domain list does not match or authorization has already been acquired by another switch.
Recommended Action Verify the interoperability mode on the switch.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-ZS_FC2_OPER_INFO: FC2 [chars] operation failed : [chars].Explanation Zone server FC2 operation failed.
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-ZS_INIT_PROCESS: Zone server process started [chars] at [chars].Explanation Zone server process started in [chars] (stateless or stateful) mode at time [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-ZS_INIT_WARNING: [chars].Explanation Warning during zone server initialization: [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Error Message ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars].Explanation Zone server received an event for a known licensing feature: [chars].
Recommended Action No action is required.
Introduced Cisco MDS SAN-OS Release 1.2(2a).