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 session to the FCIP peer closed because the TCP persist timer expired.
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.