System Messages and Recovery Procedures for the Cisco MDS 9000 Family

Table Of Contents

System Messages and Recovery Procedures for the Cisco MDS 9000 Family

AAA Messages

AAA-1

AAA-2

AAA-3

AAA-6

ACL Messages

ACL-2

ACL-4

ACL-5

ACL-6

ACLTCAM Messages

ACLTCAM-2

ACLTCAM-3

ACLTCAM-6

ASCII-CFG Messages

ASCII-CFG-2

BIOS_DAEMON Messages

BIOS_DAEMON-2

BOOTVAR Messages

BOOTVAR-2

BOOTVAR-3

BOOTVAR-5

BOOTVAR-6

CALLHOME Messages

CALLHOME-2

CALLHOME-3

CALLHOME-6

CDP Messages

CDP-2

CDP-3

CDP-6

CERT ENROLL Messages

CFS Messages

CFS-2

CFS-3

CFS-4

CFS-6

CIMSRVPROV Messages

CIMSRVPROV-2

CIMSRVPROV-3

CIMSRVPROV-6

CLOUD Messages

CLOUD-2

CLOUD-3

CLOUD-6

CORE-DMON Messages

CORE-DMON-2

CREDIT MON Messages

DEBUGPROXY Messages

DEBUGPROXY-6

DEVICE-ALIAS Messages

DEVICE-ALIAS-2

DEVICE-ALIAS-3

DEVICE-ALIAS-6

DEV_LOG Messages

DEV_LOG-3

DMM-SLOT# Messages

DMM-SLOT#-5

DPP_DEBUG Messages

DPP_DEBUG-2

DPVM Messages

DPVM-2

DPVM-3

DPVM-4

DPVM-6

DSTATS Messages

DSTATS-2

DSTATS-3

EPP Messages

EPP-5

ETHPORT Messages

ETHPORT-3

ETHPORT-5

EXCEPTIONLOG Messages

EXCEPTIONLOG-SLOT#-2

FC-TUNNEL Messages

FC-TUNNEL-3

FC-TUNNEL-5

FCC Messages

FCC-2

FCC-5

FCC-6

FCC_LC Messages

FCC_LC-2

FCC_LC-5

FCC_LC-6

FCD Messages

FCD-7

FCDD Messages

FCDD-SLOT#-3

FCDD-SLOT#-4

FCDD-SLOT#-5

FCDD-SLOT#-7

FCDD_HELPER Messages

FCDD_HELPER-SLOT#-3

FCDD_HELPER-SLOT#-4

FCDD_HELPER-SLOT#-5

FCDDH Messages

FCDDH-SLOT#-3

FCDDH-SLOT#-4

FCDDH-SLOT#-5

FCDOMAIN Messages

FCDOMAIN-2

FCDOMAIN-3

FCDOMAIN-4

FCDOMAIN-5

FCDOMAIN-6

FCDOMAIN-7

FCFWD Messages

FCFWD-3

FCFWD-4

FCFWD-6

FCMPLS Messages

FCMPLS-2

FCMPLS-3

FCMPLS-5

FCMPLS-6

FCNS Messages

FCNS-2

FCNS-3

FCNS-6

FCS Messages

FCS-2

FCS-3

FCS-4

FCS-5

FCS-6

FCSP-MGR Messages

FCSP-MGR-2

FCSP-MGR-3

FCSP-MGR-6

FDMI Messages

FDMI-2

FDMI-3

FDMI-4

FDMI-6

FEATURE-MGR Messages

FEATURE-MGR-2

FICON Messages

FICON-2

FICON-3

FICON-5

FICON-6

FLOGI Messages

FLOGI-5

FSPF Messages

FSPF-2

FSPF-3

FSPF-4

FSPF-5

FSPF-6

FSPF-7

IKE Messages

IKE-3

IKE-4

IKE-6

ILC_HELPER Messages

ILC_HELPER-2

ILC_HELPER-3

ILC_HELPER-6

ILC-SPAN Messages

ILC-SPAN-3

IMAGE_DNLD Messages

IMAGE_DNLD-SLOT#-2

IMAGE_DNLD-SLOT#-5

IMAGE_UPGRADE Messages

IMAGE_UPGRADE-SLOT#-2

IMAGE_UPGRADE-SLOT#-6

IPACL Messages

IPACL-0

IPACL-1

IPACL-3

IPACL-4

IPACL-5

IPACL-6

IPCONF Messages

IPCONF-2

IPCONF-3

IPCONF-4

IPCONF-6

IPFC Messages

IPFC-2

IPFC-3

IPFC-6

IPS Messages

IPS-2

IPS-3

IPS-4

IPS-5

IPS-7

IPS_SB_MGR Messages

IPS_SB_MGR-SLOT#-2

IPS_SB_MGR-SLOT#-3

IPS_SB_MGR-SLOT#-3

IPS_SB_MGR-SLOT#-6

IPsec Messages

IPsec-2

IPsec-3

IPsec-5

IPsec-6

IPsec-7

ISAPI Messages

ISAPI-SLOT#-0

ISAPI-SLOT#-1

ISAPI-SLOT#-2

ISAPI-SLOT#-3

ISAPI-SLOT#-4

ISAPI-SLOT#-5

ISAPI-SLOT#-6

ISAPI-SLOT#-7

ISNS Messages

ISNS-2

IVR Messages

IVR-2

IVR-3

IVR-4

IVR-5

IVR-6

IVR-7

LC-FCFWD Messages

LC-FCFWD-3

LC-SPAN Messages

LC-SPAN-3

LC_CFG Messages

LC_CFG-SLOT#-2

LC_PORT_CHANNEL Messages

LC_PORT_CHANNEL-SLOT#-0

LC_PORT_CHANNEL-SLOT#-3

LC_PORT_MGR Messages

LC_PORT_MGR-SLOT#-2

LC_RDL Messages

LC_RDL-3

LC_RDL-6

LICMGR Messages

LICMGR-2

LICMGR-3

LICMGR-6

MAC Messages

MAC-SLOT#-2

MCAST Messages

MCAST-2

MCAST-4

MCAST-5

MODULE Messages

MODULE-2

MODULE-3

MODULE-4

MODULE-5

MODULE-6

NASB Messages

NASB-SLOT#-5

NPC Messages

NPC-SLOT#-3

NPC-SLOT#-4

NPC-SLOT#-5

NPV Messages

NPV-2

NPV-3

NPV-5

NPV-6

NTP Messages

NTP-2

NTP-3

NTP-6

NVP Messages

NVP-6

NVP-SLOT# Messages

NVP-SLOT#-2

PLATFORM Messages

PLATFORM-0

PLATFORM-1

PLATFORM-2

PLATFORM-3

PLATFORM-4

PLATFORM-5

PLATFORM-7

PLOG Messages

PLOG-4

PLOG_SUP Messages

PLOG_SUP-4

PORT Messages

PORT-3

PORT-5

PORT-Resources Messages

PORT-SECURITY Messages (Deprecated)

PORT-SECURITY-2

PORT-SECURITY-3

PORT-SECURITY-4

PORT-SECURITY-6

PORT_CHANNEL Messages

PORT_CHANNEL-1

PORT_CHANNEL-2

PORT_CHANNEL-3

PORT_CHANNEL-4

PORT_CHANNEL-5

PORT_CHANNEL-6

PORT_CHANNEL-7

PORT_SECURITY Messages

PORT_SECURITY-2

PROC_MGR Messages

PROC_MGR-SLOT#-2

PROC_MGR-SLOT#-4

PSS Messages

PSS-0

PSS-1

PSS-2

PSS-4

PSS-5

QOS Messages

QOS-2

QOS-3

QOS-4

QOS-6

RADIUS Messages

RADIUS-2

RADIUS-3

RADIUS-6

RDL Messages

RDL-3

RDL-6

RIB Messages

RIB-0

RIB-1

RIB-2

RIB-3

RIB-4

RIB-5

RIB-6

RLIR Messages

RLIR-2

RLIR-6

RM Messages

RM-6

RM-SLOT# Messages

RM-SLOT#-2

RSCN Messages

RSCN-2

RSCN-4

RSCN-6

SAN_EXT_TUNER Messages

SAN_EXT_TUNER-3

SCHEDULER Messages

SCHEDULER-2

SCHEDULER-3

SCHEDULER-4

SCHEDULER-6

SCSI target Messages

SCSI target-2

SCSI target-3

SCSI target-7

SAN Device Virtualization Messages

SDV-6

SECURITYD Messages

SECURITYD-2

SECURITYD-3

SECURITYD-6

SENSOR Messages

SENSOR-2

SENSOR-3

SENSOR-5

SENSOR_USD Messages

SENSOR_USD-2

SENSOR_USD-3

SENSOR_USD-5

SFC Messages

SFC-3

SFM Messages

SFM-2

SFM-6

SME_CPP Messages

SME_CPP-2

SME_CPP-3

SME_CPP-4

SME_CPP-5

SME_CPP-SLOT#-2

SME_CPP-SLOT#-3

SKSD Message

SPAN Messages

SPAN-2

SPAN-3

SPAN-5

SPAN-6

SPI Messages

SPI_SLOT#-2

SVC Messages

SVC-0

SVC-1

SVC-2

SVC-3

SVC-4

SVC-5

SVC-6

SVC-7

SVC_BATTERY Messages

SVC_BATTERY-SLOT#-2

SVC_BATTERY-SLOT#-4

SVC_BATTERY-SLOT#-6

SYSMGR Messages

SYSMGR-2

SYSMGR-3

SYSMGR-4

SYSMGR-5

SYSMGR-6

SYSMGR-7

SYSTEMHEALTH Messages

SYSTEMHEALTH-2

SYSTEMHEALTH-4

SYSTEMHEALTH-5

SYSTEMHEALTH-6

TACACS Messages

TACACS-2

TACACS-3

TACACS-6

TCAP Messages

TCAP-2

TLPORT Messages

TLPORT-2

TLPORT-3

TLPORT-6

TLPORT-6

TP C Messages

TTYD Messages

TTYD-2

TTYD-3

TTYD-6

VEC Messages

VEC-SLOT#-3

VEC-SLOT#-4

VEC-SLOT#-5

VEDB_MGR Messages

VEDB_MGR-2

VEDB_MGR-6

VES Messages

VES-SLOT#-4

VES-SLOT#-5

VFC Messages

VFC-3

VHBAD Messages

VHBAD-2

VHBAD-3

VHBAD-7

VNI Messages

VNI-2

VNI-3

VNI-6

VOMD-SLOT Messages

VOMD-SLOT-2

VPM Messages

VPM-2

VPM-3

VPM-4

VPM-6

VPM-SLOT# Messages

VPM-SLOT#-2

VRRP_CFG Messages

VRRP_CFG-2

VRRP_CFG-3

VRRP_CFG-5

VRRP_CFG-6

VRRP_ENG Messages

VRRP_ENG-2

VRRP_ENG-3

VRRP_ENG-4

VRRP_ENG-5

VRRP_ENG-6

VSAN Messages

VSAN-2

VSAN-3

VSAN-6

VSHD Messages

VSHD-2

VSHD-3

VSHD-4

VSHD-5

VSHD-7

WWN Messages

WWN-1

WWN-2

WWN-3

WWN-4

WWN-5

WWN-6

WWN-7

XBAR Messages

XBAR-3

XBAR-5

XBAR_CLIENT Messages

XBAR_CLIENT-2

XBAR_CLIENT-3

ZONE Messages

ZONE-2

ZONE-3

ZONE-4

ZONE-5

ZONE-6


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:

AAA Messages

ACL Messages

ACLTCAM Messages

ASCII-CFG Messages

BIOS_DAEMON Messages

BOOTVAR Messages

CALLHOME Messages

CDP Messages

CERT ENROLL Messages

CFS Messages

CIMSRVPROV Messages

CLOUD Messages

CORE-DMON Messages

CREDIT MON Messages

DEBUGPROXY Messages

DEVICE-ALIAS Messages

DEV_LOG Messages

DMM-SLOT# Messages

DPVM Messages

DSTATS Messages

EPP Messages

ETHPORT Messages

EXCEPTIONLOG Messages

FC-TUNNEL Messages

FCC Messages

FCC_LC Messages

FCD Messages

FCDD Messages

FCDD_HELPER Messages

FCDDH Messages

FCDOMAIN Messages

FCFWD Messages

FCMPLS Messages

FCNS Messages

FCS Messages

FCSP-MGR Messages

FDMI Messages

FEATURE-MGR Messages

FICON Messages

FLOGI Messages

FSPF Messages

IKE Messages

ILC_HELPER Messages

ILC-SPAN Messages

IMAGE_DNLD Messages

IMAGE_UPGRADE Messages

IPACL Messages

IPCONF Messages

IPFC Messages

IPS Messages

IPS_SB_MGR Messages

IPsec Messages

ISAPI Messages

ISNS Messages

IVR Messages

LC-SPAN Messages

LC_CFG Messages

LC_PORT_CHANNEL Messages

LC_PORT_MGR Messages

LC_RDL Messages

LICMGR Messages

MAC Messages

MODULE Messages

NASB Messages

NPC Messages

NPV Messages

NTP Messages

NVP Messages

NVP-SLOT# Messages

PLATFORM Messages

PLOG Messages

PLOG_SUP Messages

PORT Messages

PORT-SECURITY Messages (Deprecated)

PORT_CHANNEL Messages

PORT_SECURITY Messages

PROC_MGR Messages

PSS Messages

QOS Messages

RADIUS Messages

RDL Messages

RIB Messages

RLIR Messages

RM Messages

RM-SLOT# Messages

RSCN Messages

SAN_EXT_TUNER Messages

SCHEDULER Messages

SCSI target Messages

SAN Device Virtualization Messages

SECURITYD Messages

SENSOR Messages

SFC Messages

SFM Messages

SME_CPP Messages

SKSD Message

SPAN Messages

SPI Messages

SVC_BATTERY Messages

SYSMGR Messages

SYSTEMHEALTH Messages

TACACS Messages

TCAP Messages

TLPORT Messages

TP C Messages

TTYD Messages

VEC Messages

VEDB_MGR Messages

VES Messages

VFC Messages

VHBAD Messages

VNI Messages

VOMD-SLOT Messages

VPM Messages

VPM-SLOT# Messages

VRRP_CFG Messages

VRRP_ENG Messages

VSAN Messages

VSHD Messages

WWN Messages

XBAR Messages

XBAR_CLIENT Messages

ZONE Messages

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 
protected 

Explanation    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 protected 

Explanation    The BIOS on the module is write protected.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_PRI_BOOT_FAIL: Primary BIOS is 
corrupted or un-bootable. 

Explanation    The primary BIOS on a module is corrupted.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

BOOTVAR Messages

This section contains the boot variable (BOOTVAR) messages.

BOOTVAR-2

Error Message     BOOTVAR-2-ALLOC_MEMORY: Memory allocation failed. 

Explanation    The service failed to allocate memory.

Recommended Action    Check to see if the switch is low on memory and reset the switch if it is low.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-2-AUTOSYNC_FAILED: Image autosync failed. Reason: [chars] 
([hex]). 

Explanation    The image synchronization has failed.

Recommended Action    Ensure that there is enough space on the flash. Verify the system high availability status.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-2-CONFIG_ERROR: Failed to update boot configuration. 

Explanation    An error has occurred during the update of the boot configuration files.

Recommended Action    Ensure that there is enough space on the flash. Enter the show boot CLI command to check the configured image names, and enter show loader internal configuration to compare them with the current bootloader configuration. If they are not coherent, enter the write erase CLI command and try to save the configuration again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-2-IMAGE_NOT_COMPATIBLE: Warning: image [chars] is not 
compatible with the current platform in Sup [dec]. 

Explanation    The input image name is not compatible with the current platform.

Recommended Action    Make sure a correct image is specified before rebooting the system.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

BOOTVAR-3

Error Message     BOOTVAR-3-AUTOCOPY_FAILED: Autocopy of file [chars] to standby 
failed, error=[hex]. 

Explanation    The automatic copy feature failed to copy the image shown to the standby module.

Recommended Action    Check the error ID for the specified reason.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    BOOTVAR-3-AUTOCOPY_FAILED_STANDBY_FULL: Autocopy of file [chars] to 
standby failed due to not enough disk space on standby. 

Explanation    There is not enough disk space on the standby supervisor for the file to be copied.

Recommended Action    Clear space on the standby supervisor.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    BOOTVAR-3-INIT_FAILED: Initialization failed: Component [chars]. 

Explanation    The service failed to start. The failure occurred during initialization of the component shown in the error message.

Explanation    Enter the show process CLI command to check the status of the other processes. Check the component shown in the error message. You can alternatively use Fabric Manager and Device Manager instead of the command line interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-3-LOAD_VERIFY_LIB_FAILED: Fetching library [chars] failed, 
reason=[chars]. 

Explanation    The boot variable verification library specified failed to load.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    BOOTVAR-3-MODULE_LOCK_FAIL: Unable to get module lock, please don't 
reload <error-id:[hex]

Explanation    Unable to acquire modlock to prevent user to reload during auto-sync.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated    Cisco MDS SAN-OS Release 3.0(1).

Error Message    BOOTVAR-3-NEIGHBOR_REJECT_AUTOCOPY: auto-copy failed - not supported 
by neighbor supervisor. 

Explanation    The standby supervisor does not support automatic copy. This automatic copy attempt has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-3-VERIFY_FAILED: Image [chars] for bootvar [chars] 
verification failed, reason=[chars]. 

Explanation    The image set for this boot variable has failed the verification process. This is just a warning.

Recommended Action    Check the reason shown in the error message to determine what action to take.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

BOOTVAR-5

Error Message     BOOTVAR-5-AUTOCOPY_SUCCEED: auto-copy of file [chars] to standby 
supervisor succeed. 

Explanation    Automatic copy of the file succeeded. Image integrity was verified by the standby supervisor.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-5-AUTOCOPY_VERIFY_SEND_FAILED: Unable to ask standby to 
verify file [chars], error = [hex]. 

Explanation    After copying the image to the standby supervisor, the active supervisor failed to verify the integrity of that image on the standby supervisor.

Recommended Action    Turn auto-copy off and back on.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-5-AUTOSYNC_DONE: Image autosync done. 

Explanation    The image synchronization was done successfully.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-5-AUTOSYNC_REBOOT: Rebooting standby after successful 
autosync. 

Explanation    Image automatic synchronization was successful. The system is resetting the standby supervisor to load the new image.

Recommended Action    Verify that the standby supervisor reloads correctly.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-5-AUTOSYNC_START: Starting image autosync. Please wait until 
completion. 

Explanation    The standby supervisor has requested a synchronization of the current image.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    BOOTVAR-5-IMAGE_NOTEXISTS: Warning: image [chars] doesn't exist on 
sup[dec]. 

Explanation    The input image name does not exist on the specified supervisor.

Recommended Action    Check whether the input image name you entered exists and make sure that you have the image on the flash before reboot.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by opposing 
supervisor, starting... 

Explanation    The standby supervisor supports automatic copy. Automatic copy has started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

BOOTVAR-6

Error Message     BOOTVAR-6-ALREADY_IN_SYNC: Image already in sync. 

Explanation    No need to update the image on the standby supervisor.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-6-CONFIG_UPDATED: Boot configuration updated. 

Explanation    The boot-loader configuration files have been successfully updated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     BOOTVAR-6-STARTING: Boot configuration initialized. 

Explanation    The service has successfully started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

CALLHOME Messages

This section contains the Call Home (CALLHOME) messages.

CALLHOME-2

Error Message     CALLHOME-2-EVENT: [chars]. 

Explanation    A Call Home event occurred.

Recommended Action    If you have configured your e-mail address to receive Call Home notifications, check your e-mail for more details about this Call Home event. If Call Home was not enabled, use either CLI commands or Cisco Fabric Manager procedures to get more information about the error.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CALLHOME-2-PROGRAM_EXIT: callhome process ending: [chars]. 

Explanation    Call Home process is exiting because of the reason shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CALLHOME-3

Error Message    CALLHOME-3-CALLHOME_CFS_MERGE_OPERATION_FAILED: [chars]. 

Explanation    A Call Home merge operation failed.

Recommended Action    Check the reason for the failure of the CFS operation and rectify the problem.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    CALLHOME-3-CALLHOME_CFS_OPERATION_FAILED: [chars] : [chars]. 

Explanation    The Call Home operation using Cisco Fabric Services (CFS) failed because of the reason shown in the error message.

Recommended Action    Check the reason for the failure of the CFS operation and rectify the problem.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CALLHOME-3-CALLHOME_MAX_ALERT_MSG: [chars]. 

Explanation    A Call Home alert occurred.

Recommended Action    Check the reason listed for the Call Home message and rectify the problem.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CALLHOME-3-EVENT_PROCESS_ERROR: error in processing callhome event 
[chars] reason:[chars]. 

Explanation    An error occurred in processing the Call Home event because of the reason shown in the error message.

Recommended Action    Verify your Call Home configuration for proper configuration. Verify the SMTP server address, verify e-mail addresses for destination profiles, and enable status of Call Home. Enter the show callhome CLI command to display the configuration. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Error Message     CALLHOME-3-MESSAGE_SIZE_EXCEED: message size for callhome 
alert:[chars] exceeds maximum limit for destination profile:[chars]. 

Explanation    The message size for the Call Home alert exceeds the maximum limit for the destination profile shown in the error message.

Recommended Action    Verify the maximum message size for the destination profile under question. Increase it, if possible, to match the maximum limit allowed by your e-mail destinations.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CALLHOME-6

Error Message    CALLHOME-6-NONCRIT_EVENT: [chars]. 

Explanation    A noncritical Call Home event occurred.

Recommended Action    If you have configured your e-mail address to receive Call Home notifications, check your e-mail for more details about this Call Home event. If Call Home was not enabled, use either CLI commands or Fabric Manager procedures to get more information about the error.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CDP Messages

This section contains the Cisco Discovery Protocol (CDP) messages.

CDP-2

Error Message     CDP-2-INITFAIL: CDP Daemon Initialization failed: [chars]. 

Explanation    The Cisco Discovery Protocol daemon initialization failed because of the reason shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CDP-3

Error Message     CDP-3-ALLOCFAIL: Heap Memory allocation failed: [chars]. 

Explanation    The Cisco Discovery Protocol daemon is out of dynamic memory. The error message shows the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-GENERROR: [chars]. 

Explanation    The Cisco Discovery Protocol daemon encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-MCASTBINDFAIL: Failed to bind for CDP multicast address on 
interface [hex] - [chars]. 

Explanation    An attempt to register for packets destined to the Cisco Discovery Protocol multicast address failed. The error message identifies the interface and the reason for the failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-MTSERROR: [chars]. 

Explanation    The Cisco Discovery Protocol daemon encountered a messaging and transaction service (MTS) error. The error message shows the context where the error occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-PKTRECVFAIL: Failed to receive packet - [chars]. 

Explanation    Failed to receive a packet because of the reason shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-PKTSENDFAIL: Failed to send packet, interface [hex] - [chars]. 

Explanation    Failed to send a packet. The error message identifies the interface and the reason for this failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-PSSERROR: [chars]. 

Explanation    The Cisco Discovery Protocol daemon encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-SOCKBINDFAIL: Failed to bind to raw socket, interface [hex] - 
[chars]. 

Explanation    The Cisco Discovery Protocol failed to bind to a raw socket. The error message identifies the interface and the reason for this failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-3-SOCKOPENFAIL: Failed to open socket for receiving raw 802_2 
packets - [chars]. 

Explanation    An attempt to open a socket for receiving raw 802.2 packets failed due to the reason shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CDP-6

Error Message     CDP-6-CDPDUP: CDP Daemon Up. 

Explanation    The Cisco Discovery Protocol daemon was created successfully and is up and running.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-6-CDPEXIT: CDP daemon shutting down gracefully. 

Explanation    The Cisco Discovery Protocol daemon is shutting down gracefully.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-6-PORTDISABLE: CDP disabled on port [chars]. 

Explanation    The Cisco Discovery Protocol was disabled on a port. The error message shows the Interface-ID string that identifies the port.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-6-PORTDOWN: A CDP enabled port [chars] went down. 

Explanation    A Cisco Discovery Protocol enabled port became unoperational. The error message shows the Interface-ID string that identifies the port.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-6-PORTENABLE: CDP enabled on port [chars]. 

Explanation    The Cisco Discovery Protocol was enabled on a port. The error message shows the Interface-ID string that identifies the port.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CDP-6-PORTUP: A CDP enabled port [chars] came up. 

Explanation    A Cisco Discovery Protocol enabled port became operational. The error message shows the Interface-ID string that identifies the port.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CERT ENROLL Messages

Error Message    CERT_ENROLL-2-CERT_EN_PROGRAM_EXIT: cert_enroll daemon exiting: 
[chars]. 

Explanation    The process is responsible for digital certificate enrollment exited.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     CERT_ENROLL-3-CERT_EN_ERROR_MESSAGE: [chars]. 

Explanation    The digital certificate enrollment process generated an error message.

Recommended Action    Review the error in the message to determine the next steps.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    CERT_ENROLL-3-CERT_EN_FIPS_MODE_INIT_ERROR: Could not initialize FIPS 
mode : [chars]. 

Explanation    FIPS mode initialization error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    CERT_ENROLL-6-CERT_EN_MESSAGE: [chars]. 

Explanation    The digital certificate enrollment process generated an informational message.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

CFS Messages

This section contains the Cisco Fabric Services (CFS) messages.

CFS-2

Error Message    CFS-2-MTS_REJECT: Verification failed reject MTS message SAP 
[dec]:RR-token [hex]. 

Explanation    This MTS message could have been posted by the previous active running pre 3.x; MTS structure has changed since then hence ignore the MTS message, Source SAP [dec]; RR-token [hex].

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.2(1).

Error Message    CFS-2-CFS_REJECT: CFS reject: [chars]: Switch WWN [chars], reason 
[chars]. 

Explanation    When Cisco Fabric Service (CFS) receives a malformed CFS packet from a switch with WWN and IP address shown in the error message, then CFS rejects the packet.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CFS-2-EXITING: Exit reason: [chars]. 

Explanation    The Cisco Fabric Services process has exited because of the error shown in the error message. The process will be restarted automatically.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-2-GENERAL_ERROR: [chars]. 

Explanation    The Cisco Fabric Services process has encountered a critical error. The description of error is shown in the error message.

Recommended Action    Refer to the listed error and take action as required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-2-INITFAIL: CFS Service Init failed: [chars]. 

Explanation    The Cisco Fabric Services initialization failed. The error message explains the reason for the failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CFS-2-LOCK_FAILED: lock failed for sap [dec] due to internal error.

Explanation    Lock failed because the unrestricted and uncoordinated count is not zero for an application with the service access point (SAP) shown in error message.

Recommended Action    To recover from this state, use the cfs internal decrement-unrestricted <app-sap> CLI command.

Introduced Cisco MDS SAN-OS Release 3.0(2a).

Error Message    CFS-2-MALLOC_ERROR: Size [dec] bytes. 

Explanation    The Cisco Fabric Services could not allocate memory.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-2-PSS_ERROR: [chars]: PSS ret. val=[dec]. 

Explanation    The Cisco Fabric Services encountered an error while operating on a persistent storage database.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

CFS-3

Error Message    CFS-3-ALLOCFAIL: Heap Memory allocation failed: [chars]. 

Explanation    The Cisco Fabric Services process is out of dynamic memory. The error message specifies the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CFS-3-FIPS_TEST_FAILED: FIPS compliance test failed. 

Explanation    A FIPS compliance test failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    CFS-3-MERGE_FAILED: Merge failed for app [chars], local switch wwn 
[chars],ip [chars], remote switch wwn [chars], ip [chars]. 

Explanation    The Cisco Fabric Services has detected a merge failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-CFS_PSS_CORRUPTED: [chars] PSS found corrupted. 

Explanation    The Cisco Fabric Services detected corruption in one of its persistent information databases. The database will be recreated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-DBERROR: [chars]. 

Explanation    The Cisco Fabric Services encountered a database error. The error message specifies the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-FAILURE_RESPONSE: [chars] [hex]. 

Explanation    The Cisco Fabric Services failed to get a response. The error message shows the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-GENERROR: [chars]. 

Explanation    The Cisco Fabric Services encountered a general error, one that does not fall in any of the above categories. The error message describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-LICERR: [chars]. 

Explanation    The Cisco Fabric Services failed to get a license.

Recommended Action    Install a license.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-MTSERROR: [chars]. 

Explanation    The Cisco Fabric Services encountered a messaging and transaction service (MTS) error. The error message specifies the context where the error occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-PSSERROR: [chars]. 

Explanation    The Cisco Fabric Services encountered a persistent storage service (PSS) error. The error message specifies the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-TIMEOUT_ERROR: [chars] [hex]. 

Explanation    The Cisco Fabric Services encountered a timeout. The error message shows the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]. 

Explanation    The Cisco Fabric Services received an unknown message from a node. This information is for debugging only.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

CFS-4

Error Message     CFS-4-LICEXP: [chars]. 

Explanation    The Cisco Fabric Services license is going to expire. The error message shows the expiration time.

Recommended Action    Install a license.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]. 

Explanation    There was a version mismatch between the Cisco Fabric Services and one of its persistent storage databases. The persistent information has been translated to the new format.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

CFS-6

Error Message     CFS-6-BECAME_ACTIVE: Became ACTIVE from standby mode. 

Explanation    The Cisco Fabric Services on the standby supervisor became active and it is ready to serve client requests.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-BECAME_STDBY: Became STANDBY from active mode. 

Explanation    The Cisco Fabric Services changed to standby mode from active mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-EXCESSIVE_DELAY: [chars]. 

Explanation    A processing event took an excessive amount of time. The description of the event is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system 
manager: Reason=[chars]. 

Explanation    The Cisco Fabric Services failed to send a heartbeat message to the system manager.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-GENERAL_EVENT: [chars]. 

Explanation    The Cisco Fabric Services generated an event. The description of the event is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CFS-6-LOGICAL_DISTRIBUTION_INFO: vsan [dec], source wwn [chars], ip 
[chars] app-id [dec], session-id [dec], user [chars], [chars]. 

Explanation    This is an information message that is logged during different stages for coordinated distribution of an application with the application ID shown in the error message (logical scope). Different stages are LOCK_ACQUIRED, LOCK_RELEASED, LOCK_CLEAR, and COMMIT which are shown at the end of the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    CFS-6-PHYSICAL_DISTRIBUTION_INFO: source wwn [chars], ip [chars], 
app-id [dec], session-id [dec], user [chars], [chars]. 

Explanation    This is an information message that is logged during different stages for coordinated distribution of an application with the application ID shown in the error message (physical scope). Different stages are LOCK_ACQUIRED, LOCK_RELEASED, LOCK_CLEAR, and COMMIT which are shown at the end of the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    CFS-6-PSS_CREATED: [chars] PSS Created. 

Explanation    A persistent information database for the Cisco Fabric Services has been recreated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-PSS_DESTROYED: [chars] PSS Destroyed. 

Explanation    A persistent information database for Cisco Fabric Services has been deleted and will be recreated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    CFS-6-REGION_CTX_REMOVED: Region info is deleted for [chars]. 

Explanation    [chars] is in logical scope. Regions are supported only physical scope applications.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    CFS-6-SERVICE_UP: Initialized [chars]. 

Explanation    The Cisco Fabric Services process is up and ready to accept client requests. The process was initialized in the mode shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-SRVCREATED: CFS Service created. 

Explanation    The Cisco Fabric Services process was created successfully and is up and running.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-SRVEXIT: CFS Service shutting down gracefully. 

Explanation    The Cisco Fabric Services process is shutting down gracefully.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     CFS-6-SWITCHOVER: Switching Over to other Sup. 

Explanation    The Cisco Fabric Services successfully switched over to the standby supervisor.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

CIMSRVPROV Messages

This section contains the Common Information Model (CIM) server (CIMSRVPROV) messages.

CIMSRVPROV-2

Error Message     CIMSRVPROV-2-CIM_SYSLOG_EXIT: Message:[chars] errcode:[dec]. 

Explanation    The CIM server exited because of a critical error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-2-CIM_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] 
Destination URI:[chars] errcode:[dec]. 

Explanation    A persistent storage service (PSS) snapshot error occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-2-CIM_SYSLOG_SDWRAP_ERR: Description:[chars] 
errcode:[dec]. 

Explanation    The CIM server experienced a debug infrastructure error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

CIMSRVPROV-3

Error Message     CIMSRVPROV-3-CIM_SYSLOG_COPY_CONFIG_ERR: Message:[chars] URI:[chars] 
errcode:[dec]. 

Explanation    The CIM server experienced a copy running startup error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-3-CIM_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] 
errcode:[dec]. 

Explanation    The CIM server experienced a file handling error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-3-CIM_SYSLOG_MTS_ERR: message [chars]. 

Explanation    The CIM server experienced a messaging and transaction service (MTS) message handling error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-3-CIM_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] 
errcode:[dec]. 

Explanation    The CIM server experienced a persistent storage service (PSS) handling error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

CIMSRVPROV-6

Error Message     CIMSRVPROV-6-LOG_CIM_CERTIFICATE_CLEARED: Cleared certificate 
[chars]. 

Explanation    The CIM server experienced a cleared a certificate named in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     CIMSRVPROV-6-LOG_CIM_CERTIFICATE_INSTALLED: Installed certificate 
[chars]. 

Explanation    The CIM server installed a certificate named in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

CLOUD Messages

CLOUD-2

Error Message    CLOUD-2-PROGRAM_EXIT: cloud-discovery process ending: [chars]. 

Explanation    Cloud-discovery process is exiting for the reason stated.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

CLOUD-3

Error Message    CLOUD-3-CLOUD_CFS_MERGE_OPERATION_FAILED: [chars]. 

Explanation    CFS merge failed.

Recommended Action    Check the message for the reason for failure of the CFS operation and rectify the problem.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     CLOUD-3-CLOUD_CFS_OPERATION_FAILED: [chars] : [chars]. 

Explanation    CFS operation failed.

Recommended Action    Check the message for the reason for failure of the CFS operation and rectify the problem.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     CLOUD-3-CLOUD_FEATURE_MANAGER_ERROR: [chars] : [chars]. 

Explanation    iSLB manager experienced an error.

Recommended Action    Check the message for the reason for failure of the CFS operation and rectify the problem.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     CLOUD-3-CLOUD_PSS_OPERATION_FAILED: [chars] : [chars]. 

Explanation    PSS operation failed

Recommended Action    Check the message for the reason for failure of the CFS operation and rectify the problem.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

CLOUD-6

Error Message     CLOUD-6-CLOUD_DISCOVERY_DONE: discovery over. 

Explanation    Cloud-discovery started.

Recommended Action    Check the cloud membership.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     CLOUD-6-CLOUD_DISCOVERY_STARTED:  [chars] discovery started. 

Explanation    Cloud-discovery started.

Get more information using the cloud-discovery status CLI command. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

CORE-DMON Messages

This section contains the core dump daemon (CORE-DMON) messages.

CORE-DMON-2

Error Message     CORE-DMON-2-MODULE_COREDUMP_DONE: kernel coredump completed on 
module:[dec]. 

Explanation    Kernel core dump finished on the module shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     CORE-DMON-2-MODULE_COREDUMP_STARTED: kernel coredump started on 
module:[dec]. 

Explanation    Kernel core dump started on the module shown in the error message. Another system message will be generated when this task completes.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

CREDIT MON Messages

Error Message    CREDITMON-SLOT#-2-SYSERR_CREDITMON_APP_EXITED: [chars]. 

Explanation    Credit Monitor application exited.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    CREDITMON-SLOT#-2-SYSERR_CREDITMON_MTS_INIT_ERR: [chars]. 

Explanation    Credit Monitor error binding to MTS.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

DEBUGPROXY Messages

This section contains the debug proxy (DEBUGPROXY) messages.

DEBUGPROXY-6

Error Message     DEBUGPROXY-6-ILC_DEBUG_PROXY_COMMON: ilc debug proxy [chars] [dec]. 

Explanation    General intelligent line card (ILC) debug proxy information.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    DEBUGPROXY-6-SSM_DEBUG_PROXY_COMMON: SSM debug proxy [chars] [dec]. 

Explanation    General Storage Services Module (SSM) debug proxy information.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

DEVICE-ALIAS Messages

This section contains the device alias (DEVICE-ALIAS) messages.

DEVICE-ALIAS-2

Error Message    DEVICE-ALIAS-2-ALLOC_FAILED: Memory allocation failed for size:[dec] 
type:[dec]. 

Explanation    Memory allocation failed for the size and type of memory shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DEVICE-ALIAS-2-INIT_FAILED: [chars]. 

Explanation    An error occurred during initialization because of the reason shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DEVICE-ALIAS-3

Error Message    DEVICE-ALIAS-3-CFS_OPER_FAILED: [chars]. 

Explanation    An error occurred while performing a Cisco Fabric Services (CFS) operation. The error message indicates the CFS operation and the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DEVICE-ALIAS-3-CLEAR_FAILED: [chars]. 

Explanation    An error occurred while clearing the session. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DEVICE-ALIAS-3-COMMIT_FAILED: [chars]. 

Explanation    An error occurred while committing the database. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-COMMIT_REJECTED: [chars]. 

Explanation    Commit request received from a remote switch was rejected. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DEVICE-ALIAS-3-LOCK_FAILED: [chars]. 

Explanation    An error occurred while acquiring the lock. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-LOCK_REJECTED: [chars]. 

Explanation    Lock request received from a remote switch is rejected. The error message indicates the reason for the failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-MERGE_ACTIVATION_FAILED: [chars]. 

Explanation    An error occurred while activating the merged database. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-MERGE_ACTIVATION_REJECTED: [chars]. 

Explanation    An activation request received from a remote switch is rejected. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-MERGE_FAILED: [chars]. 

Explanation    An error occurred during a merge operation. The error message indicates the reason for failure.

Recommended Action    Compare the device-alias database with the other switches in the fabric. Resolve any conflicts and commit the changes.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-MTS_OPER_FAILED: [chars]. 

Explanation    An error occurred during a messaging and transaction service (MTS) operation. The error message indicates the messaging and transaction service (MTS) operation and the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-PSS_OPER_FAILED: [chars]. 

Explanation    An error occurred during a persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation and the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-UNLOCK_FAILED: [chars]. 

Explanation    An error occurred while releasing the lock. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-3-UNLOCK_REJECTED: [chars]. 

Explanation    An unlock request received from a remote switch is rejected. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DEVICE-ALIAS-6

Error Message     DEVICE-ALIAS-6-CLEAR_FAILED_INFO: [chars]. 

Explanation    An error occurred while clearing the session. The error message indicates the additional information regarding failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-COMMIT_FAILED_INFO: [chars]. 

Explanation    An error occurred while committing the database. The error message indicates the additional information regarding failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-IMPORT_DEFINITION_CONFLICT: Fcalias [chars] could not 
be imported due to definition conflict. 

Explanation    The fcalias shown could not be imported because of a definition conflict. Either there is already a device-alias configuration present with the same definition, or another VSAN specified in the import VSAN range has an fcalias with the same definition.

Recommended Action    Resolve the conflict and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-IMPORT_MEMBER_TYPE_CONFLICT: Fcalias [chars] could not 
be imported due to having unsupported member type. 

Explanation    The fcalias shown in the error message could not be imported because of unsupported member types. The fcalias can be imported only if it has port WWN based members.

Recommended Action    Make sure that the fcalias has port WWN based members and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-IMPORT_NAME_CONFLICT: Fcalias [chars] could not be 
imported due to name conflict. 

Explanation    The fcalias shown could not be imported because of a name conflict. Either there is already a device-alias configuration present with the same name, or another VSAN specified in the import VSAN range has an fcalias with the same name.

Recommended Action    Resolve the conflict and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-IMPORT_NUM_MEMBERS_CONFLICT: Fcalias [chars] could not 
be imported due to having unsupported number of members. 

Explanation    The fcalias listed could not be imported because of an unsupported number of members. The fcalias can be imported only if it has exactly one member.

Recommended Action    Make sure that the fcalias has exactly one member and issue the import command again. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-LOCK_FAILED_INFO: [chars]. 

Explanation    An error occurred while acquiring the lock. The error message indicates the additional information regarding failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DEVICE-ALIAS-6-MERGE_ACTIVATION_FAILED_INFO: [chars]. 

Explanation    An error occurred while activating the merged database. The error message indicates the additional information regarding failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DEVICE-ALIAS-6-UNLOCK_FAILED_INFO: [chars]. 

Explanation    An error occurred while releasing the lock.The error message shows additional information regarding failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DEV_LOG Messages

This section contains the DEV_LOG messages.

DEV_LOG-3

Error Message    DEV_LOG-3-ERROR: [chars]

Explanation    Dev_log_lc encountered an error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

DMM-SLOT# Messages

DMM-SLOT#-5

Error Message    DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_SRVR_ZONE: Job Id:%Ld VSAN :[dec] 
New N-Port FCID :[hex] Server FCID:[hex] are in the same zone. ALERT!!. 

Explanation    A new N port has come up, which is zoned in the same zone as the server.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_STG_ZONE: Job Id:%Ld VSAN :[dec] New 
N-Port FCID :[hex] Storage FCID:[hex] are in the same zone. ALERT!!. 

Explanation    A new N port has come up, which is zoned in the same zone as the storage.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_ERR_DMM_SRVR_RSCN: Job Id:%Ld Server N-Port pWWN:0x%Lx 
[chars]. 

Explanation    An RSCN event was received for the server associated with a job.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_ERR_DMM_STG_RSCN: Job Id:%Ld N-Port pWWN:0x%Lx 
Storage:[chars] [chars]. 

Explanation    An RSCN event was received for the storage associated with a job.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_COMPLETE: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the completion of a data migration job.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the suspension of data migration job.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR_LOST_SSM_PEER_CONNECTION: Job Id:%Ld 
NumSession:[dec]. 

Explanation    Event indicating the suspension of data migrationjob because of in IP connectivity to the peer SSM.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_START: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the start of a data migration job.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_STOP: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating that the data migration job was stopped by administrator.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_COMPLETE: Job Id:%Ld 
NumSession:[dec]. 

Explanation    Event indicating the completion of a data migration job verification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_ERROR: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the suspension of data migration job verification due to an error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_START: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the start of a data migration job verification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_STOP: Job Id:%Ld NumSession:[dec]. 

Explanation    Event indicating the suspension of data migration job verification by the user.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

DPP_DEBUG Messages

This section contains the data path processor debug (DPP_DEBUG) messages.

DPP_DEBUG-2

Error Message    DPP_DEBUG-2-DPP_CRIT: [DPP[dec]] [chars]. 

Explanation    A data path processor generated a critical message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

DPVM Messages

This section contains the dynamic port VSAN membership (DPVM) messages.

DPVM-2

Error Message     DPVM-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for 
[chars]. 

Explanation    Memory allocation failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DPVM-2-FEATURE_DISABLED: [chars]. 

Explanation    The dynamic port VSAN membership feature is unavailable and disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Deprecated Cisco MDS SAN-OS Release 2.0(2b).

Error Message    DPVM-2-FEATURE_ENABLED: [chars]. 

Explanation    Dynamic port VSAN membership (DPVM) is available and enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Deprecated Cisco MDS SAN-OS Release 2.0(2b).

DPVM-3

Error Message     DPVM-3-DB_ERR: [chars]. 

Explanation    An error occurred during a dynamic port VSAN membership database operation. The error message indicates the reason for the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DPVM-3-DDAS_MODE_INVALID: [chars]. 

Explanation    The Distributing Devise Alias Services (DDAS) mode is invalid when you merge two switches that have different device aliases.

Recommended Action    Make the DDAS mode consistent across switches.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    DPVM-3-INIT_FAIL: [chars]. 

Explanation    An error occurred during dynamic port VSAN membership initialization. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DPVM-3-MTS_ERR: [chars]. 

Explanation    An error occurred in processing a messaging and transaction service (MTS) message. The error message indicates the error that occurred.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DPVM-3-PSS_ERR: [chars]. 

Explanation    An error occurred during a dynamic port VSAN membership persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation that caused the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DPVM-4

Error Message     DPVM-4-ACTIVATION_FAIL: [chars]. 

Explanation    VSAN membership The activation of dynamic port VSAN membership (DPVM) device mappings failed because of the reason shown in the error message.

Recommended Action    Correct the error and reactivate the DPVM database. Enter the dpvm activate CLI command or use a similar procedure with Fabric Manager/Device Manager.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DPVM-4-FEATURE_DISABLED: [chars]. 

Explanation    Dynamic port VSAN membership (DPVM) is unavailable and disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(2b).

DPVM-6

Error Message    DPVM-6-FEATURE_ENABLED: [chars]. 

Explanation    Dynamic port VSAN membership (DPVM) is available and enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(2b).

Error Message    DPVM-6-INFO: [chars]. 

Explanation    An event occurred that affects the dynamic port VSAN membership. The error message indicates the event.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DSTATS Messages

This section contains the DSTATS messages.

DSTATS-2

Error Message     DSTATS-2-PSS_INIT_FAIL: pss initialization failed due to error: 
[hex]. 

Explanation    DSTATS persistent storage service (PSS) initialization failed because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

DSTATS-3

Error Message     DSTATS-3-PSS_CREATE_FAIL: pss create runtime database failed due to 
error: [hex]. 

Explanation    DSTATS failed to create the persistent runtime database using the persistent storage service (PSS) because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    DSTATS-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed 
due to error: [hex]. 

Explanation    DSTATS failed to delete the persistent storage service (PSS) runtime entry key because of the reason shown in the error message.

Recommended Action    Enter the show flash command or similar Fabric Manager/Device Manager procedure to collect more information. See the PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to 
error: [hex]. 

Explanation    DSTATS failed to set the persistent storage service (PSS) runtime max key because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See the PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to 
error: [hex]. 

Explanation    DSTATS failed to set the persistent storage service (PSS) runtime max value because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: 
[hex]. 

Explanation    DSTATS failed to open the persistent storage service (PSS) runtime database because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to 
error: [hex]. 

Explanation    DSTATS failed to reload the persistent storage service (PSS) runtime database because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to 
uri:[chars] failed due to error: [hex]. 

Explanation    DSTATS failed to snapshot the persistent storage service (PSS) runtime debug to the URI because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] 
failed due to error: [hex]. 

Explanation    DSTATS failed to snapshot the persistent storage service (PSS) runtime to URI because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     DSTATS-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] 
failed due to error: [hex]. 

Explanation    DSTATS failed to store the persistent storage service (PSS) runtime entry key/value pair because of the reason shown in the error message.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to collect more information. See PSS system error codes in the output for the cause of the PSS error.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

EPP Messages

This section contains the exchange peer parameters (EPP) messages.

EPP-5

Error Message     EPP-5-EPP_FAILURE: Interface [chars] EPP Failure. 

Explanation    Trunk protocol failed.

Recommended Action    Enter show epp internal event-history err to determine what errors were encountered.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     EPP-5-EPP_LOOPBACK: Interface [chars] is looped back to the same 
switch. 

Explanation    The interface is looped back to another interface on the same switch.

Recommended Action    Check the connectivity of this interface and ensure that it is connected to another switch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

ETHPORT Messages

This section contains the Ethernet port (ETHPORT) messages.

ETHPORT-3

Error Message     ETHPORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface 
[chars] is not supported. 

Explanation    The transceiver is not from an authorized vendor.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to determine which transceiver is being used. Contact customer support for a list of authorized transceiver vendors.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

ETHPORT-5

Error Message     ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down 
(Administratively down). 

Explanation    The interface has been configured to be administratively down.

Recommended Action    Enter the show flash command or use a similar Fabric Manager/Device Manager procedure to set this interface to administratively up.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config 
change). 

Explanation    FCIP interface temporarily down because of a reconfiguration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down 
(Channel admin down). 

Explanation    This interface belongs to a PortChannel and the PortChannel is configured to be administratively down.

Recommended Action    Enter the no shutdown command or use a similar Fabric Manager/Device Manager procedure on the PortChannel that the interface belongs to.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface 
[chars] is down (Channel membership update in progress). 

Explanation    The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel.

Recommended Action    Wait until the PortChannel configuration completes and then try the interface configuration again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface 
[chars] is down (Isolation due to domain id assignment failure).

Explanation    Isolated due to a failure while assigning a domain.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is 
down (Isolation due to invalid fabric reconfiguration). 

Explanation    Invalid fabric reconfiguration received.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down 
(Isolation due to domain manager disabled). 

Explanation    The interface is isolated because the domain manager is disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface 
[chars] is down (Isolation due to domain manager other side not responding). 

Explanation    Remote end domain manager is not responding.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface 
[chars] is down (Isolation due to domain other side eport isolated).

Explanation    Isolating this interface because the remote end is isolated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down 
(Isolation due to domain overlap). 

Explanation    The interface is isolated because of a domain overlap.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down 
(Isolation due to ELP failure). 

Explanation    Exchange link parameters (ELP) failed on the interface.

Recommended Action    Enter show port internal info and check the status in the ELP failure reason field.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ETHPORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error 
Disabled - EPP Failure). 

Explanation    Trunk protocol failed.

Recommended Action    Enter show port internal event-history msgs to list the trunk protocol exchanges to determine why the trunk protocol failed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error 
disabled). 

Explanation    The interface encountered an error during configuration.

Recommended Action    Collect more information about failed interface using show port internal all interface [char]. In most cases, you can recover using a shutdown followed by a no shutdown

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down 
(Isolation due to ESC failure). 

Explanation    Exchange switch parameters (ESC) failed on the interface.

Recommended Action    Check the output of show port internal event-history to show the ESC protocol exchanges and determine how it failed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port 
src interface down). 

Explanation    Ethernet link to which the FCIP interface is bound is down.

Recommended Action    Verify that the Ethernet cable is connected and that the interface is administratively enabled.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel 
port src interface link down). 

Explanation    Ethernet link to which the FCIP interface is bound is down.

Recommended Action    Verify that the Ethernet cable is connected and that the remote end is also active.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT 
not present). 

Explanation    The small form-factor pluggable (SFP) device has been removed.

Recommended Action    Insert an SFP.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is 
down (Error disabled - Fcot vendor not supported). 

Explanation    The inserted small form-factor pluggable (SFP) device is not supported.

Recommended Action    Contact customer support for a list of authorized SFP vendors.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware 
Failure). 

Explanation    The module hardware has failed.

Recommended Action    Collect more information about failed module by entering the show module internal all module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive). 

Explanation    The port VSAN has been suspended or deleted.

Recommended Action    Assign a new active port VSAN to the interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down 
(Error disabled - Incompatible admin port mode). 

Explanation    The configured mode is not supported on this interface.

Recommended Action    Enter a show port internal info to determine the list of modes supported on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is 
down (Error disabled - Incompatible admin port rxbbcredit).

Explanation    The configured receive BB_credit size is not supported.

Recommended Action    Get the allowed receive BB_credit size from show port internal info.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is 
down (Error disabled - Incompatible admin port rxbufsize).

Explanation    The configured receive buffer size is not supported.

Recommended Action    Get the allowed receive buffer size from show port internal info.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down 
(Error disabled - Incompatible admin port speed). 

Explanation    The configured speed is not supported on this interface.

Recommended Action    Enter show port internal info to determine the range of speed supported on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down 
(Initializing). 

Explanation    The interface is in the process of coming up.

Recommended Action    If the interface is stuck in this state for an extended time, check the output of show port internal event-history to determine what it is waiting for.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down 
(Interface removed). 

Explanation    The interface has been removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link 
failure). 

Explanation    The physical link has gone down.

Recommended Action    Verify that the cable is connected and the remote end is not shut down.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down 
(Diag failure). 

Explanation    Diagnostic tests failed on the interface.

Recommended Action    Enter attach module to connect to the module and collect more information about the failed interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down 
(Isolation due to port loopback to same switch). 

Explanation    The interface is looped back to another interface on the same switch.

Recommended Action    Check the connectivity of this interface and ensure that it is connected to another switch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module 
removed). 

Explanation    Interface is down because the module was removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non 
participating). 

Explanation    The loop port has been put into nonparticipating mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_NONE: Interface [chars] is down (None). 

Explanation    There is no apparent reason why the interface is down.

Recommended Action    Enter show port internal info or show port internal event-history to collect more information about port and determine why it went down.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline). 

Explanation    The interface has been placed into an offline state.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down 
(Parent interface down). 

Explanation    The parent interface is down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. 
closed by peer). 

Explanation    The FCIP peer connected to this interface closed the TCP connection.

Recommended Action    Enter show interface to find the IP address of this FCIP interface. Check to see why the peer closed the TCP connection.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. 
reset by peer). 

Explanation    The TCP connection to the FCIP peer has been reset.

Recommended Action    Enter the show interface and show ip route CLI command. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is 
down (No operational members). 

Explanation    This is a PortChannel interface and all its members are operationally down.

Recommended Action    Enable at least one of the PortChannel's members.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is 
down (Isolation due to port vsan mismatch). 

Explanation    Isolated due to a mismatch in the configured port VSAN of the local and remote ends.

Recommended Action    Configure the port VSAN of the local and remote interfaces to be the same and enter the shutdown and then no shutdown commands. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in 
progress). 

Explanation    There is a fabric reconfiguration in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port 
software failure). 

Explanation    The software servicing the data path on the port has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is 
down(Tunnel source module not online). 

Explanation    The module that has the tunnel source port of this FCIP interface is not fully online.

Recommended Action    The module that has the tunnel source port is coming online. Enter show module to find the module status.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down 
(Tunnel port src interface unbound). 

Explanation    The tunnel port source interface is unbound.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel 
src port removed). 

Explanation    The tunnel source port of this FCIP interface has been removed.

Recommended Action    The source interface with an IP address that matches the IP address of the bound entity is removed. This happens normally when the module on which the source interface exists is removed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended). 

Explanation    This interface belongs to a PortChannel and has been suspended because of an error during port bringup.

Recommended Action    Enter the shutdown CLI command then no shutdown. If this happens again, enter the show port internal info and show port internal event-history CLI commands on the interface to collect more information. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down 
(Suspended due to incompatible mode). 

Explanation    This interface belongs to a PortChannel and the operational mode of the interface is different from that of the PortChannel.

Recommended Action    Change the mode and the trunking mode of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down 
(Suspended due to incompatible speed). 

Explanation    This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel.

Recommended Action    Change the speed of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down 
(Suspended due to incompatible remote switch WWN). 

Explanation    This interface belongs to a PortChannel and the remote switch WWN of the interface is different from that of the PortChannel.

Recommended Action    Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is 
down(TCP conn. closed - Keep alive expired). 

Explanation    The TCP session to the FCIP peer was closed due to loss of the TCP keepalive.

Recommended Action    This may be due to loss of IP connectivity. Enter the show interface and show ip route CLI commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP 
conn. closed - retransmit failure). 

Explanation    Interface is down due to a maximum retransmission failure.

Recommended Action    This may be due to loss of IP connectivity. Enter the show interface and show ip route CLI commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is 
down(TCP conn. closed - Persist timer expired). 

Explanation    The TCP persist timer expired and the connection was in idle state for the maximum backoff time without receiving an ACK (TCP window size update) from the peer.

Recommended Action    This may be due to loss of IP connectivity. Enter the show interface and show ip route commands to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter traceroute [ipaddr] to check the connectivity to the peer. You can also use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and check the connection to the peer.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down 
(Linecard upgrade in progress). 

Explanation    A line card software upgrade is in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ETHPORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down 
(Isolation due to VSAN mismatch). 

Explanation    This is a trunking interface and the VSANs configured here do not match the VSANs configured on the remote end.

Recommended Action    Check the VSANs configured on the local end with the remote end.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is 
down (Isolation due to zone merge failure). 

Explanation    The interface has been isolated due to a failure during zone merge.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] 
is down (Isolation due to remote zone server not responding).

Explanation    Isolated due to remote zone server not responding.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release1.2(2a).

Error Message     ETHPORT-5-IF_TRUNK_DOWN: Interface [chars], VSAN [chars] is down 
([chars]). 

Explanation    The interface is trunking and the VSAN is down due to the reason shown.

Recommended Action    Enter show interface, show port internal info interface [vsan], and show port internal event-history interface [vsan] to help determine why this VSAN is down on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_TRUNK_UP: Interface [chars], VSAN [chars] is up. 

Explanation    The interface is trunking and the VSAN is up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     ETHPORT-5-IF_UP: Interface [chars] is up [chars]. 

Explanation    Interface is up. If applicable, the mode is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

EXCEPTIONLOG Messages

This section contains the exception log (EXCEPTIONLOG) messages.

EXCEPTIONLOG-SLOT#-2

Error Message    EXCEPTIONLOG-SLOT#-2-LC_EXP_MSG: Linecard exception: [chars] is the 
affected Port bit map. [dec] Additional information - [chars]. 

Explanation    Line card exception event.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FC-TUNNEL Messages

This section contains the FC-TUNNEL messages.

FC-TUNNEL-3

Error Message     FC-TUNNEL-3-INTERNAL_ERROR: Internal error: [chars]. 

Explanation    FC MPLS tunnel process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-IPFC_ERROR: IPFC API, [chars], failed with error [hex]. 

Explanation    FC MPLS tunnel invoked the IPFC API and received the error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-MTS_ERROR: MTS message transmission failed with error 
[dec].

Explanation    FC MPLS tunnel process unsuccessfully tried to send a messaging and transaction service (MTS) message. The messaging and transaction service (MTS) error number is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-NS_ERROR: FCNS API, [chars], failed with error [hex]. 

Explanation    FC MPLS tunnel invoked the Fibre Channel name server (FCNS) API and received an error code. The error message shows the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-PM_ERROR: Port Manager API, [chars], failed with error 
[hex]. 

Explanation    FC MPLS tunnel invoked the Port Manager API and received an error. The error message shows the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for 
[chars] failed with error [hex]. 

Explanation    FC MPLS tunnel read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message shows the configuration, which the process tried to restore and system error code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-PSS_ERROR: PSS operation [chars] returned error: [hex]. 

Explanation    A persistent storage service operation failed. The error message shows the context where the failure occurred and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for 
[chars] failed with error [hex]. 

Explanation    FC MPLS tunnel read the saved runtime database and encountered an error while rebuilding the runtime database. The error message shows the runtime database, which the process tried to restore and the system error code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-RIB_ERROR: RIB API, [chars], failed with error [hex]. 

Explanation    FC MPLS tunnel invoked the routing information base (RIB) API and received an error. The error message shows the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-RSVP_PROTO_ERROR: RSVP protocol error: [chars]. 

Explanation    RSVP-TE protocol error is encountered. The error message shows the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], 
is received. 

Explanation    FC MPLS tunnel process received unexpected messaging and transaction service (MTS) event. The error message shows the messaging and transaction service (MTS) opcode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FC-TUNNEL-5

Error Message     FC-TUNNEL-5-MSG_INTERFACE_DOWN: Interface [chars] is down. 

Explanation    The Fibre Channel interface is down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FC-TUNNEL-5-MSG_INTERFACE_UP: Interface [chars] is up. 

Explanation    The Fibre Channel interface is up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCC Messages

This section contains the Fibre Channel Congestion Control (FCC) messages.

FCC-2

Error Message     FCC-2-SHUTDOWN: Process shutting down: [chars]. 

Explanation    The Fibre Channel Congestion Control process is shutting down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCC-5

Error Message     FCC-5-BAD_MSG: Received bad message: [chars]. 

Explanation    The Fibre Channel Congestion Control process has received a malformed or unrecognized message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCC-5-CONGESTION_STATE_CHANGE_NOTIF: Received Congestion State Change 
notification to state: [dec]. 

Explanation    The Fibre Channel Congestion Control process has received a congestion state change notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC-5-DISABLE: FCC has been disabled. 

Explanation    The Fibre Channel Congestion Control process has been disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCC-5-ENABLE: FCC has been enabled. 

Explanation    The Fibre Channel Congestion Control process has been enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCC-5-RATE_LIMIT_END_NOTIF: Received Rate Limit End notification. 

Explanation    The Fibre Channel Congestion Control process has received a rate limit end notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC-5-RATE_LIMIT_START_NOTIF: Received Rate Limit Start notification. 

Explanation    The Fibre Channel Congestion Control process has received a rate limit start notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC-5-STARTING: FCC process started. 

Explanation    The Fibre Channel Congestion Control process started successfully.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCC-6

Error Message     FCC-6-PRIO_UPDATE: Updated enable priority to [dec]. 

Explanation    The Fibre Channel Congestion Control process is active for packets with priority greater than or equal to the threshold shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCC_LC Messages

This section contains the Fibre Channel Congestion Control line card (FCC_LC) messages.

FCC_LC-2

Error Message    FCC_LC-2-ERROR_SENDING_HEART_BEAT: Error sending heart beat [dec]. 

Explanation    Fibre Channel Congestion Control line card (FCC_LC) had an error sending a heartbeat.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    FCC_LC-2-EXITING: Exiting fcc_lc: [chars]. 

Explanation    Fibre Channel Congestion Control line card (FCC_LC) is exiting.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     FCC_LC-2-HEART_BEAT_NOT_SENT: Heart beat not sent for [dec] 
millisecs. 

Explanation    Fibre Channel Congestion Control line card (FCC_LC) has not sent a heartbeat.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    FCC_LC-2-UNABLE_READ_DATA: Unable to read fcc data ([chars]). 

Explanation    Fibre Channel Congestion Control is unable to read and process relevant FCC data.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    FCC_LC-2-SHUTDOWN: Process shutting down: [chars]. 

Explanation    The Fibre Channel Congestion Control line card process is shutting down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

FCC_LC-5

Error Message     FCC_LC-5-BAD_MSG: Received bad message: [chars]. 

Explanation    The Fibre Channel Congestion Control line card process has received a malformed or unrecognized message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC_LC-5-DISABLE: FCC_LC has been disabled. 

Explanation    The Fibre Channel Congestion Control line card process has been disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC_LC-5-ENABLE: FCC_LC has been enabled. 

Explanation    The Fibre Channel Congestion Control line card process has been enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCC_LC-5-STARTING: FCC_LC process started. 

Explanation    The Fibre Channel Congestion Control line card process started successfully.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

FCC_LC-6

Error Message     FCC_LC-6-PRIO_UPDATE: Updated enable priority to [dec]. 

Explanation    The Fibre Channel Congestion Control line card process is active for packets with priority less than or equal to the threshold shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

FCD Messages

This section contains the FICON control device (FCD) messages.

FCD-7

Error Message     FCD-7-SB3_ABTS_EXCHANGE: sb3 aborted exchange[hex] from vsan:[dec] 
ch:[hex] chi:[hex] ccw:[hex] token:[hex] cmd:[hex] reason:[chars] 
state:[chars]:[dec]. 

Explanation    SB3 aborted exchange due to the reason given. Aborts are caused by either the channel or control unit detecting a device protocol error. Recovery actions are performed to restore communication. In certain circumstances aborts occur in normal operations.

Recommended Action    No action is required if communication with FICON control device is still operational.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDD Messages

This section contains the Fibre Channel device discovery (FCDD) messages.

FCDD-SLOT#-3

Error Message     FCDD-SLOT#-3-LOG_FCDD_ERR: Nonrecoverable error - exiting: [chars]. 

Explanation    Errors caused the program to exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDD-SLOT#-4

Error Message     FCDD-SLOT#-4-LOG_FCDD_WARNING: Warning!: [chars]. 

Explanation    Serious errors that affect all normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDD-SLOT#-5

Error Message     FCDD-SLOT#-5-LOG_FCDD_GCONF_FSM: [chars]. 

Explanation    Illegal event received in global configuration finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDD-SLOT#-5-LOG_FCDD_NOTICE:  [chars]. 

Explanation    Major configuration changes occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDD-SLOT#-5-LOG_FCDD_RESCAN_FSM:  [chars]. 

Explanation    Illegal event received in rescan finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDD-SLOT#-5-LOG_FCDD_TZONE_FSM:  [chars]. 

Explanation    Illegal event received in twilight zone remover finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDD-SLOT#-5-LOG_FCDD_VCONF_FSM:  [chars]. 

Explanation    Illegal event received in VSAN configuration finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDD-SLOT#-5-LOG_FCDD_VNO_FSM:  [chars]. 

Explanation    Illegal event received in VSAN normal operation finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDD-SLOT#-7

Error Message     FCDD-SLOT#-7-LOG_FCDD_DEBUG:  [chars]. 

Explanation    Unexpected errors that affect some normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDD_HELPER Messages

This section contains the FCDD_HELPER messages. FCDD_HELPER messages were deprecated in Cisco MDS SAN-OS Release 1.3(3a). They were replaced with FCDDH messages.

FCDD_HELPER-SLOT#-3

Error Message     FCDD_HELPER-SLOT#-3-LOG_FCDDH_ERR:  Nonrecoverable error - exiting: 
[chars]. 

Explanation    Errors caused the program to exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCDD_HELPER-SLOT#-4

Error Message     FCDD_HELPER-SLOT#-4-LOG_FCDDH_WARNING:  Serious error: [chars]. 

Explanation    Serious errors that affect all normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCDD_HELPER-SLOT#-5

Error Message     FCDD_HELPER-SLOT#-5-LOG_FCDDH_DEBUG:  Unexpected error: [chars]. 

Explanation    Unexpected errors that affect some normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCDD_HELPER-SLOT#-5-LOG_FCDDH_NOTICE:  [chars]. 

Explanation    Major configuration changes occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCDDH Messages

This section contains the Fibre Channel device discovery helper FCDDH messages.

FCDDH-SLOT#-3

Error Message     FCDDH-SLOT#-3-LOG_FCDDH_ERR:  Nonrecoverable error - exiting: 
[chars]. 

Explanation    Errors caused the program to exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FCDDH-SLOT#-4

Error Message     FCDDH-SLOT#-4-LOG_FCDDH_WARNING:  Serious error: [chars]. 

Explanation    Serious errors that affect all normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FCDDH-SLOT#-5

Error Message     FCDDH-SLOT#-5-LOG_FCDDH_DEBUG:  Unexpected error: [chars]. 

Explanation    Unexpected errors that affect some normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCDDH-SLOT#-5-LOG_FCDDH_NOTICE:  [chars]. 

Explanation    Major configuration changes have occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FCDOMAIN Messages

This section contains the Fibre Channel domain manager (FCDOMAIN) messages.

FCDOMAIN-2

Error Message    FCDOMAIN-2-DOMS_CONFLICT: Conflict detected: ([dec]) domain ID [dec] 
WWN [chars]. 

Explanation    Two switches have the same WWN or domain ID.

Recommended Action    Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    FCDOMAIN-2-EPORT_ALREADY_ISOLATED: Interface [chars] is down - VSAN 
[dec]. 

Explanation    The domain manager was going to isolate the interface in the VSAN shown in the error message, but the interface does not exist.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-2-EPORT_ISOLATED: Isolation of interface [chars] (reason: 
[chars]). 

Explanation    The domain manager has isolated the interface because of the reason shown in the error message. Enter show interface. Based on the reason specified, you might have to reinitialize the port or ensure the domains are adequate and unique in the VSAN and perform a disruptive restart by entering fcdomain restart disruptive.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-FC2_INITIALIZATION_FAILED: FC initialization sequence 
failed. 

Explanation    The domain manager process has not been able to complete the initialization sequence with the FC (Fibre Channel) subsystem. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-FC2BIND_FAILED: Bind to FC2 Service failed. 

Explanation    The domain manager has not been able to contact the FC2 module.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-FCID_PERSISTENT_TBL_COMPLETELY_FULL: FCID persistent 
table is completely full. 

Explanation    The domain manager has the FC ID persistent table full with entries. Enter show fcdomain fcid persistent to view the entries currently in the table. No more entries can be saved as persistent FC IDs across reboots.

Recommended Action    Enter purge fcdomain fcid to purge stale entries and to obtain more free entries. Alternatively, you can disable the feature on certain VSANs which are not critical using no fcdomain fcid persistent.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-INITIALIZATION_FAILED: Initialization sequence failed. 

Explanation    The domain manager has not been able to complete the initialization sequence. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-MTS_INITIALIZATION_FAILED: IPC initialization sequence 
failed. 

Explanation    The domain manager has not been able to complete the initialization sequence with the interprocess communication (IPC) subsystem. The domain manager depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-MTSBIND_FAILED: Bind to IPC failed. 

Explanation    The domain manager has not been able to contact the inter-process communication (IPC) module.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-MTSREGISTRATION_FAILED: Registration of opcodes with IPC 
Service failed. 

Explanation    The domain manager has not been able to register its messages with the inter-process communication (IPC) module.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-2-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected 
that the local switch has the same domain ID [dec] and WWN [chars] of another 
switch. 

Explanation    The local switch has the same domain ID and WWN of another switch.

Recommended Action    Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-2-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected 
conflict between two switches having the same non-virtual domain ID [dec] and the 
same WWN [chars]. 

Explanation    Two switches have the same non-virtual domain ID and the same WWN.

Recommended Action    Check which switches have the same WWN and change one to a unique WWN. Then change the domain ID for one of the switches.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    FCDOMAIN-2-PSSBIND_FAILED: Bind to Persistent Storage Service failed. 

Explanation    The domain manager has not been able to contact the persistent storage service (PSS).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-RDIRJT: Rejected request for domain ID [dec], WWN requestor 
[chars] (reason code [dec]). 

Explanation    An invalid request for domain IDs has been rejected by fcdomain.

Recommended Action    Enter show fcdomain for all the switches in the affected VSAN. If a switch does not have a valid current domain ID, configure the preferred domain ID zero, then enter the fcdomain restart CLI command in the affected VSAN. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-SDWRAPBIND_FAILED: Bind to Debug Server failed. 

Explanation    The domain manager has not been able to contact the history debug service. Any problems occurring in the domain manager will not be logged to this debug history list.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-SDWRAPHISTINIT_FAILED: Initialization of history message 
list failed. 

Explanation    The domain manager has not been able to contact the history debug service. Any problems occurring in the domain manager will not be logged to this debug history list.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-2-SYSBIND_FAILED: Bind to System Manager service failed. 

Explanation    The domain manager has not been able to contact the system manager.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-SYSMGR_INITIALIZATION_FAILED: System Manager 
initialization sequence failed. 

Explanation    The domain manager has not been able to complete the initialization sequence with the system manager. The domain manager process depends on resources not available at the moment. The switch might be short in memory or some other component might be unable to provide the necessary information to the domain manager.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-2-VSAN_MERGE_DETECTED:  Merge detected with VSAN [dec] 
(Common Fabric Name [chars]). 

Explanation    The local VSAN and remote VSAN have the same principal switch and are connected in the same logical fabric.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDOMAIN-3

Error Message    FCDOMAIN-3-COMMITERRORLOCALINVALIDALLOWEDDOMS: A remote switch 
attempted to locally apply an illicit allowed domains configuration. 

Explanation    A remote switch attempted to locally apply an allowed domains configuration that does not include all currently assigned domains or the locally configured domain.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-3-COMMITERRORREMOTEINVALIDALLOWEDDOMS: A remote switch 
(domain ID [dec], WWN [chars]) refuses to locally apply the proposed allowed 
domains. 

Explanation    The remote switch the with domain ID and WWN listed in the error message refuses to locally apply the proposed allowed domains. This is probably because the proposed allowed domains list is incompatible with the locally configured domain or domain ID list.

Recommended Action    Check the configuration on the remote switch, and make sure that the proposed allowed domains include the local domain ID. Also, make sure that the proposed allowed domains include all the domains in the local domain ID list.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-3-MTSOPENTRX_FAILED: IPC failure (opening of a transaction 
failed). 

Explanation    The domain manager was not able to open a transaction for high availability purposes.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-3-MTSRECV_FAILED: IPC failure (receiving of a message 
failed). 

Explanation    The domain manager has not been able to receive a message from the inter-process communication (IPC) module.

Recommended Action    Execute a nondisruptive fcdomain restart in the affected VSAN.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-3-MTSRESP_FAILED: IPC failure (replying to a message 
failed). 

Explanation    The domain manager has not been able to reply to a request coming from the inter-process communication (IPC) module.

Recommended Action    Execute a nondisruptive fcdomain restart in the affected VSAN.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-3-MTSSEND_FAILED: IPC failure (sending of a message failed). 

Explanation    The domain manager has not been able to send a message to the message transactional service (MTS).

Recommended Action    Execute a nondisruptive fcdomain restart in the affected VSAN.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-3-MTSSENDREQ_FAILED: IPC failure (sending of a request 
failed). 

Explanation    The domain manager was not able to send a request using the inter-process communication module.

Recommended Action    Execute a nondisruptive fcdomain restart in the affected VSAN.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-3-NVRAMFAILURE: NVRAM open failed. 

Explanation    Reading the last assigned run time domain IDs from NVRAM failed.

Recommended Action    The domain manager is able to continue without using the NVRAM.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-3-PORT_SUSPENDED: Response (Cmd Code [hex]) for SWILS [hex] 
intended for [chars] is received on [chars]. 

Explanation    An FC2 SW-ILS response frame has been received on the wrong interface.

Recommended Action    Check the configuration of both the interfaces on the local switch; also check the interfaces on the other side of the corresponding links. Ensure whether the interfaces should all belong to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    FCDOMAIN-3-SDWRAPBIND_FAILED: Bind to debug server failed. 

Explanation    The domain manager feature has not been able to contact the debug service. Any problems occurring in the The domain manager feature will not be logged.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    FCDOMAIN-3-SDWRAPHISTINIT_FAILED: Initialization of history message 
list failed. 

Explanation    The domain manager feature has not been able to contact the debug history service. Any problems occurring in the fcdomain feature will not be logged to this debug history.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    FCDOMAIN-3-VSAN_MERGE_DETECTED:  Merge detected with VSAN [dec] 
(Common Fabric Name [chars]). 

Explanation    The local VSAN and VSAN [dec] have the same principal switch [chars], hence are connected in the same logical fabric.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

FCDOMAIN-4

Error Message    FCDOMAIN-4-DM_ALLOWED_DM_LIST_MOD_ON_SUBORDINATE: Allowed domain list 
for vsan [dec] modified on subordinate switch with fcdomain distribution enabled. 

Explanation    The allowed domai list was modified on a non-principal switch while fcdomain distribution was enabled.

Recommended Action    We recommend that you modify the allowed domain list on the principal switch only when fcdomain distribution is enabled. Discard the current session on the local switch and start a new one on the principal switch.

Introduced Cisco MDS SAN-OS Release 3.0(2).

Error Message    FCDOMAIN-4-FABRICCONFSTARTRCF: Disruptive reconfiguration started. 

Explanation    A disruptive reconfiguration (RCF phase) started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-4-FC2_CORRUPTED: Received malformed FC2 [chars] frame. 

Explanation    The domain manager received a malformed FC2-SWILS frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-4-FCID_PERSISTENT_TBL_ALMOST_FULL: FCID persistent table is 
almost full. 

Explanation    The domain manager has 80% or more of the FC ID persistent table full with entries. Enter show fcdomain fcid persistent to view the entries currently in the table.

Recommended Action    Enter purge fcdomain fcid to purge stale entries and to obtain more free entries.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDOMAIN-5

Error Message     FCDOMAIN-5-DOMAIN_TYPE_IS_PREFERRED: The domain ID type is currently 
configured as preferred in all the existing VSANs. 

Explanation    All the currently existing VSANs have the domain ID type configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link.

Recommended Action    Use the CLI or Fabric Manager/Device Manager to configure the domain ID type as static in an existing VSAN. On the CLI, enter the fcdomain domain [static vsan vsan-id] command.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-5-FABRICCONFSTARTBF: Nondisruptive reconfiguration started 
- VSAN [dec]. 

Explanation    A nondisruptive reconfiguration started on VSAN [dec].

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-5-FCIDP_DISABLED: FCID persistency feature is currently not 
enabled in any of the existing VSANs. 

Explanation    All the currently existing VSANs have the FC ID persistency feature disabled.

Recommended Action    Enter fcdomain fcid persistent [vsan]

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-5-FCID_PERSISTENT_TBL_HALF_FULL: FCID persistent table is 
half full. 

Explanation    The domain manager has 50% of the FC ID persistent table full with entries. Enter show fcdomain fcid persistent

Recommended Action    Enter purge fcdomain fcid to purge stale entries and to obtain more free entries.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-5-PSWSSTARTED: Principal Switch Selection started - VSAN 
[dec]. 

Explanation    The principal switch selection has started for the VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message    FCDOMAIN-5-UNKNOWNDOMAININCFSDATAREQUEST: Received CFS Data request 
from unknown domain [dec]. 

Explanation    A CFS Data request from the unknown domain [dec] has been received.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-5-UNKNOWNDOMAININCFSLOCKREQUEST: Received CFS Lock request 
from unknown domain [dec]. 

Explanation    A CFS Lock request from the unknown domain [dec] has been received.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-5-UNKNOWNDOMAININCFSRELEASEREQUEST: Received CFS Release 
request from unknown domain [dec]. 

Explanation    A CFS Release request from the unknown domain [dec] has been received.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-5-UNKNOWNDOMAININUNKNOWNCFSREQUEST: Received CFS request 
from unknown domain [dec]. 

Explanation    A CFS request from the unknown domain [dec] has been received.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

FCDOMAIN-6

Error Message    FCDOMAIN-6-BF_STARTED: BF started by [chars]. 

Explanation    A build fabric has started in this VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    FCDOMAIN-6-CANNOTFREESINGLEFCID: Impossible to free single FCIDs. 

Explanation    It is not possible to free single FC IDs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-CLEARLOCKNOTIFICATIONRECEIVED: Implict lock release. 

Explanation    Lock has been implicitly released due to a clear session operation.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release.

Error Message    FCDOMAIN-6-DOMAINID_INVALID: Local domain ID invalid. 

Explanation    The local domain ID is invalid.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-6-DOMAINID_VALID: Local domain ID [dec] available. 

Explanation    The domain ID is available.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a)

Error Message    FCDOMAIN-6-DOWNSTREAM_SWITCHED: Downstream interface has been 
fast-switched from [chars] to [chars]. 

Explanation    The downstream interface has been fast-switched because of a link failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(2)

Error Message     FCDOMAIN-6-UPSTREAM_SWITCHED: Upstream interface has been 
fast-switched from [chars] to [chars]. 

Explanation    The upstream interface has been fast-switched because of a link failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(2)

Error Message    FCDOMAIN-6-EPORT_ALREADY_CREATED: Interface [chars] already created. 

Explanation    The interface is already created.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-EPORT_ALREADY_DOWN: Interface [chars] is already down. 

Explanation    The interface is already down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-EPORT_CLEANUP: Interface [chars] received cleanup request. 

Explanation    The domain manager on the interface has received a cleanup request.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-EPORT_CREATED: Creation of interface [chars]. 

Explanation    The domain manager is going to create the interface shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-EPORT_DOWN: Interface [chars] is down. 

Explanation    The domain manager is going to remove the interface from its database.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-FABRICCONFSTARTBF: Nondisruptive reconfiguration started. 

Explanation    A nondisruptive reconfiguration (BF phase) of the VSAN has started. This can happen when two or more fabrics merge, or when the user manually triggers a nondisruptive reconfiguration of the VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-6-FABRICNAME_INVALID: Fabric name not available. 

Explanation    Fabric name is not available.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-FABRICNAME_VALID: Fabric name [chars] available. 

Explanation    Fabric name is available.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-FCIDALREADYFREE: FCIDs already free. 

Explanation    FC IDs are already free.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-FCIDNOTSTORED: FCIDs not stored. 

Explanation    FC IDs are not stored.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-FCIDS_ASSIGNED: Assigned FCID(s) [hex]:[hex]:[hex] with 
mask [dec]. 

Explanation    The domain manager assigned the FC ID(s) with mask shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     FCDOMAIN-6-FCIDS_FREED: Freed FCID(s) [hex]:[hex]:[hex] with mask 
[dec]. 

Explanation    The domain manager freed FC ID(s) with the mask shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     FCDOMAIN-6-FCIDP_ENABLED_DOM_TYPE_PREFERRED: FCID persistency is 
enabled, but the domain ID type is configured as preferred. 

Explanation    The FC ID persistency feature is enabled, but the domain ID type is configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link. Should the domain ID change, all the FC IDs associated with it would be invalidated.

Recommended Action    Use the CLI or Fabric Manager/Device Manager to configure the domain ID type as static in an existing VSAN. On the CLI, enter the fcdomain domain static vsan [vsan-id] command.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-6-FCIDS_ASSIGNED: Assigned a sequence of 256 contiguous 
FCIDs starting from FCID [hex]:[hex]:[hex]. 

Explanation    The domain manager assigned a sequence of 256 contiguous FC IDs starting from the FC ID shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-6-FCIDS_FREED: Freed a sequence of 256 contiguous FCIDs 
starting from FCID [hex]:[hex]:[hex]. 

Explanation    The domain manager freed a sequence of 256 contiguous FC IDs starting from FC ID shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-6-INCORRECTDOMAIN: Requested FCIDs with domain field 
different from local domain. 

Explanation    FC IDs were requested with the domain field different from local domain.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-INCORRECTDOMAINRANGE: Requested FCIDs with domain field not 
in expected range. 

Explanation    Requested FC IDs with domain field not in expected range.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-6-INVALIDARG: Requested FCID of type 00.00.YY, but 
specifying an entire area. 

Explanation    An FC ID was requested with type 00.00.YY, but specified an entire area.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected 
that the local switch has the same domain ID [dec] and WWN [chars] of another 
switch. 

Explanation    It has been detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.

Recommended Action    Check which switches have the same WWN and change either one; then change the domain ID of either one.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Deprecated Cisco MDS SAN-OS Release 3.0(1).

Error Message    FCDOMAIN-6-MY_SAME_WWN_DIFFERENT_DOMS_CONFLICTS: During VSAN merge 
detected local WWN [chars] is already in use by another switch (the two switches 
have different domain IDs: [dec] (local) and [dec]). 

Explanation    It has been detected that the local switch has the same WWN [chars] of another switch, and that they have different domain IDs: [dec] (local) and [dec].

Recommended Action    Check which switches have the same WWN and change either one.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCDOMAIN-6-NODOMAIN: Local domain not available. 

Explanation    The local domain is not available yet.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-NOFREEFCID: No free FCIDs. 

Explanation    No free FC IDs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected 
conflict between two switches having the same non-virtual domain ID [dec] and the 
same WWN [chars]. 

Explanation    It has been detected that two switches have the same non-virtual domain ID [dec] and the same WWN [chars].

Recommended Action    Check which switches have the same WWN and change either one; then change the domain ID of either one.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Deprecated Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-6-NOTOWNER: Feature [dec] cannot free FCID 
([dec]:[dec]:[dec]). 

Explanation    Feature universal unique ID (UUID) cannot free the FC ID shown in the error message because it is not its owner.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-OTHER_SIDE_VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge 
detected overlap with virtual IVR domain ID [dec] from across the link. 

Explanation    The VSAN merge detected an overlap between the local VSAN domain ID list and the IVR virtual domain ID list in the remote VSAN.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-6-PSWSSTARTED: Principal Switch Selection started. 

Explanation    A principal switch selection (PSwS phase) has started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message    FCDOMAIN-6-RCF_STARTED: RCF started by [chars]. 

Explanation    A fabric reconfiguration has started in this VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    FCDOMAIN-6-REQSINGLEFCIDWITHINRESERVEDRANGE: Requested single FCIDs 
in area [dec] within the reserved range. 

Explanation    Requested single FC IDs in an area within the reserved range.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-REQUESTEDFCIDNOTFREE: Requested FCIDs not free. 

Explanation    Requested FC IDs are not free.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-REQUESTEDFCIDRESERVED: Requested reserved FCIDs. 

Explanation    Requested reserved FC IDs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-REQUESTEDRESERVEDFCIDMISMATCH: Requested persistent 
FCIDs, but there is a mismatch. 

Explanation    Requested persistent FC IDs, but there is a mismatch.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-SAME_WWNS_DIFFERENT_DOMS_CONFLICTS: During VSAN merge 
detected two switches with same WWN [chars] and different non-virtual domain IDs 
[dec] and [dec]. 

Explanation    Two switches have the same WWN but different non-virtual domain IDs.

Recommended Action    Check which switches have the same WWN and change either one.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    FCDOMAIN-6-TIMER_UNKNOWN: fcdomain has received a notification for an 
unknown timer expiration. 

Explanation    A timer unknown to the domain manager has expired.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-6-VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected 
overlap with local virtual IVR domain ID [dec]. 

Explanation    The VSAN merge detected an overlap between the IVR virtual domain ID on the local VSAN and the domain IDs on the remote VSAN.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FCDOMAIN-6-UUIDNOSPACEFOUND: No available space to store the identity 
of the requestor the FCIDs. 

Explanation    No available space to store the identity of the requestor for the FC IDs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-6-UUIDNOTFOUND: Universal Unique ID (UUID) not found. 

Explanation    Universal unique ID (UUID) not found.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCDOMAIN-7

Error Message     FCDOMAIN-7-EPORT_ALREADY_ISOLATED: Interface [chars] is down. 

Explanation    The domain manager was going to isolate the interface, but the interface does not exist.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-7-FABRICCONFCOMPLETEDBF: Nondisruptive reconfiguration 
completed. 

Explanation    A nondisruptive reconfiguration (BF phase) completed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-7-FABRICCONFCOMPLETEDRCF: Disruptive reconfiguration 
completed. 

Explanation    A disruptive reconfiguration (RCF phase) has completed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-7-FC2_RETRY: Retransmission of FC2 frame on interface [chars] 
(Cmd Code: [hex]). 

Explanation    The domain manager is retrying an FC2 frame on the interface because of a loss/no response. The command code of the frame is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-7-FCID_IN_USE_PURGING_FOR_FICON_MGR: FICON needs to purge the 
persistent FCID table, but at least one FCID is still in use,  preventing this 
purge from completely remove all entries belonging to the VSAN. 

Explanation    There may be a problem in the sequence that shuts down all interfaces before fcdomain receives a request from FICON manager to purge the persistent FC ID table.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FCDOMAIN-7-FSM_FAILED: FSM transition failed on interface [chars] 
(current state [chars]). 

Explanation    The domain manager finite state machine generated an invalid event on the interface for which no proper action was defined.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-7-FSM_FORBIDDEN_TRANSITION: fcdomain state machine has hit a 
forbidden transition. 

Explanation    The domain manager state machine has tried to execute a forbidden transition.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-7-INTERFACERDY: Interface [chars] ready. 

Explanation    Interface is ready.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-7-PREACTIONTYPE_UNKNOWN: fcdomain state machine has hit an 
unknown pre-action type. 

Explanation    An undefined pre-action type has been used.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCDOMAIN-7-PSWSCOMPLETED: Principal Switch Selection completed (Fabric 
Name [chars]). 

Explanation    The principal switch selection (PSwS phase) has completed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCDOMAIN-7-RDIACC: Assigned domain ID [dec], WWN of requestor [chars] 
(requested domain ID [dec]). 

Explanation    Domain ID has been received by VSAN with WWN shown in the error message. The requested domain ID is also shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCFWD Messages

This section contains the FCFWD messages.

FCFWD-3

Error Message     FCFWD-3-ERROR: [chars]. 

Explanation    FCFWD encountered an error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCFWD-4

Error Message     FCFWD-4-WARNING: [chars]. 

Explanation    FCFWD is generating a relevant notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCFWD-6

Error Message     FCFWD-6-INFO: [chars]. 

Explanation    An FCFWD event happened.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCMPLS Messages

This section contains the FC MPLS messages. FC MPLS messages were deprecated in Cisco MDS SAN-OS Release 1.3(1).

FCMPLS-2

Error Message     FCMPLS-2-PROC_SHUTDOWN: daemon shutting down. 

Explanation    FC MPLS process exited.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-2-PROC_STARTING: daemon started in the [chars] mode. 

Explanation    FC MPLS process started. The error message describes the start mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCMPLS-3

Error Message     FCMPLS-3-INTERNAL_ERR: Internal err: [chars]. 

Explanation    FC MPLS process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-3-NO_MEM: out of memory. 

Explanation    FC MPLS process is out of dynamic memory.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-3-PSS_ERR: PSS err: [chars]. 

Explanation    The error message specifies the context where the failure occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-3-RIB_ERROR: RIB api error, api to [chars] returned [dec]. 

Explanation    FC MPLS invoked routing information base (RIB) API and received the error. The error message describes the API.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, 0x[dec], is 
received. 

Explanation    FC MPLS process received unexpected messaging and transaction service (MTS) event. MTS opcode is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCMPLS-5

Error Message     FCMPLS-5-LDP_SES_ESTABLISHED: LDP session with [chars] is 
established. 

Explanation    A new LDP session is established.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-5-LDP_SES_SHUTDOWN: LDP session with [chars] is shutdown. 

Explanation    Existing LDP session has been shut down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCMPLS-6

Error Message     FCMPLS-6-FT_SEQ_ROLLOVER: Rolling over the local ft ack number. 

Explanation    Fault-tolerant LDP is handling sequence number overflow.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-6-LDP_START_SENDING_HELLO: LDP start sending hellos to 
[chars]. 

Explanation    LDP start sending hellos to establish a session.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-6-LDP_STOP_SENDING_HELLO: LDP stop sending hellos to [chars]. 

Explanation    LDP stopped sending hello messages to the LDP peer specified in [chars].

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCMPLS-6-UNKNOWN_MSG_TYPE_RXED: Unknown LDP message type 0x[hex] is 
received from [chars]. 

Explanation    LDP process received an unknown LDP message type is specified in hex.The error message describes the LDP peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message    FCMPLS-6-UNKNOWN_TLV_RXED: Unknown LDP TLV: type 0x[hex], length 
[dec], is received from [chars]. 

Explanation    LDP process received an unknown TLV. TLV type received is specified in [hex]. TLV length is specified. The error message describes the LDP peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

FCNS Messages

This section contains the Fibre Channel name server (FCNS) messages.

FCNS-2

Error Message     FCNS-2-DB_FULL: the database; max entries [dec] exceeded. 

Explanation    Name server database is full. The max number of entries of ports is already present in the database.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-2-INIT_FAILURE: : [chars]. 

Explanation    The Fibre Channel name server initialization has failed due to [chars].

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCNS-2-NO_RESPONSE: domain [dec]. 

Explanation    No response in the VSAN from domain shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-2-PSS_VERSION_MISMATCH: : for [chars]. 

Explanation    Version mismatch for persistent storage service (PSS) for the type shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-2-RELOAD_FAILURE: : [chars]. 

Explanation    Failed to reload information from persistent storage service( PSS).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCNS-3

Error Message     FCNS-3-BAD_FRAME: : [chars]. 

Explanation    Received a bad frame from the network.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-CFG_FAILURE: : [chars]. 

Explanation    A failure related to the Fibre Channel name server configuration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-CHUNK_FAILURE: : [chars]. 

Explanation    Chunk memory failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-DB_FAILURE: : [chars]. 

Explanation    A failure occurred in the Fibre Channel name server database.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-MALLOC_FAILURE: : [chars]. 

Explanation    Memory allocation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-MTS_FAILURE: : [chars] [chars]. 

Explanation    Failure occurred trying to do a messaging and transaction service messaging and transaction service (MTS) operation.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-3-PSS_FAILURE: : [chars]. 

Explanation    Persistent storage service (PSS) failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCNS-6

Error Message     FCNS-6-DB_INFO: : [chars] [hex]. 

Explanation    Database modification for the entry shown in the error message has occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCNS-6-STATUS_INFO: : [chars]. 

Explanation    A change in the Fibre Channel name server status.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCS Messages

This section contains the Fabric Configuration Server (FCS) messages.

FCS-2

Error Message     FCS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]. 

Explanation    Memory allocation failed.

Recommended Action    Restart the process.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-2-CHUNK_ALLOC_FAILED: Chunk memory allocation failed for [chars] 
chunk. 

Explanation    Chunk memory allocation failed. The error message indicates the chunk name.

Recommended Action    Restart the process.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCS-2-NO_RESPONSE: Retried maximum number of times for [chars] to 
domain [dec] in VSAN [dec]. 

Explanation    Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    FCS-2-RANDNUM_FAIL: [chars]. 

Explanation    There was a critical error during random number generation. This error message indicates details of the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

FCS-3

Error Message     FCS-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], 
expected version [dec].[dec].[dec]. 

Explanation    There was a mismatch in the persistent storage services (PSS) version.The error message indicates the PSS service, its current version number, and the expected version.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex]. 

Explanation    An invalid Fabric Configuration Server (FCS) FC-CT frame received from FC ID is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-DB_ERR: [chars]. 

Explanation    An error occurred during a Fabric Configuration Server (FCS) database operation. [chars] indicates the reason for the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-INIT_FAIL: [chars]. 

Explanation    An error happened during Fabric Configuration Server (FCS) initialization. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-MTS_ERR: [chars]. 

Explanation    An error occurred in processing of a messaging and transaction service (MTS) message. The error message indicates the error that occurred.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-NO_MTS_RESP: [chars]. 

Explanation    There was no response to a messaging and transaction service (MTS) request. The error message indicates details of the messaging and transaction service (MTS) message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-NO_REMOTE_RESP: No response for request [chars] from domain 
[dec] in VSAN [dec]. 

Explanation    There was no response to an FC2 request. The error message indicates Fabric Configuration Server (FCS) request, remote domain, and VSAN ID.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-OTHER_ERR: [chars]. 

Explanation    A Fabric Configuration Server (FCS) generic error occurred. The error message indicates the description of the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-PSS_ERR: [chars]. 

Explanation    An error occurred during a Fabric Configuration Server (FCS) persistent storage service (PSS) operation. The error message indicates the PSS operation that caused the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-3-SOCK_ERR: sd: [dec], [chars]. 

Explanation    An FC-2 socket error occurred on socket-id (sd) listed in the error message. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCS-4

Error Message    FCS-4-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex]. 

Explanation    An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

FCS-5

Error Message     FCS-5-API_FAIL: [chars]: [chars]. 

Explanation    An API called by Fabric Configuration Server (FCS) failed. The error message indicates the failed API name and the reason for failure.

Recommended Action    If this message is seen during a cold boot, it means that the queried module came up after Fabric Configuration Server (FCS) and this case can be ignored.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCS-6

Error Message     FCS-6-INFORMATION: [chars]. 

Explanation    An event happened that affects FCS. The error message indicates the event.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCS-6-REXMIT_PKT: Retransmitting request [chars] to domain [dec] in 
VSAN [dec]. 

Explanation    There was a retransmission of an FC2 request. The error message indicates Fabric Configuration Server (FCS) request, the remote domain, and the VSAN ID.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FCSP-MGR Messages

This section contains the Fibre Channel Security Protocol (FCSP-MGR) messages.

FCSP-MGR-2

Error Message     FCSP-MGR-2-ASSERT_FAILED: Code path reached unexpected location: 
assert might have been activated: File [chars] Line [dec]. 

Explanation    This is a deprecated message and should be ignored.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message     FCSP-MGR-2-DBG_INIT_FAILED:  Debug Infrastructure Initialization 
failed ( [chars] ). 

Explanation    The debug infrastructure initialization failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCSP-MGR-2-FC2_E_INIT_FAILED:  Fibre-Channel Initialization of an 
E_Port failed ( [chars] ). 

Explanation    FC-SP manager is unable to initialize with the FC-2 E port infrastructure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-FC2_F_INIT_FAILED:  Fibre-Channel Initialization of an 
F_Port failed ( [chars] ). 

Explanation    FC-SP manager is unable to initialize with the FC-2 F port infrastructure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-FC2_UNKNOWN_FRM_RECD_CRIT:  Received an unexpected/unknown 
FC-2 frame on [chars]. 

Explanation    Received an unexpected or unknown FC-2 frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-FCSP_AUTHENT_FAILURE: FC-SP Authentication failure on Port 
[chars] (FC-SP Failure Reason: [chars] [chars]). 

Explanation    Fibre Channel authentication failed on the port.The error message shows the reason code detail.

Recommended Action    Verify password configuration and ensure appropriate security modes on this port as well as its peer port.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCSP-MGR-2-FSMU_INIT_FAILED:  State Machine Infrastructure 
Initialization failed ( [chars] ). 

Explanation    The state machine infrastructure has not initialized properly.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-IPC_INIT_FAILED: IPC (Inter Process Communication) 
Initialization failed ( [chars] ). 

Explanation    FC-SP manager is unable to initialize with the inter-process communications infrastructure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-LICENSE_UNAVAILABLE:  License:[chars] unavailable, service 
exiting. 

Explanation    The license is unavailable. The FC-SP service will exit now.

Recommended Action    Install the license file to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FCSP-MGR-2-MEM_FAILED:  Memory operations failed File: [chars] Line 
[dec] for size [hex] bytes. 

Explanation    A memory operation has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    FCSP-MGR-2-POST_INIT_FAILED:  Post-Initialization failed ( [chars] ). 

Explanation    FC-SP has failed following normal initialization.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FCSP-MGR-2-PSS_INIT_FAILED:  PSS Infrastructure Initialization failed 
( [chars] ). 

Explanation    The persistent storage services (PSS) infrastructure initialization failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FCSP-MGR-3

Error Message     FCSP-MGR-3-TASK_Q_INIT_FAILED:  Task Queue initialization failed. 

Explanation    The task queue initialization failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a)).

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FCSP-MGR-3-TIMER_GRP_INIT_FAILED:  Timer Group initialization failed. 

Explanation    The timer group initialization failed.

Recommended Action    No action is required.

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

FCSP-MGR-6

Error Message     FCSP-MGR-6-UNCOMMON_RT_PATH:  Runtime path reached special location: 
File [chars]. 

Explanation    This is a deprecated, internal message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

FDMI Messages

This section contains the Fabric-Device Management Interface (FDMI) messages.

FDMI-2

Error Message     FDMI-2-MTS_ERROR: MTS message transmission failed with error [dec]. 

Explanation    The Fabric-Device Management Interface (FDMI) process unsuccessfully tried to send a messaging and transaction service (MTS) message. MTS error number is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-2-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars] 
failed with error [hex] for key type [dec]. 

Explanation    The Fabric-Device Management Interface (FDMI) read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message describes the configuration that the process tried to restore and the system error code.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FDMI-2-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for 
[chars] failed with error [hex]. 

Explanation    The Fabric-Device Management Interface (FDMI) read the saved runtime database and encountered an error while rebuilding the runtime database. The error message describes the runtime database that the process tried to restore and the system error code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FDMI-3

Error Message     FDMI-3-BAD_FRAME: Malformed frame received: [chars]. 

Explanation    The Fabric-Device Management Interface (FDMI) process received malformed frame. The error message describes the problem.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-BAD_RESPONSE: response with command code: [hex]. 

Explanation    The Fabric-Device Management Interface (FDMI) process received bad payload in response.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FDMI-3-INTERNAL_ERROR: Internal err: [chars]. 

Explanation    The Fabric-Device Management Interface (FDMI) process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-MTS_API_ERROR: API, [chars] returned [hex]. 

Explanation    The Fabric-Device Management Interface (FDMI) invoked the API and received the error code specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-MTS_FORMAT_ERROR: Unknown MTS message format in opcode [dec] 
from module [chars]. 

Explanation    The Fabric-Device Management Interface (FDMI) received message from the module that contains an unknown message format. The messaging and transaction service (MTS) opcode is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-NO_RESPONSE: No response from switch whose domain id is [dec]. 

Explanation    The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to a switch and has not received the response. The domain ID for the switch is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-PSS_ERROR: PSS operation [chars] returned err: [hex]. 

Explanation    The error message specifies the context where the failure occurred and specifies the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FDMI-3-SW_REJ_RESPONSE: Reject response [chars] from switch whose 
domain id is [dec]. 

Explanation    The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to a switch and has received the reject response with reason code in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     FDMI-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is 
received. 

Explanation    The Fabric-Device Management Interface (FDMI) process received an unexpected messaging and transaction service (MTS) event. The messaging and transaction service (MTS) opcode is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FDMI-4

Error Message     FDMI-4-SW_REJ_RESPONSE: Reject response [chars] from switch whose 
domain id is [dec]. 

Explanation    The Fabric-Device Management Interface (FDMI) process sent an inter-switch packet to the switch and has received the reject response with reason code in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FDMI-6

Error Message     FDMI-6-DEBUG_INFO: [chars]. 

Explanation    This is Fabric-Device Management Interface (FDMI) process debug information.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FEATURE-MGR Messages

This section contains the feature manager (FEATURE-MGR) messages.

FEATURE-MGR-2

Error Message     FEATURE-MGR-2-MODULE_FM_DONE: feature manager completed. 

Explanation    Feature manager completed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FEATURE-MGR-2-MODULE_FM_STARTED: feature manager started. 

Explanation    Feature manager started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FICON Messages

This section contains the FICON messages.

FICON-2

Error Message    FICON-2-E_DUPLICATE_PN_BRINGUP_FAIL: [chars]. 

Explanation    This port has the same port number assigned to another port in the same FICON VSAN. If two ports have duplicate port numbers in a FICON VSAN, only one port can be up at a time.

Recommended Action    Avoid duplicate number assignment in each FICON VSAN

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-2-E_PN_PA_NOT_IN_BOUND: [chars]. 

Explanation    Port number or port address in the startup configuration is out of bound.

Recommended Action    Change the FICON port number assigned and save the running configuration to the startup configuration.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-2-SHUTDOWN: FICON Manager process shutting down: [chars]. 

Explanation    FICON manager is shutting down.

Recommended Action    This is a severe error. Provide the reason given in the message to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FICON-3

Error Message    FICON-3-E_ASSIGN_BINDING_PN_FAIL: [chars]. 

Explanation    Port number has FCIP or port channel binding that cannot be removed or changed.

Recommended Action    Remove port number binding of the logical interface first.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FICON-3-E_ASSIGN_INVALID_PN_PARAM: [chars]. 

Explanation    Invalid port number parameters in command.

Recommended Action    Check port numbers in the command.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FICON-3-E_ASSIGN_OVERLAP_PN_FAIL: [chars]. 

Explanation    Port number assigned to physical and logical cannot overlap.

Recommended Action    Check the port numbers in the command.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FICON-3-E_ASSIGN_PN_NOT_DOWN_FAIL: [chars]. 

Explanation    Only port number assigned to a port in the down state can be removed or changed.

Recommended Action    Bring down the port and then change the assigned port number.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     FICON-3-E_ASSIGN_PROHIBIT_PN_FAIL: [chars]. 

Explanation    Logical port address cannot be prohibited.

Recommended Action    Check port numbers in the command.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-3-E_DUPLICATE_PN_ASSIGN_WARNING: [chars]. 

Explanation    This port has the same port number assigned to another port in the same FICON VSAN. No more than one port should have the same port number in each FICON VSAN.

Recommended Action    Avoid duplicate number assignments in each FICON VSAN.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-3-E_INVALID_PA_BRINGUP_FAIL: [chars]. 

Explanation    This port either has an invalid port address assigned or has no port address assigned.

Recommended Action    Assign a valid FICON port number to the port.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-3-E_PORT_PROHIBIT_BRINGUP_FAIL: [chars]. 

Explanation    This port has been prohibited. Prohibiting E or TE ports is not allowed. This port cannot be configured in E mode or TE mode until the prohibit dynamic connectivity mask configuration is changed.

Recommended Action    Correct the prohibit dynamic connectivity mask (PDCM) for this port to bring it up as an E or TE port in a FICON VSAN.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Error Message     FICON-3-PDCM_CHANGE_REJ_E_PORT: [chars]. 

Explanation    The FICON prohibit dynamic connectivity mask (PDCM) change rejected because an E or TE port is being prohibited. Prohibiting an E or TE port in not allowed.

Recommended Action    Correct the prohibit dynamic connectivity mask (PDCM) for this port to bring the port up as an E or TE port in a FICON VSAN.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    FICON-3-E_UNASSIGN_NO_PN_FAIL: [chars]. 

Explanation    Only port number already assigned can be removed.

Recommended Action    Check port numbers in the configuration.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

FICON-5

Error Message     FICON-5-STARTING: FICON manager process starting. 

Explanation    FICON manager process is being started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FICON-6

Error Message     FICON-6-PDCM_CHANGE: VSAN [dec] port-address [dec] prohibit mask set 
to [chars]. 

Explanation    The FICON prohibit dynamic connectivity mask (PDCM) for this port has changed. The VSAN port address PDCM is now set to the value shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Error Message     FICON-6-PORT_SWAP: port number [dec] [dec] swapped. 

Explanation    FICON port numbers swapped.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FICON-6-VSAN_DISABLED: FICON disabled on VSAN [dec]. 

Explanation    FICON has been disabled on the VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     FICON-6-VSAN_ENABLED: FICON enabled on VSAN [dec]. 

Explanation    FICON has been enabled on the VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

FLOGI Messages

This section contains the fabric login (FLOGI) messages.

FLOGI-5

Error Message    FLOGI-5-MSG_IF_REINIT_ALPA_CONFLICT: [VSAN [dec], Interface [chars]] 
FL/TL interface [chars] re-initialized as ALPA - PWWN map conflict occurred. 

Explanation    The FL or TL interface reinitialized as an arbitrated loop physical address (ALPA) and now conflicts with an existing fabric login (FLOGI) session after the Loop Initialization Protocol (LIP). All devices will log in again with new ALPA and pWWN mapping.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     FLOGI-5-MSG_PORT_LOGGED_IN: [VSAN [dec], Interface [chars]] Nx Port 
[chars] with fcid [chars] logged IN. 

Explanation    Nx port logged in with the specified information.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FLOGI-5-MSG_PORT_LOGGED_OUT: [VSAN [dec], Interface [chars]] Nx Port 
[chars] logged OUT. 

Explanation    Nx port logged out.

Recommended Action    Enter the show interface, show VSAN, or show module command (or use an equivalent Fabric Manager/Device Manager procedure) to help determine why this Nx port logged out. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF Messages

This section contains the Fabric Shortest Path First (FSPF) messages.

FSPF-2

Error Message     FSPF-2-SHUTDOWN: Routing daemon shutting down : [chars]. 

Explanation    Fabric Shortest Path First (FSPF) routing daemon is shutting down because of the reason shown in the error message.

Recommended Action    This is a severe problem. Provide the reason shown and the log files for Fabric Shortest Path First (FSPF) to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF-3

Error Message     FSPF-3-BAD_FC2_PKT: Received bad FC2 packet on interface [chars] VSAN 
[dec] : [chars]. 

Explanation    Fabric Shortest Path First (FSPF) received a bad FC2 packet on the interface and VSAN shown in the error message. The error description is shown in the error message.

Recommended Action    FSPF daemon has received a bad FC frame. Provide the output of the debug fc2 pkt CLI command to your customer service representative.You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-CHECKSUM_FAIL: Checksum test failed for LSR domain [dec] in 
VSAN [dec]. 

Explanation    Periodic database checksum test failed for LSR for the domain and VSAN shown in the error message.

Recommended Action    This indicates that the internal database is corrupted because of some memory corruption problem. Provide the output of show fspf database to your customer service representative. You may need to power cycle the switch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-FC2_PROC_ERR: Error in processing [chars] packet on interface 
[chars] VSAN [dec], Error = [chars]. 

Explanation    An error occurred in processing the FC2 packet on the interface and VSAN shown in the error message. The internal error code is also shown in the error message.

Recommended Action    Enter debug fspf error to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Provide the output of the show fspf vsan [vsan-id] and show fspf vsan[vsan-id] interface commands and the debug fspf fc pkt command results for the specific interface to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-FLOOD_ERR: Error in flooding the local LSR in VSAN [dec] , 
Error = [chars]. 

Explanation    Fabric Shortest Path First (FSPF) had an error in flooding the local LSR in VSAN shown in the error message. The error description is shown in the error message.

Recommended Action    Provide the output of the debug fspf flood and debug fspf error CLI commands. If an error is reported in transmitting a packet, check if the interface is up and then enter the debug fc2 error CLI command.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-HELLO_MISMATCH: Mismatch in [chars] in the Hello packet on 
interface [chars] in VSAN [dec]. 

Explanation    There is a mismatch in the entry in the hello packet received on the interface and VSAN shown in the error message. The packet will be dropped.

Recommended Action    Check the configuration of the the hello or dead interval on the switches on the two ends of the interface to see if there is a mismatch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-INTF_TIMER_ERR: Error in processing interface timer event 
[chars] for interface [chars] in VSAN [dec] , error = [chars]. 

Explanation    Fabric Shortest Path First (FSPF) had an error processing a timer event for the named interface. The error is shown in the error message.

Recommended Action    Provide the output of the debug fspf error command to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-IPC_PROC_ERR: Error in processing IPC message : Opcode = [dec], 
Error code = [hex]. 

Explanation    Fabric Shortest Path First (FSPF) had an error processing a message (opcode shown in the error message). The internal error code is shown in the error message.

Recommended Action    An incorrect IPC message may have been received by FSPF. Provide the output of the debug fspf mts pkt and debug fspf error CLI command to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-LOCK_FAIL: FSPF failure in gaining lock. 

Explanation    There is a problem with locking a shared resource between Fabric Shortest Path First (FSPF) threads.

Recommended Action    Provide the output of the debug fspf all CLI command to your customer service representative.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FSPF-3-MTS_MSG_BEFORE_GSYNC: FSPF in standby received MTS message 
opcode = [hex] before GSYNC. 

Explanation    Fabric Shortest Path First (FSPF) in standby received a messaging and transaction service (MTS) message before receiving the GSYNC message.

Recommended Action    Provide the output of the debug fspf mts pkt command to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-RIB_ERR: Error in RIB : [chars]. 

Explanation    Fabric Shortest Path First (FSPF) had an error in interacting with the routing information base (RIB). The error description is shown in the error message.

Recommended Action    Enter show processes to check if RIB application is running. Provide the output of the debug fspf route command and RIB debug traces to your customer service representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-ROUTE_COMPUTE_ERR: Error in computing or sending routes for 
VSAN [dec] : Error = [chars]. 

Explanation    Fabric Shortest Path First (FSPF) had an error in computing routes for the VSAN. The error description is shown in the error message.

Recommended Action    Provide the error code and the output of the debug fspf error and debug fspf route CLI commands if the problem is reproducible.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-3-UNLOCK_FAIL: FSPF failure in releasing lock. 

Explanation    Cannot release the lock on the shared resource between Fabric Shortest Path First (FSPF) threads.

Recommended Action    Provide the output of the debug fspf all CLI command to your customer support representative.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     FSPF-3-VSAN_TIMER_ERR: Error in processing VSAN timer event [chars] 
for VSAN [dec] , error description = [chars]. 

Explanation    Fabric Shortest Path First (FSPF) had an internal error in processing timer event for the VSAN. The error description is shown in the error message.

Recommended Action    Provide the output of thedebug fspf error CLI command to your customer support representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF-4

Error Message     FSPF-4-FC2_DOWN_INTF: Received FC2 packet on DOWN interface [chars] 
in VSAN [dec]. 

Explanation    Fabric Shortest Path First (FSPF) received a FC2 packet on inactive interface in the VSAN shown in the error message.

Recommended Action    This message may be printed for the first FSPF packet when an interface is brought up. If the message is seen continuously, check if FSPF is disabled on one end for the interface or the VSAN. Otherwise, enter the show interface command to see if the interface is physically up only on one side. Also check if there is any error message printed for IPC_PROC_ERR.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-4-FC2_DOWN_VSAN: Received FC2 packet on inactive VSAN [dec]. 

Explanation    Fabric Shortest Path First (FSPF) received a FC2 packet on the inactive VSAN.

Recommended Action    If this message is seen continuously, check if FSPF is disabled on the VSAN. Investigate whether the VSAN is active and a valid domain is assigned on the switch. Also check if the IPC_PROC_ERR message is printed in the message logs.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-4-ILLEGAL_FSM_EVENT: Illegal FSM event for state [chars] in 
interface [chars] in VSAN [dec]. 

Explanation    An illegal protocol event has occurred for the Fabric Shortest Path First (FSPF) state machine. The old state is shown in the error message for the interface and VSAN.

Recommended Action    It is possible to get this message if a protocol packet gets dropped, but FSPF should recover and move back to FULL state. Enter show fspf interface to check the state of the interface. If it is stuck in a state other than full, provide the output the of debug fspf event and debug fspf fc pkt CLI commands for the interfaces involved to your customer support representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-4-LSR_DROPPED: [chars], Dropping LSR [dec] received on interface 
[chars] in VSAN [dec]. 

Explanation    An LSR packet is dropped because of the reason shown in the error message. LSR belonged to the domain shown in the error message and was received on the interface and VSAN shown in the error message.

Recommended Action    Provide the reason given for dropping the LSR and the output the of debug fspf fc pkt CLI command. If the reason is checksum failure, investigate for possible packet corruption or truncation. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-4-LSR_MIN_LS_ARRIVAL: Packet arrived before MIN_LS_ARRIVAL, 
Dropping LSR [dec] on interface [chars] in VSAN [dec]. 

Explanation    An LSR packet is dropped as it arrived before MIN_LS_ARRIVAL.LSR belonged to the domain shown in the error message and was received on the interface and VSAN shown in the error message.

Recommended Action    This can occur in a transient situation; the protocol recovers by retransmitting the LSR. If the message is seen continuously, provide the output of the debug fspf flood, debug fspf retrans and debug fspf error CLI commands. The message may be seen more often when interoperating with other vendors. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-4-LSU_RX_INIT: Dropping LSU received in state INIT on interface 
[chars] in VSAN [dec]. 

Explanation    An LSU packet is dropped because the interface is in the initialization (INIT) state when it received the LSU.

Recommended Action    This can occur in some transient situations. If the problem persists, provide the output of the show fspf VSAN [dec] interface and debug fspf fc pkt and debug fspf event VSAN [dec] commands to your customer support representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF-5

Error Message     FSPF-5-STARTING: Routing daemon started. 

Explanation    Fabric Shortest Path First (FSPF) routing daemon has been started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF-6

Error Message     FSPF-6-ADD_LSR: New LSR added for domain [dec] in VSAN [dec]. 

Explanation    A new LSR is added to the database for the domain and VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-DELETE_LSR: LSR deleted for domain [dec] in VSAN [dec]. 

Explanation    The LSR for the domain is deleted from the database for VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-INTF_OPER_DOWN: Down on interface [chars] in VSAN [dec]. 

Explanation    Fabric Shortest Path First (FSPF) has become operationally down on the interface and VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-INTF_OPER_UP: Up on interface [chars] in VSAN [dec]. 

Explanation    Fabric Shortest Path First (FSPF) has become operational on the interface and VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-MAX_AGE: LSR [dec] in VSAN [dec] reached Maxage. 

Explanation    The LSR for the domain and VSAN shown in the error message reached the maximum age and will be deleted from all the connected switches.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-ROLLOVER: Rolling over the incarnation number of Local LSR of 
VSAN [dec]. 

Explanation    The incarnation number of local LSR in the VSAN shown in the error message reached the maximum value and is rolling over.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-SELF_ORIGINATED: Received local LSR in VSAN [dec] with higher 
incarnation number. 

Explanation    An LSR for the local domain was received in the VSAN shown in the error message with an incarnation number higher than the one in the database. This situation should only occur initially on a topology change. If the situation persists, the domain assignment of switches may not be unique.

Recommended Action    If this message is received continuously, check if the domain assignment is unique in the fabric.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-STATE_CREATED: Internal state created [chars]. 

Explanation    Fabric Shortest Path First (FSPF) has created its internal state stateless or stateful condition shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-VSAN_OPER_DOWN: Down on VSAN [dec]. 

Explanation    Fabric Shortest Path First (FSPF) has become operationally down on the VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     FSPF-6-VSAN_OPER_UP: Up on VSAN [dec] with local domain [dec]. 

Explanation    Fabric Shortest Path First (FSPF) has started on the VSAN with the local domain shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

FSPF-7

Error Message     FSPF-7-ROUTE_THREAD_STARTED: Thread number [dec] started. 

Explanation    Route computation thread number shown in the error message has been started for Fabric Shortest Path First (FSPF).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IKE Messages

This section contains the Internet Key Exchange (IKE) messages.

IKE-3

Error Message    IKE-3-CRYPTO_INIT_ERROR:  IKEv2 crypto init error: [chars]. 

Explanation    Cryptographic initialization error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-3-ENABLE_ERROR:  Unable to store enable flag in configuration  
(error-id [hex]). 

Explanation    The Internet Key Exchange (IKE) service failed to store the enable flag in the configuration. As a result, IKE will exit.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IKE-3-FIPS_MODE_ERROR:  Could not set FIPS mode. 

Explanation    The FIPS mode could not be set by IKE.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IKE-3-MAX_HALF_CONN_LIMIT_REACHED:  IKEv1 : Exceeded the limit for 
number of half open Phase 1 connections. 

Explanation    The number of half open connections has exceeded the maximum limit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(3).

Error Message    IKE-3-PHASE1_NEGOTIATION_FAILED:  IKEv1: Phase 1 negotiation failed 
for peer [chars]. 

Explanation    The Internet Key Exchange (IKE) policy negotiation failed for the peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-3-PHASE1_PROPOSAL_MISMATCH:  IKEv1: No matching phase 1 proposal 
found for peer [chars]. 

Explanation    There is an Internet Key Exchange (IKE) policy mismatch for the peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-3-PHASE2_NEGOTIATION_FAILED:  IKEv1: Phase 2 negotiation failed 
for peer [chars]. 

Explanation    IPsec policy negotiation failed for the peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-3-PHASE2_PROPOSAL_MISMATCH:  IKEv1: No matching phase 2 proposal 
found for peer [chars]. 

Explanation    There is an IPsec policy mismatch for the peer.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-3-IKE_PROGRAM_EXIT: [chars]. 

Explanation    The Internet Key Exchange (IKE) process experienced an abnormal exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IKE-3-UNSUPPORTED_EXCHANGE:  IKEv1: Unsupported exchange [dec] 
received from [chars]. 

Explanation    An unsupported Internet Key Exchange (IKE) was received.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IKE-4

Error Message     IKE-4-INVALID_PAYLOAD_APPEAR:  IKEv2 received message (from [chars]) 
with payload ([chars]) appeared in [chars]([chars]). 

Explanation    Internet Key Exchange (IKE) received a payload in an inappropriate exchange.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-4-MESSAGE_ERROR:  IKEv2 message (from [chars]) message error: 
[chars]. 

Explanation    Internet Key Exchange (IKE) received a malformed message that does not adhere to the IKE protocol.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-4-PARSING_ERROR:  IKEv2 message (from [chars]) parsing error: 
[chars]. 

Explanation    Internet Key Exchange (IKE) received a malformed message that cannot be parsed appropriately.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-4-UNKNOWN_PAYLOAD:  IKEv2 received message (from [chars]) with 
un-recognized payload ([chars]). 

Explanation    Internet Key Exchange (IKE) received an invalid payload.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IKE-4-UNSUPPORT:  [chars] is not supported (message from [chars]). 

Explanation    Internet Key Exchange (IKE) received something unsupported.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IKE-6

Error Message     IKE-6-POLL_START_DONE: IKE is exiting since it is not enabled. 

Explanation    Internet Key Exchange (IKE) is exiting because it has not been enabled in the configuration.

Recommended Action    This is an informational message.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

ILC_HELPER Messages

This section contains the intelligent line card helper messages.

ILC_HELPER-2

Error Message    ILC_HELPER-2-NO_LICENSE_REBOOT: Linecard [dec] will reboot now. 

Explanation    The SSE license has expired; therefore, the line card will be rebooted.

Recommended Action    Install the appropriate SSE license so you can use the Storage Services Module (SSM) features.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ILC_HELPER-3

Error Message    ILC_HELPER-3-INVALID_BOOTVAR: Invalid [chars] boot variable 
configured. The linecard will come online in L2 mode. 

Explanation    The boot variable is misconfigured to a wrong image. So the linecard comes online in normal L2 mode instead of L3 mode.

Recommended Action    Configure a proper image for the target boot variable.

Introduced Cisco MDS SAN-OS Release 3.0(3).

ILC_HELPER-6

Error Message    ILC_HELPER-6-LICENSE_VALID: A valid license for linecard [dec] has 
been obtained. 

Explanation    A valid license has been obtained for the Storage Services Module (SSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ILC-SPAN Messages

This section contains the intelligent line card SPAN (ILC-SPAN) messages.

ILC-SPAN-3

Error Message    ILC-SPAN-3-ERROR: [chars]. 

Explanation    The intelligent line card SPAN manager encountered an error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IMAGE_DNLD Messages

This section contains the image download (IMAGE_DNLD) messages.

IMAGE_DNLD-SLOT#-2

Error Message    IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_COMPLETE: Module image download 
process. [chars]. 

Explanation    Image download completed. The module image is being installed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_FAILED: Module image download 
process failed. [chars]. 

Explanation    The add-on image download to the module failed. This module is not operational until an add-on image has been successfully installed.

Recommended Action    Verify the location and version of your module image. Enter install module CLI command or use a similar Fabric Manager/Device Manager procedure to download a new module image.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_STARTED: Module image download 
process. [chars]. 

Explanation    The add-on image download started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_SUCCESSFUL: Module image download 
process. [chars]. 

Explanation    The add-on image download and install successful.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IMAGE_DNLD-SLOT#-2-IMG_DNLD_COMPLETE: Module image download process. 
[chars]. 

Explanation    The image download completed. The module image is being installed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IMAGE_DNLD-SLOT#-2-IMG_DNLD_FAILED: Module image download process. 
[chars]. 

Explanation    The image download failed. The module may be inoperable.

Recommended Action    Enter the show module CLI command or use a similar Fabric Manager/Device Manager procedure to verify the state of this module. Enter the install module CLI command or use a similar Fabric Manager/Device Manager procedure to retry the image download.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_CHECK_ERROR: File System 
check failed: [chars].

Explanation    The file system consistency check failed.

Recommended Action    Use the fsck command to repair the file system. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_RECREATION: File System 
checking and recreation. [chars]. 

Explanation    File system checking and recreation if necessary for /images.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    IMAGE_DNLD-SLOT#-2-IMG_DNLD_STARTED: Module image download process. 
[chars]. 

Explanation    The image download started. The module image downloads are nondisruptive to module operation.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IMAGE_DNLD-SLOT#-5

Error Message     IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_COMPLETE: Addon module image 
download process completed. [chars]. 

Explanation    The add-on image download to the module has completed. The module should now be installing this new image.

Recommended Action    This message is informational only.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_STARTED: Addon module image 
download process started. [chars]. 

Explanation    The add-on image download to the module has started. This is a disruptive download and this module will be inoperable until this download process is complete.

Recommended Action    This message is informational only.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_SUCCESSFUL: Addon module image 
download and install process successful. [chars]. 

Explanation    The add-on image download and install to the module is successful.

Recommended Action    Enter show module to verify the module's operational status.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IMAGE_UPGRADE Messages

This section contains the image upgrade (IMAGE_UPGRADE) messages.

IMAGE_UPGRADE-SLOT#-2

Error Message     IMAGE_UPGRADE-SLOT#-2-IMAGE_UPGRADE_ERROR: [chars]. 

Explanation    An image upgrade error has occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IMAGE_UPGRADE-SLOT#-6

Error Message     IMAGE_UPGRADE-SLOT#-6-IMAGE_UPGRADE_INFO: [chars]. 

Explanation    The image upgrade information is shown.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL Messages

This section contains the IP access control list (IP-ACL) messages.

IPACL-0

Error Message     IPACL-0-EMERG: [chars]. 

Explanation    IP-ACL caused a system failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL-1

Error Message     IPACL-1-ALERT: [chars]. 

Explanation    The IP access control list caused failures in other services.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPACL-2-CRIT: [chars]. 

Explanation    The IP access control list encountered a catastrophic error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL-3

Error Message     IPACL-3-ERR: [chars]. 

Explanation    The IP access control list encountered an error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL-4

Error Message     IPACL-4-WARN: [chars]. 

Explanation    The IP access control list ignored an unexpected condition.

Recommended Action    Enter debug ipacl all, then recreate the operation scenario to find out more details.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL-5

Error Message     IPACL-5-NOTE: [chars]. 

Explanation    The IP access control list does not support this operation.

Recommended Action    Enter debug ipacl all, then recreate the operation scenario to find out more details.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPACL-6

Error Message     IPACL-6-INFO: [chars]. 

Explanation    An IP access control list event occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPCONF Messages

This section contains the IP configuration manager (IPCONF) messages.

IPCONF-2

Error Message     IPCONF-2-ALLOC_MEMORY: Memory allocation failed. 

Explanation    The IP configuration manager failed to allocate a block of dynamic memory.

Recommended Action    Check if the system is low on memory; if so reset the switch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPCONF-3

Error Message    IPCONF-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error: 
[chars]. 

Explanation    The IP configuration manager failed to write to a file. This is probably because the file sytem is full.

Recommended Action    Check the file systems and remove unnecassary files.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPCONF-3-INIT_FAILED: Initialization failed. Component [chars]. 

Explanation    The service failed to start. The failure is initializing the component shown in the error message.

Recommended Action    Enter show process to check the status of the other processes. Debug the specified component.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPCONF-4

Error Message    IPCONF-4-DAD_FAILED_EVENT: Duplicate address detection failed for 
[chars] on [chars]. 

Explanation    Duplicate address detection for IP address failed.

Recommended Action    Check the IP addresses and correct any duplicates.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

IPCONF-6

Error Message     IPCONF-6-CONFIG_EVENT: IP Configuration Msg:. 

Explanation    An IP configuration event occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IPCONF-6-INTERFACE_DELETED: The interface [chars] has been deleted. 

Explanation    The specified interface has been deleted. The service will delete all the configuration in that interface.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPCONF-6-INTERFACE_EVENT: IP address [chars] [chars] on interface 
[chars]. 

Explanation    The IP address has been successful in handling the condition shown in the error message for the interface shown.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPCONF-6-ROUTE_NOT_ACTIVE: The [chars] is not active. 

Explanation    The specified route is successfully configured but currently is not active.

Recommended Action    Check that the route is correct and the outgoing interface is operationally up.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPCONF-6-STARTING: IP configuration Manager started. 

Explanation    The IP configuration manager service has successfully started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPFC Messages

This section contains the IP over Fibre Channel (IPFC) messages.

IPFC-2

Error Message     IPFC-2-ALLOC_MEMORY: Memory allocation failed. 

Explanation    The service failed to allocate a block of dynamic memory.

Recommended Action    Check if the system is low on memory and reset the switch if necessary.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPFC-3

Error Message     IPFC-3-INIT_FAILED: Initialization failed. Component [chars]. 

Explanation    The service failed to start. The failure occurred while initializing the component shown in the error message.

Recommended Action    Enter show processes to check the status of the other processes,. Debug the specified component.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IPFC-3-IOCTL_FAILED: IOCTL failed. 

Explanation    An IOCTL to the character device failed.

Recommended Action    Enter show ipfc internal interface vsan for all the configured VSAN interfaces to check the internal status, and enter the show ipfc internal mip CLI command to check the internal status. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPFC-3-GENERIC_ERROR: Error: [chars]. Err_value: [dec]. 

Explanation    Error occurred while bringing a VSAN interface up or down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(2b).

Error Message    IPFC-3-PSSERROR: [chars]. 

Explanation    IPFC manager encountered a PSS error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

IPFC-6

Error Message     IPFC-6-CONFIG_EVENT: VSAN interface [dec] [chars]. 

Explanation    The specified VSAN interface successfully handled the condition shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPFC-6-STARTING: IP Over Fiber Channel service started. 

Explanation    The service successfully started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPFC-6-STATE_CHANGE: VSAN interface [dec] [chars]. 

Explanation    The specified VSAN interface is shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPS Messages

This section contains the IP service (IPS) messages.

IPS-2

Error Message     IPS-2-ISCSI_IPS_INIT: Ips initialization of [chars] [chars]. 

Explanation    The IP service (IPS) initialization failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

IPS-3

Error Message    IPS-3-IPS_EGRESS_PERR: Parity error on dma-bridge egress. Count: 
[dec]. 

Explanation    Parity error occured in dma-bridge egress direction.

Recommended Action    Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    IPS-3-FCIP_FTA_ACCEL_CHAIN_ABORTED: Exch Aborted FC oxid [hex] My oxid 
[hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: 
[hex] DA [hex] VSAN: [dec] (Internal [hex]:[hex]). 

Explanation    FICON tape acceleration exchange was discarded.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(3).

Error Message    IPS-3-FCIP_FTA_DATA_SENSE: Sense data with ERA [hex] sent to CH FCID: 
[hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    Sense data with ERA sent.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-FCIP_FTA_ERA_35: ERA [hex] presented to CH FCID: [hex] CHI: [hex] 
from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP got an ERA 35.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-FCIP_FTA_ERA_38: ERA 0x38 received CH FCID: [hex] CHI: [hex] from 
FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] at tape capacity: [dec] MB. 

Explanation    FCIP got an ERA 38.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-FCIP_FTA_LOCATE_RBID_MISMATCH: Permanent Error due to Locate 
RBID Mismatch, CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: 
[dec]. 

Explanation    FCIP-FTA received a permanent error.

Recommended Action    This error message is informational. No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-FCIP_FTA_PERM_ERR: Permanent Error, ERA [hex] rcvd CH FCID: 
[hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] sense_byte[2,6]: 
[[hex], [hex]]. 

Explanation    FCIP-FTA received a permanent error.

Recommended Action    This error message is informational. No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-IPS_CRYPTO_FIPS_FAILED: IPS module [dec] has failed FIPS tests. 
FIPS info - [chars]. 

Explanation    FIPS error occurred in the IPS module.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-IPS_FIPS_TEST_FAILED: IPS FIPS compliance test failed. 

Explanation    IPS FIPS compliance test failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-IPS_HIFN_CRYPTO_ENGINE_POST_FAILED: Crypto engine in the IPS 
module [dec] has failed POST tests. POST info - [chars]. 

Explanation    An error occurred in the crypto engine used in the IPS module.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-3-IPS_INGRESS_PERR: Parity error on dma-bridge ingress. Count: 
[dec]. 

Explanation    Parity error occured in dma-bridge ingress direction.

Recommended Action    Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    IPS-3-ISLB_CFS_CLEAR_FAILED: [chars]. 

Explanation    An error occurred while clearing the CFS lock. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_COMMIT_FAILED: [chars]; [chars]. 

Explanation    An error occurred while issuing a CFS commit. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_CONFIG_FAILED: [chars]; [chars]. 

Explanation    An error occurred while distributing the CFS config data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Error Message    IPS-3-ISLB_CFS_LOCK_FAILED: [chars]. 

Explanation    An error occurred while acquiring the CFS lock. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_ACTIVATION_FAILED: [chars]; [chars]. 

Explanation    An error occurred while activating a merged configuration. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_CLEARED: [chars]. 

Explanation    Merge has been cleared.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_COMMIT_FAILED: [chars]; [chars]. 

Explanation    An error occurred while committing the CFS merged config data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_CONFIG_FAILED: [chars]; [chars]. 

Explanation    An error occurred while distributing the CFS merge config data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_FAILED: [chars]; [chars]. 

Explanation    An error occurred while merging iSLB CFS fabrics. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-3-ISLB_CFS_MERGE_PRECOMMIT_FAILED: [chars]; [chars]. 

Explanation    An error occurred while pre-committing merge data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGE_REQ_REJECTED: [chars]. 

Explanation    Merge request rejected.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_PWWN_RESV_CLAIM_FAILED: [chars]. 

Explanation    PWWN reservation claim failed. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_MERGING_CONFIG_DB_FAILED: [chars]; [chars]. 

Explanation    An error occurred while merging the config data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Error Message    IPS-3-ISLB_CFS_PRECOMMIT_FAILED: [chars]; [chars]. 

Explanation    An error occurred while pre-committing data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_CFS_PWWN_RESV_RELEASE_FAILED: [chars]. 

Explanation    PWWN reservation release failed. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-3-ISLB_CFS_UNLOCK_FAILED: [chars]. 

Explanation    An error occurred while releasing the CFS lock. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-3-ISLB_CFS_VRRP_DIST_FAILED: [chars]. 

Explanation    An error occurred while distributing the VRRP CFS runtime data. The reason for the failure is listed in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_ZONE_ACTIVATION_FAILED: iSLB zoneset activation returned 
[hex] for VSAN [dec]. 

Explanation    iSLB zone set activation failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-3-ISLB_ZONE_ACTIVATION_RETRY: iSLB zoneset activation returned 
[hex] for VSAN [dec]. 

Explanation    iSLB zone set activation failed because the zone server was busy.

Recommended Action    Retry the iSLB zone set activation.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-3-ISLB_ZONE_NO_ACTIVE_ZONESET: iSLB zonset activation returned 
[hex] for VSAN [dec]. 

Explanation    iSLB zone set activation failed because there is no active zone set.

Recommended Action    Activate a zone set in the specified VSAN and retry.

Introduced Cisco MDS SAN-OS Release 3.0(1).

IPS-4

Error Message    IPS-4-FCIP_FTA_CFG_MISMATCH: [chars]: Mismatch in FCIP FICON Tape 
Acceleration configuration with peer. 

Explanation    The FCIP FICON Tape Acceleration configuration does not match the peer's configuration.

Recommended Action    Adjust the FCIP FICON tape acceleration configuration to be consistent with the peer.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-4-FCIP_FTA_VSAN_UPDATE_WARNING: FCIP FICON tape acceleration VSAN 
update had an error ([chars]) on interface [chars] causing a flap of the interface. 

Explanation    The FCIP FICON tape acceleration VSAN configuration experienced an error when disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and re-enabled as a result of this error to ensure data integrity.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-4-FCIP_LICENSE_BIND_FAILED: Bind failed for [chars] due to [chars] 
for license failure; configuration accepted but bind failed. 

Explanation    The FCIP configuration was accepted but the FCIP interface did not bind to a physical interface because the appropriate license was not available. If a license becomes available in the future, this FCIP interface will bind to a physical interface automatically.

Recommended Action    Check the license state using either the CLI show license usage command or a similar Fabric Manager procedure. Acquire the necessary FCIP license.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

IPS-5

Error Message    IPS-5-FCIP_BIND_FAILED: Bind failed for [chars] due to [chars] for 
[chars]. 

Explanation    The FCIP interface bind to the Ethernet port failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-FCIP_FTA_ALREADY_OFF: FTA Already Off, [chars] VSAN: [hex]. 

Explanation    FTA is already turned off.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_FTA_ALREADY_ON: FTA Already ON, [chars] VSAN: [hex]. 

Explanation    FTA is already turned on.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_CB_DOWN: FTA [chars] is DOWN. 

Explanation    FTA is down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_CB_UP: FTA [chars], is UP. 

Explanation    FTA is up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_DISBAND_GRP_CMD: Disband Group message processed PGID: 
[chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP disbanded a group.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_ERA_90: ERA 90 rcvd CH FCID: [hex] CHI: [hex] CU FCID 
[hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP internal error generated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_EST_GRP_CMD: Path Group establised for PGID: [chars] 
CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP established a Path Group.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_FTA_INVALID_FRAME: INVALID FTA FRAME :[chars]. 

Explanation    Invalid FICON tape acceleration frame received.

Recommended Action    Informational message. No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS1: RSCN Cleanup Pass1 
[chars] FCID1: [hex] FCID2: [hex] VSAN: [hex]. 

Explanation    RSCN cleanup first pass is in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS2: RSCN Cleanup Pass2 
[chars] FCID1: [hex] FCID2: [hex] VSAN: [hex]. 

Explanation    RSCN cleanup second pass is in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_RESIGN_GRP_CMD: Resign group processed for PGID: 
[chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP resigned a group.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_RESP_3490: 3490 device discovered by FCIP CH FCID: 
[hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    Device type discovered is 3490.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_RESP_3590: 3590 device discovered by FCIP CH FCID: 
[hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    Device type discovered is 3590.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_RESP_NOT_TAPE: Non-tape device discovered by FCIP CH 
FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [hex]. 

Explanation    FCIP discovered a non-tape device.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_TURN_OFF_LAST_VSAN: FTA turned off for the Last VSAN, 
[chars] VSAN: [hex]. 

Explanation    FTA twas turned off for the last Vsan.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_TURN_OFF_NONLAST_VSAN: FTA turned off for the Non-Last 
VSAN, [chars] VSAN: [hex]. 

Explanation    FTA was turned off for the non-last Vsan.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-FCIP_FTA_TURN_ON: Turn ON FTA, [chars] VSAN: [hex]. 

Explanation    FTA was turned on.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_FTA_WARNING: FTA Warning :[chars]. 

Explanation    Generic FTA Warning.

Recommended Action    This error message is informational. No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPS-5-FCIP_IF_CR_DEL: Interface [chars] [chars]. 

Explanation    The FCIP interface was created or deleted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPS-5-FCIP_NUM_TCP_CONNS_MISMATCH: [chars]: configured for 2 tcp 
connections but currently operating with 1 connection. 

Explanation    The number of configured TCP connections do not match the number of connections currently up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-FCIP_RA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Read 
Acceleration capability with peer. 

Explanation    The FCIP Tape Read Acceleration capability does not match the peer configuration.

Recommended Action    Adjust the FCIP Tape Read Acceleration capability to be consistent with the peer.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_TA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape 
Acceleration configuration with peer. 

Explanation    The FCIP tape acceleration configuration does not match the configuration on the peer.

Recommended Action    Adjust the FCIP tape acceleration configuration to be consistent with the peer.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPS-5-FCIP_TA_ITL_MISMATCH: [chars]: Mismatch in FCIP Write/Tape 
Acceleration software capability with peer. 

Explanation    The FCIP Write/Tape Acceleration software capability does not match with peer's software capability.

Recommended Action    Fix the FCIP software to be consistent with the peer.

NPV-2-NPV_EXITED: NPV process exited in file [chars]

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    IPS-5-FCIP_TSTAMP_CHK_FAILED: [chars]: Timestamp check failed on 
ingressing frames. 

Explanation    The timestamp between local and remote sides exceeds the configured tolerance.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPS-5-IPS_TCP_PORT_IN_USE: Cannot bringup interface [chars], local 
port already in use. 

Explanation    FCIP and iSCSI interfaces are trying to use the same local port.

Recommended Action    Use different ports.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-ISCSI_BAD_DATA_DIGEST_CRC: iSCSI ingress data digest error from 
initiator [chars] alias [chars] S_ID [hex] to D_ID [hex]. 

Explanation    iSCSI ingress data digest CRC failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI session down from initiator 
[chars] alias [chars] ip [chars] to target [chars], reason: [chars]. 

Explanation    iSCSI session goes down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-ISCSI_CONN_DOWN_BATCH: [chars]: [dec] iSCSI sessions failed in 
last [chars], reason: [chars]. 

Explanation    The listed number of iSCSI sessions were down during the last interval for the reason shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IPS-5-ISCSI_CONN_UP: [chars]: iSCSI session up from initiator [chars] 
alias [chars] ip [chars] to target [chars]. 

Explanation    An iSCSI session has come up and reached full-feature phase.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSI initiator [chars] alias 
[chars] ip [chars] target [chars]. FC session failed over to port [chars]. 

Explanation    The FC session for the iSCSI session failed over to a newly active port.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-ISCSI_SB_GET_TGT: iSCSI SB get [dec] targets, initiator [chars] 
alias [chars] ip [chars]. 

Explanation    iSCSI FCNS query response.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-ISCSI_SESSION_CREATE_REDIRECT: [chars]: iSCSI Session initiator 
[chars] target [chars] redirected to [chars]/[chars]. 

Explanation    iSCSI session create was redirected.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-ISCSI_SESSION_REDIRECT_TIMEOUT: iSCSI Session initiator [chars] 
to [chars] redirected to [chars] timeout. 

Explanation    iSCSI session redirect has timed out.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IPS-5-ISLB_CFS_SESSION_CLEARED:  CFS Session Cleared. 

Explanation    CFS session has been cleared by a user.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-FCIP_WA_CFG_MISMATCH: [chars]: Mismatch in FCIP Write 
Acceleration configuration with peer. 

Explanation    The FCIP write acceleration configuration does not match the configuration on the peer.

Recommended Action    Fix the FCIP write acceleration configuration to be consistent with the peer.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPS-5-IPS_IPACL_LOG_MSG: [chars]. 

Explanation    The message lists details of the packet dropped due to ACLs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI   session down from [chars] 
[chars] to target [chars], reason: [chars]. 

Explanation    The iSCSI session going down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-ISCSI_CONN_UP: [chars]: iSCSI   session up from [chars] [chars] 
to target: [chars]. 

Explanation    The iSCSI session came up and reached full-feature phase.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSI

Explanation    The Fibre Channel session for the iSCSI session failed over to newly active port.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS-5-ISCSI_SESSION_CREATE_FAILURE: [chars]: iSCSI   Session 
initiator [chars] target [chars] create failed. [chars]. 

Explanation    The iSCSI session create failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPS-5-ISCSI_SESSION_DESTROY_FAILURE: [chars]: iSCSI   Session 
initiator [chars] target [chars] destroy failed. [chars]. 

Explanation    The iSCSI session destroy failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS-5-PORT_IPCFG_FAILED: Cannot configure ip address for interface 
[chars]. 

Explanation    Cannot configure IPS port IP address.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IPS-5-SB_MGR_CORE_FAILED: Ethernet Processing core [chars] failed due 
to [chars]. 

Explanation    Ethernet processing core failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-SFRAME_ENTITY_ID_MISMATCH: [chars]: special frame profile id 
mismatch. 

Explanation    A special frame was received, and the destination profile ID does not match the local profile ID.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-SFRAME_FABRIC_WWN_MISMATCH: [chars]: special frame fabric wwn 
mismatch. 

Explanation    A special frame was received, and the source or destination fabric WWN does not match the local destination or source fabric WWN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-SFRAME_IF_ADMIN_DOWN: [chars]: special frame recvd if down. 

Explanation    A special frame was received and the interface is administratively down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-SFRAME_IF_NOT_ENABLED: [chars]: special frame not enabled. 

Explanation    A special frame was received and the interface special frame configuration is disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-5-SFRAME_INVALID_NONCE: [chars]: special frame response has 
invalid nonce for FCIP. 

Explanation    Special frame response has a different server-specified data string (nonce) than was originally sent in the special frame.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-SFRAME_NOT_RECV: [chars]: special frame was not received by 
passive-side FCIP. 

Explanation    Special frame was not received by the passive-side of the FCIP TCP tunnel within given time period.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-SFRAME_RESP_MISMATCH: [chars]: special frame response has byte 
mismatch for FCIP. 

Explanation    Special frame response has a mismatch in one of the bytes from what was sent from the FCIP special frame sender.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IPS-5-SFRAME_RESP_NOT_RECV: [chars]: special frame response was not 
received by active-side FCIP. 

Explanation    Special frame response was not received by the active-side of the FCIP TCP tunnel within given time period.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

IPS-7

Error Message     IPS-7-ISCSI_FCNS_QUERY_REQ: return [hex], wait [dec], VSAN [dec], 
Init: [chars]. 

Explanation    The iSCSI Fibre Channel name server (FCNS) query details are shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-7-ISCSI_FCNS_QUERY_RESP: result [hex], [dec] tgts, wait [dec], 
Init: [chars]. 

Explanation    The iSCSI Fibre Channel name server (FCNS) query response details are shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-7-ISCSI_SB_GET_TGT: iSCSI   SB get [dec] tgts, Init: [chars] 
[chars]. 

Explanation    The iSCSI Fibre Channel name server (FCNS) query response details are shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IPS-7-ISNS_SVR_ERR_RESPONSE: isns server returned following error code 
on isns request for interface [chars] : [dec]. 

Explanation    The Internet Storage Name Service (iSNS) server returned an error for a register or deregister request. For select error codes, the ISNS client would retry and re-register all target nodes corresponding to the interface.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

IPS_SB_MGR Messages

This section contains the IP Storage services sibyte manager (IPS_SB_MGR) messages.

IPS_SB_MGR-SLOT#-2

Error Message    IPS_SB_MGR-SLOT#-2-NODE_CORE_NOT_RESPONDING: [Node [dec], Core 
[dec]]: Not responding to heartbeats, state=[hex]. 

Explanation    The node is not sending heartbeats periodically.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-NODE_NOT_RESPONDING: [Node [dec], Core [dec]] : Not 
responding to heartbeats. 

Explanation    Node manager is not receiving heartbeat responses from the node.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-NODE_REIMAGE_PREPARE_FAIL: [Node [dec]]: Disk 
formatting failed during node install. 

Explanation    There was a problem during the partitioning of the disk and creation of the file systems during the node install.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-PORT_SOFTWARE_FAILURE: Port software failure, 
module [dec] port [dec]. 

Explanation    The software servicing the data path on the port failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IPS_SB_MGR-SLOT#-2-SB0_REIMAGE_PREPARE_FAIL:Sibyte0 reimage disk 
formatting failed. 

Explanation    There was a problem during the partitioning of the disk and the creation of file systems during reimage.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-SB1_REIMAGE_PREPARE_FAIL:Sibyte1 reimage disk 
formatting failed. 

Explanation    There was a problem during the partitioning of the disk and the creation of file systems during reimage.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-SIBYTE_CORE0_NOT_RESPONDING:Sibyte [dec] Core0 is 
not responding to heartbeats, state=0x[hex]. 

Explanation    The code of core-0 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte manager.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-2-SIBYTE_CORE1_NOT_RESPONDING:Sibyte [dec] Core1 is 
not responding to heartbeats, state=0x[hex]. 

Explanation    The code of core-1 is not incrementing heartbeats.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-2-SIBYTE_NOT_RESPONDING:Sibyte is not responding to 
heartbeats. 

Explanation    The code of either core-0 or core-1 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte manager.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

IPS_SB_MGR-SLOT#-3

Error Message     IPS_SB_MGR-SLOT#-3-COMP_FAILURE: Heartbeat failure in compression 
engine (error [hex]). 

Explanation    The compression engine did not respond to heartbeats because of some failure. The compression engine will be restarted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IPS_SB_MGR-SLOT#-3-CRYPTO_FAILURE: Heartbeat failure in encryption 
engine (error [hex]). 

Explanation    The encryption engine did not respond to heartbeats because of some failure. The encryption engine will be restarted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IPS_SB_MGR-SLOT#-3

Error Message     IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_ADD_ON: svc-node[dec] image 
is not compatible with svclc image. 

Explanation    The SAN Volume Controller (SVC) image on the node is not compatible with the add-on image running on the line card.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_CURRENT: svc-node[dec] image 
is not compatible with current node image. 

Explanation    The new SAN Volume Controller (SVC) image is not compatible with the SVC image currently running on the node.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_SUP: svc-node[dec] image is 
not compatible with system image. 

Explanation    The SAN Volume Controller (SVC) image on the node is not compatible with the supervisor image.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    PS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_ADD_ON:Sibyte0 is not 
compatible with add on. 

Explanation    The code of sibyte0 is not compatible with the add-on image running on the line card.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_SB:Sibyte0 is not compatible 
with current sibyte image. 

Explanation    The new code of sibyte0 is not compatible with the running sibyte image.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-4-SB0_NOT_COMPAT_WITH_SUP:Sibyte0 is not compatible 
with supervisor. 

Explanation    The code of sibyte0 is not compatible with the supervisor image.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_ADD_ON:Sibyte1 is not 
compatible with add on. 

Explanation    The code of sibyte1 is not compatible with the add on image running on the line card.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_SB:Sibyte1 is not compatible 
with current sibyte image. 

Explanation    The new code of sibyte1 is not compatible with the running sibyte image.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-4-SB1_NOT_COMPAT_WITH_SUP:Sibyte1 is not compatible 
with supervisor. 

Explanation    The code of sibyte1 is not compatible with the supervisor image.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

IPS_SB_MGR-SLOT#-6

Error Message     IPS_SB_MGR-SLOT#-6-SBMGR_EVENT: Sbmgr event: [chars]. 

Explanation    This is an event log of the sibyte manager relating to a port or node.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IPS_SB_MGR-SLOT#-6-SBMGR_SDWRAP:Sbmgr sdwrap: [chars]. 

Explanation    This is for messages from the sibyte manager on the line card to the supervisor system messages log.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IPS_SB_MGR-SLOT#-6-SIBYTE_NOT_RESPONDING: Sibyte is not responding to 
heartbeats. 

Explanation    The code of either core-0 or core-1 is not incrementing heartbeats periodically or heartbeat responses from sibyte are not making through to the sibyte manager.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

IPsec Messages

This section contains the IPsec messages.

IPsec-2

Error Message    IPSEC-2-IPSEC_INIT: IPSec initialization of [chars] [chars] 

Explanation    IPsec initialization failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPSEC-2-IPSEC_SPD_OVERFLOW_DUE_TO_ACL:  SPD Overflow on interface due 
to IP ACL [chars] bound to  crypto map [chars] [dec]. 

Explanation    Modifying IP-ACL caused the security policy database on the interface to overflow. The IP-ACL filter was not applied to the security policy database.

Recommended Action    Remove the IP-ACL change.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IPsec-3

Error Message    IPSEC-3-14_2_MODULE_PACKETS_DROPPED: [chars]: packets were dropped in 
the module. 

Explanation    The 14/2-port Multiprotocol Services (14/2-MPS) module dropped packets.

Recommended Action    Enter the show ipsec internal crypto-acc interface gigabit <slot/port> CLI command or use a similar Fabric Manager/Device Manager procedure to collect drop statistics. If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(2b).

Error Message    IPSEC-3-IPSEC_FIPS_TEST_FAILED: IPSEC FIPS compliance test failed. 

Explanation    IPsec FIPS compliance test failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IPSEC-3-IPSEC_MSG_SEND_FAILURE:  failed to send [chars] to sap [dec]: 
[chars]. 

Explanation    Failed to send a message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IPsec-5

Error Message     IPSEC-5-IPSEC_CMS_IF_ACL_UPDATED:  IP ACL [chars] updated while 
Crypto map [chars] [dec]  bound to interface(s). 

Explanation    IP-ACL was updated while it is mapped to a crypto map that is bound to an interface(s).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IPSEC-5-IPSEC_DISABLED: IPSec Disabled. 

Explanation    IPsec is disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPSEC-5-IPSEC_DISABLED_LIC_EXPIRED: IPSec Disabled due to License 
Expiry. 

Explanation    IPsec is disabled because the license expired.

Recommended Action    Install an updated, valid license to continue using this feature.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IPSEC-5-IPSEC_ENABLED: IPSec Enabled. 

Explanation    IPsec is enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IPsec-6

Error Message    IPSEC-6-IPSEC_TUNNEL_CREATED: [chars]: IPSec tunnel created: local_ip: 
[chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: 
[chars]/[chars]. 

Explanation    IPsec tunnel created.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPSEC-6-IPSEC_TUNNEL_DELETED: [chars]: IPSec tunnel deleted: local_ip: 
[chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: 
[chars]/[chars]. 

Explanation    IPsec tunnel deleted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPSEC-6-IPSEC_TUNNEL_REKEYED: [chars]: IPSec tunnel rekeyed: local_ip: 
[chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: 
[chars]/[chars]. 

Explanation    IPsec tunnel rekeyed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IPsec-7

Error Message     IPSEC-7-IPSEC_SA_CREATED: [chars]: IPSec SA created: local_ip: 
[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]). 

Explanation    An IPsec security association (SA) was created.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IPSEC-7-IPSEC_SA_DELETED: [chars]: IPSec SA deleted: local_ip: 
[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]), reason: [chars]. 

Explanation    An IPsec security association (SA) was deleted.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Recommended Action    No action is required.

Error Message     IPSEC-7-IPSEC_SA_REKEYED: [chars]: IPSec SA rekeyed: local_ip: 
[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]). 

Explanation    An IPsec security association (SA) was rekeyed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IPSEC-7-IPSEC_TUNNEL_REKEYED: [chars]: IPSec tunnel rekeyed: local_ip: 
[chars], peer_ip: [chars], id: [dec], traffic:: local: [chars]/[chars], remote: 
[chars]/[chars]. 

Explanation    IPsec tunnel rekeyed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

ISAPI Messages

This section contains the intelligent switch application programming interface (ISAPI) messages.

ISAPI-SLOT#-0

Error Message    ISAPI-SLOT#-0-ILC_EMERG: [chars]. 

Explanation    This is an intelligent switch API emergency software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-0-INVISTA_EMERG: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-0-NSP_EMERG: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-0-SSM_EMERG: [chars]. 

Explanation    This is an intelligent switch API emergency software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    ISAPI-SLOT#-0-SSM_EMERG: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

ISAPI-SLOT#-1

Error Message     ISAPI-SLOT#-1-ILC_ALERT: [chars]. 

Explanation    This is an intelligent switch API alert software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-1-INVISTA_ALERT: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-1-NSP_ALERT: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-1-SSM_ALERT: [chars]. 

Explanation    This is an intelligent switch API alert software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    ISAPI-SLOT#-1-SSM_ALERT: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

ISAPI-SLOT#-2

Error Message     ISAPI-SLOT#-2-ILC_CRIT: [chars]. 

Explanation    This is an intelligent switch API critical software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-2-INVISTA_CRIT: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-2-NSP_CRIT: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-2-SSM_CRIT: [chars]. 

Explanation    This is an intelligent switch API critical software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    ISAPI-SLOT#-2-SSM_CRIT: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

ISAPI-SLOT#-3

Error Message     ISAPI-SLOT#-3-ILC_ERROR: [chars]. 

Explanation    This is an intelligent switch API error software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-3-INVISTA_ERROR: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-3-NSP_ERROR: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-3-SSM_ERROR: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-3-SSM_ERROR: [chars]. 

Explanation    This is an intelligent switch API error software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ISAPI-SLOT#-4

Error Message     ISAPI-SLOT#-4-ILC_WARN: [chars]. 

Explanation    This is an intelligent switch API warning software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-4-INVISTA_WARN: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-4-NSP_WARN: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-4-SSM_WARN: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-4-SSM_WARN: [chars]. 

Explanation    This is an intelligent switch API warning software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ISAPI-SLOT#-5

Error Message     ISAPI-SLOT#-5-ILC_NOTICE: [chars]. 

Explanation    This is an intelligent switch API notice software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-5-INVISTA_NOTICE: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-5-NSP_NOTICE: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-5-SSM_NOTICE: [chars]. 

Explanation    Isapi software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-5-SSM_NOTICE: [chars]. 

Explanation    This is an intelligent switch API notice software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ISAPI-SLOT#-6

Error Message     ISAPI-SLOT#-6-ILC_INFO: [chars]. 

Explanation    This is an intelligent switch API informational software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-6-INVISTA_INFO: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-6-NSP_INFO: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-6-SSM_INFO: [chars]. 

Explanation    This is an intelligent switch API informational software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ISAPI-SLOT#-7

Error Message     ISAPI-SLOT#-7-ILC_DEBUG: [chars]. 

Explanation    This is an intelligent switch API debug software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    ISAPI-SLOT#-7-INVISTA_DEBUG: [chars]. 

Explanation    Isapi-invista software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-7-NSP_DEBUG: [chars]. 

Explanation    Isapi-nsp software messages.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    ISAPI-SLOT#-7-SSM_DEBUG: [chars]. 

Explanation    This is an intelligent switch API debug software message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

ISNS Messages

This section contains the Internet Storage Name Service (ISNS) messages.

ISNS-2

Error Message    ISNS-2-ISNS_CFS_OPERATION_FAILED: iSNS CFS [chars] failed. 

Explanation    iSNS CFS operation failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    ISNS-2-ISNS_INIT: iSNS initialization of [chars] [chars]. 

Explanation    Internet Storage Name Service (ISNS) initialization failed. ISNS is automatically restarted.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IVR Messages

This section contains the inter-VSAN routing (IVR) messages.

IVR-2

Error Message    IVR-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars] 
was lost in the middle of an active CFS session. Abort the CFS session and re-enter 
the configuration changes. 

Explanation    Due to port flaps (enable and disable of the VSAN), link outages, switch restarts and so on, a CFS peer switch of IVR was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync. with this peer. We recommend that you discard this CFS session using ivr abort command and then re-enter the configuration changes. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Recommended Action    No action is required.

Error Message    IVR-2-DEVICE_FCID_REWRITE_FAILURE: Failure while programming FCID 
rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able 
to communicate with its peer devices. 

Explanation    Device failed to program the FC ID rewrite entries; this probably occurred because the hardware ran out of FC ID rewrite entries. This can happen if there are too many devices in an inter-VSAN routing (IVR) zone, or there are too many local VSANs in the VSAN topology.

Recommended Action    Reduce the number of devices involved in inter-VSAN routing (IVR) in the active IVR zone set. Also, reduce the number of redundant transit VSANs, if any.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-2-DEVICE_ON_WRONG_NATIVE_AFID_VSAN: Device with port WWN [chars] 
(FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other 
VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec]. 

Explanation    Device has come online on a different AFID/VSAN from the configured native AFID/VSAN, or the device does not satisfy unique domain criteria.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-2-DEVICE_ON_WRONG_NATIVE_VSAN: Device with port WWN [chars] 
(FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for 
Inter-VSAN zoning) because domain [hex] exists in VSAN [dec]. 

Explanation    Device has come online on a VSAN different from the configured native VSAN, or the device does not satisfy unique domain criteria.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IVR-2-DEVICE_STATE_INCOMPATIBLE_WITH_NAT_MODE: State for device with 
port WWN [chars] could not be restored because it was incompatible with the current 
NAT mode([dec]). This probably happened because NAT mode was modified without 
completely deactivating the active IVR zoneset. 

Explanation    This can happen if the Network Address Translation (NAT) mode is modified without completely deactivating the active inter-VSAN routing (IVR) zone set.

Recommended Action    Reboot the switch.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-2-DEVICE_VSAN_REWRITE_FAILURE: Failure while programming VSAN 
rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able 
to communicate with its peer devices. 

Explanation    Device failed to program the VSAN rewrite entries, probably because the hardware ran out of VSAN rewrite entries. This can happen if there are too many devices in an inter-VSAN zone or too many local VSANs in the VSAN topology.

Recommended Action    Reduce the number of domains involved in IVR by moving the members of the active IVR zone set to fewer switches. Also, reduce the number of redundant transit VSANs, if any.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IVR-2-DOMAIN_DISALLOWED_IN_INTEROP: Device with port WWN [chars] and 
FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] 
is disallowed in the interop mode for VSAN [dec]. 

Explanation    VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. Refer to the Cisco MDS 9000 Family CLI Configuration Guide or Cisco MDS 9000 Family Fabric Manager Configuration Guide for details on the domain range limitations.

Recommended Action    Change the domain of the switch to which this IVR zone member is connected so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using the fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fcdomain's allowed-domains interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IVR-2-DOMAIN_UNAVAILABLE: Device with port WWN [chars] and FCID 
[chars] may not be able to participate in Inter-VSAN zone since domain [dec] is 
already assigned in VSAN [dec]. 

Explanation    Device with the port WWN and FC ID shown in the error message may not be able to participate in the inter-VSAN zone because the domain shown is already assigned in a VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IVR-2-INTEROP_MODE_2_OR_3_BF_FAILED: [chars] VSAN [dec] Virtual 
Domain [chars]. 

Explanation    Build fabric failed in VSAN [dec]. The build fabric was initiated to remove an unused virtual domain from the fcdomain list in that VSAN. The virtual domain still remains in the fcdomain list and hence it would not be available in that VSAN for assignment.

Recommended Action    Perform a manual build fabric using fcdomain's interface if you would like to remove the unused virtual domain(s) from the fcdomain list.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     IVR-2-INTEROP_MODE_2_OR_3_RDI_FAILED: VSAN [dec], requested domain 
[chars], received domain [chars] sWWN [chars]. Return Code [chars]. 

Explanation    Request domain identifier (RDI) failed to allocate virtual domain in the VSAN. Received another domain instead, as shown in the error message. IVR-members connected to a third-party switch may not participate in IVR communications. It is likely that the domain requested in the IVR RDI command is already in use.

Recommended Action    Reassign the domains so that the domain requested by RDI does not overlap any existing domain in that VSAN.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message    IVR-2-IVR_ASSERTION_FAILED: Unexpected assertion failure in File 
[chars] at Line [dec]. 

Explanation    The inter-VSAN routing code shows an assertion failure.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-2-IVR_DISABLE_FAILED: Inter-VSAN Routing disable failed for 
reason: [chars]. 

Explanation    Inter-VSAN routing disable failed for the reason shown in the error message. Cleanup might not have completed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IVR-2-IVZS_ACTIVATION_FAILED_RETRYING: Inter-VSAN zoneset activation 
failed in VSAN [dec] : [chars]. retrying after [dec] seconds. 

Explanation    Inter-VSAN zone set activation failed in the listed VSAN. This could be an intermittent, regular zone set activation error. The activation will be retried after the number of seconds listed in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IVR-2-NO_LICENSE_SHUTDOWN: Inter-VSAN Routing is shutting down. 

Explanation    License required for continued IVR operation is not available. IVR is shutting down.

Recommended Action    Install the appropriate license for IVR services and then enable IVR again.

Introduced Cisco MDS SAN-OS Release2.0(1b).

Error Message     IVR-2-NO_LICENSE_WARNING: Inter-VSAN Routing would shutdown in [dec] 
seconds. 

Explanation    License required for continued IVR operation is not available. Unless the required license is installed, IVR will shut down in the number of seconds shown in the error message. IVR configurations will be lost.

Recommended Action    Install the appropriate license for IVR services within the shown seconds to continue uninterrupted operation.

Introduced Cisco MDS SAN-OS Release2.0(1b).

Error Message    IVR-2-PERSISTENT_VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the 
configured persistent virtual domain/fcid could not be assigned. 

Explanation    This can happen if the virtual domain/FC ID configured by the user is already in use (either by IVR or a switch) or not allowed because of the interop mode or allowed domain list configured.

Recommended Action    Verify that the configured virtual domain/FC ID is allowed and available for use.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IVR-2-VIRTUAL_DOMAIN_CONFLICT: In VSAN [dec] virtual domain [dec] from 
native VSAN [dec] conflicts with native VSAN [dec] for the same virtual domain. 

Explanation    The currently advertised virtual domain in the VSAN shown in the error message is native to different VSAN. This switch has learned of a device that is a member of the active IVR zone and has the same domain ID, but belongs to a different native VSAN. This device is not advertised in that VSAN until the domain conflict is resolved.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    IVR-2-VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the internally 
generated FCID conflicts with fcid assigned to WWN [chars]. Please configure fcid 
for WWN [chars] too. 

Explanation    This can happen if the virtual domain/FCID internally configured is already in use by another active device.

Recommended Action    Assign a different persistent virtual FCID.

Introduced Cisco MDS SAN-OS Release 3.2(1).

IVR-3

Error Message    IVR-3-ACL_ERROR: ACL API, [chars], failed with error [hex]. 

Explanation    IVR invoked the ACL API and received an error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-ACL_PERMIT_ENTRY_ERROR: ACL permit entry update on interface 
[chars] failed for reason: [chars]. 

Explanation    ACL could not program permit entries for IVR traffic.The error message describes the interface named and the system error message from ACL. IVR traffic coming from the interface may be dropped.

Recommended Action    If the problem persists, contact your support representative. If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IVR-3-ACL_PLOGI_ENTRY_ERROR: PLOGI capture entry update in slot [dec] 
failed for reason: [chars]. 

Explanation    ACL could not program IVR. Port login (PLOGI) could not be programmed. The error message describes the line card slot number, and the error detected. PLOGI and its response may be dropped because the IVR process cannot capture those frames.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message    IVR-3-AFID_CONFLICT: [chars]. 

Explanation    AFID configuration is different at different IVR-enabled switches in the same VSAN.

Recommended Action    Change either the AFID configuration (auto mode) or the VSAN topology configuration (user mode) to make it consistent.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-3-CFS_INVALID_PAYLOAD_RECEIVED: Inter-VSAN process received 
invalid payload from CFS. 

Explanation    Inter-VSAN process received invalid payload from CFS.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    IVR-3-CLEAR_FAILED: [chars]. 

Explanation    An error occurred while clearing the lock. The reason for the failure is shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IVR-3-COMMIT_FAILED: [chars]. 

Explanation    An error occurred while issuing a CFS commit. The reason for the failure is shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IVR-3-COMMIT_PARTIALLY_FAILED: [chars]. 

Explanation    An error occurred while committing the configuration. Configuration could not be committed on some switches. The reason for the failure is that the configuration is inconsistent in the fabric.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-3-COMMIT_REJECTED: [chars]. 

Explanation    The commit request received from the remote switch is rejected. The reason for the failure is shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-3-DDAS_LOCK_TIMER_EXPIRED: IVR database lock is released, as 
device-alias commit/abort notification is not received in the expected time frame. 

Explanation    When device-alias sends the validation request, the IVR database is locked and a timer is started. For any reason, if device-alias commit/abort notification is not received within the expected time frame, the lock timer expires and the lock is released. If device-alias commit notification is received after the lock is released, the changes are not applied and this could cause inconsistency between IVR and device-alias.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IVR-3-DEVICE_NOT_PRESENT_IN_FB_DB_FICON: Device with port WWN [chars] 
could not be exported to VSANs [chars] because its native switch is not present 
in the current active fabric binding database of those VSANs. 

Explanation    This happens if FICON is enabled on VSANs and native switch of device with port WWN is not present in the current active fabric binding database of those VSANs. This is a requirement for FICON compliance.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IVR-3-DEVICE_ON_WRONG_NATIVE_AFID_VSAN: Device with port WWN [chars] 
(FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other 
VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec]. 

Explanation    Device has come online on a AFID/VSAN different from the configured native AFID/VSAN.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IVR-3-DEVICE_ON_WRONG_NATIVE_VSAN: Device with port WWN [chars] 
(FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for 
Inter-VSAN zoning) because domain [hex] exists in VSAN [dec]. 

Explanation    Device has come online on a VSAN different from the configured native VSAN or the device does not satisfy unique domain criteria.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-3-DM_ERROR: Domain Manager API, [chars], failed with error [hex]. 

Explanation    IVR invoked the domain manager API and received an error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-DOMAIN_DISALLOWED_IN_INTEROP: Device with port WWN [chars] and 
FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] 
is disallowed in the interop mode for VSAN [dec]. 

Explanation    VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. Refer to the Cisco MDS 9000 Family CLI Configuration Guide or Cisco MDS 9000 Family Fabric Manager Configuration Guide for details on the domain range limitations.

Recommended Action    Change the domain of the switch to which this IVR zone member is connected so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fcdomain allowed-domains' interface.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-3-DOMAIN_UNAVAILABLE: Device with port WWN [chars] and FCID 
[chars] may not be able to participate in Inter-VSAN zone since domain [dec] is 
already assigned in VSAN [dec]. 

Explanation    Device with the named port WWN and FC ID may not be able to participate in Inter-VSAN zone because the named domain is already assigned in the named VSAN.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-3-FC2_ERROR: FC2 API [chars] failed with error [hex] for [chars]. 

Explanation    IVR invoked a Fibre Channel Layer 2 (FC-2) API for a socket and received an error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-3-INTERNAL_ERROR: Internal error: [chars]. 

Explanation    The IVR process encountered a general error, one that does not fall in any of the categories. The error message describes the error and its context.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-3-FCID_REWRITE_REQUEST_TO_ACL_FAILED: fcid rewrite [chars] 
request vsan [dec] did [chars] sid [chars] failed:[chars]. 

Explanation    This happens either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IVR-3-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED: qos iod undrop request 
vsan [dec] did [chars] failed:[chars]. 

Explanation    This happens either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-3-IVZ_ACTIVATION_FAILED: Inter-VSAN zoneset [chars] activation 
failed. 

Explanation    Inter-VSAN zone set activation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-IVZ_ACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars] 
activation failed in VSAN [dec]. 

Explanation    Inter-VSAN zone set activation failed in the VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-IVZ_DEACTIVATION_FAILED: Inter-VSAN zoneset [chars] 
deactivation failed. 

Explanation    Inter-VSAN zone set deactivation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-IVZ_DEACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars] 
deactivation failed in VSAN [dec]. 

Explanation    Inter-VSAN zone set deactivation failed in the VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-3-LOCK_FAILED: [chars]. 

Explanation    An error occurred while acquiring the lock. The reason for the failure is listed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IVR-3-MERGE_FAILED: [chars]. 

Explanation    An error occurred while merging the configuration. The reason for the failure is shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IVR-3-MTS_ERROR: MTS message transmission failed with error [dec]. 

Explanation    IVR process unsuccessfully tried to send a messaging and transaction service (MTS) message. The messaging and transaction service (MTS) error number is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-NS_ERROR: FCNS API, [chars], failed with error [hex]. 

Explanation    IVR invoked the Fibre Channel name server (FCNS) API and received an error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars] 
failed with error [hex]. 

Explanation    IVR read the saved configuration and encountered an error while rebuilding the runtime configuration. The error message describes the configuration that the process tried to restore and describes the system error code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-PSS_ERROR: PSS operation [chars] returned error: [hex]. 

Explanation    A persistent storage service error occurred. The error message specifies the context where the failure occurred and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for 
[chars] failed with error [hex]. 

Explanation    IVR read the saved runtime database and encountered an error while rebuilding the runtime database. The error message describes the runtime database that the process tried to restore and shows the system error code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-RIB_ERROR: RIB API, [chars], failed with error [hex]. 

Explanation    IVR invoked the Routing Information Base (RIB) API and received an error code. The error message describes the API and the error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-3-ROUTE_REQUEST_TO_ACL_FAILED: route [chars] request vsan [dec] 
domain [dec] failed:[chars]. 

Explanation    This happens when either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-3-TOPOLOGY_COMPUTATION_FAILED: Inter-VSAN Topology computation 
has failed due to: [chars]. 

Explanation    Inter-VSAN topology has failed because of the reason shown in the message. Possible reasons are (a) number of AFID/VSAN combination is more than the maximum supported value of 128, or (b) number of IVR-enabled switches is more than the maximum supported value of 128.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is 
received. 

Explanation    IVR process received an unexpected message and transaction service (MTS) event. The MTS opcode is specified in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-3-UNLOCK_FAILED: [chars]. 

Explanation    An error occurred while releasing the lock. The reason for the failure is shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IVR-3-VSAN_SEGMENTED: [chars]. 

Explanation    VSAN is segmented. VSAN is removed from the topology graph and therefore inter-VSAN traffic cannot flow through this VSAN.

Recommended Action    To correct the segmentation, use one of the following methods:

Modify one of the VSAN IDs so it is no longer a segmented VSAN.

Add a different AFID to one of the VSANs so the AFID/VSAN combination is unique.

Bring up a link in the segmented VSAN that goes between the two segments so that they are no longer segmented.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-3-ZS_POLICY_IS_DENY_NO_ACTIVE_ZS: Default zone behavior policy 
changed to deny on VSAN [dec] and there is no active zoneset. 

Explanation    The default zone behavior is changed to deny, and there is no active zone set. Inter-VSAN zone members may not be able to communicate in this VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     IVR-3-ZS_POLICY_IS_PERMIT_NO_FORCE: Default zone behavior policy 
changed to permit on VSAN [dec] and the force option is off. 

Explanation    The default zone behavior is changed to permit and the force option is off. Inter-VSAN zone set activation in this VSAN has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-3-ZS_POLICY_IS_PERMIT_ZS_DEACTIVATED: Default zone behavior 
policy changed to permit on VSAN [dec] and regular zoneset deactivated. 

Explanation    Default zone behavior is changed to permit and the regular zone set is deactivated. Inter-VSAN zone members may not be able to communicate.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4b).

IVR-4

Error Message    IVR-4-AUTO_TOPOLOGY_UPDATE_DISCARDED: [chars]. 

Explanation    The auto-topology update is discarded because of conflicts.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING: fcid rewrite 
[chars] request vsan [dec] did [chars] sid [chars] failed:[chars]. Retrying the 
request again. 

Explanation    This happens when either the line cards are being upgraded or the ACL experienced an error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-4-PERSISTENT_VIRTUAL_DOMAIN_MERGE_CONFLICT: [chars]. 

Explanation    Merge failed because of a conflict in the persistent virtual domain configuration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IVR-4-PERSISTENT_VIRTUAL_FCID_MERGE_CONFLICT: [chars]. 

Explanation    Merge failed because of a conflict in the persistent virtual FC ID configuration.

Recommended Action    Check the configuration and resolve merge issues.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IVR-4-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED_AND_RETRYING: qos iod 
undrop request vsan [dec] did [chars] failed:[chars]. Retrying the request again. 

Explanation    This happens when either line cards are being upgraded or the ACL experienced an error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     IVR-4-ROUTE_REQUEST_TO_ACL_FAILED_AND_RETRYING: route [chars] 
request vsan [dec] domain [dec] failed:[chars]. Retrying the request again. 

Explanation    This happens when either line cards are being upgraded or the ACL experienced an error while processing the request.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-4-UNKNOWN_NATIVE_VSAN: Unknown native VSAN for the virtual domain 
[dec] in VSAN [dec] local native VSAN for the same virtual domain is [dec]. 

Explanation    Could not determine the native VSAN of the currently advertised virtual domain in the VSAN shown in the error message. This switch has learned of a device that is a member of the active IVR zone, has the same domain ID, but belongs to another native VSAN.This device is not advertised in that VSAN until the native VSAN information is resolved.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

IVR-5

Error Message    IVR-5-FCID_NAT_MODE_ACTIVATED: FCID network address translation (NAT) 
mode has been activated. 

Explanation    FC ID Network Address Translation (NAT) mode has been activated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-5-FCID_NAT_MODE_DEACTIVATED: FCID network address translation 
(NAT) mode has been deactivated. 

Explanation    FC ID Network Address Translation (NAT) mode has been deactivated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-5-IVR_ASSERTION_FAILED: Unexpected assertion failure in File 
[chars] at Line [dec]. 

Explanation    A software assertion occurred in the IVR code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    IVR-5-IVZS_ACTIVATION_RETRYING: Inter-VSAN zoneset activation failed 
with error [hex] in VSAN [dec]. retrying after [dec] seconds. 

Explanation    Inter-VSAN zone set activation failed with VSAN shown in the error message. This could be an intermittent regular zone set activation error. The activation retried in the number of seconds shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Error Message     IVR-5-IVZS_WAITING_FOR_LOWEST_SWWN: Waiting for lowest switch WWN 
Inter-VSAN enabled switch in VSAN [dec]. 

Explanation    This switch does not have the lowest switch world wide name (sWWN) in the VSAN. Only the inter-VSAN enabled switch with the lowest sWWN can add the inter-VSAN zones to the regular active zone set in a VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     IVR-5-IVZ_ACTIVATED: Inter-VSAN zoneset [chars] activated. 

Explanation    Inter-VSAN zone set activated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_ACTIVATED_VSAN: Inter-VSAN zoneset [chars] activated in 
VSAN [dec]. 

Explanation    Inter-VSAN zone set activated in the VSAN shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_CLEANUP_DONE: Inter-VSAN clean-up is done. 

Explanation    Inter-VSAN related configuration might not be cleaned up before exiting.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_CLEANUP_DONE_BY_TIMER: Inter-VSAN clean-up is not done 
after waiting for 5 minutes. 

Explanation    Inter-VSAN related configuration might not be cleaned up before the IVR process is terminated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(2a).

Error Message     IVR-5-IVZ_DEACTIVATED: Inter-VSAN zoneset [chars] deactivated. 

Explanation    Inter-VSAN zone set deactivated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_DEACTIVATED_VSAN: Inter-VSAN zoneset [chars] deactivated in 
VSAN [dec]. 

Explanation    Inter-VSAN zone set deactivated in the VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_PARTIALLY_ACTIVATED: Inter-VSAN zoneset [chars] partially 
activated. 

Explanation    Inter-VSAN zone set activated.

Recommended Action    Check if it is successful in all VSANs by entering the show ivr zone set status command or use a similar Fabric Manager/Device Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     IVR-5-IVZ_PARTIALLY_DEACTIVATED: Inter-VSAN zoneset [chars] partially 
deactivated. 

Explanation    Inter-VSAN zone set deactivated.

Recommended Action    Check if it is successful in all VSANs by entering the show ivr zone set status command or use a similar Fabric Manager/Device Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    IVR-5-LICENSE_CHECKIN_FAILED: Failed to checkin [chars] license: 
Err=[chars]. 

Explanation    Failed to check in the listed license.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    IVR-5-SERVICE_GROUP_ACTIVATED: Inter-VSAN Service Group has been 
activated. 

Explanation    Inter-VSAN Service Group has been activated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IVR-5-SERVICE_GROUP_DEACTIVATED: Inter-VSAN Service Group has been 
deactivated. 

Explanation    Inter-VSAN Service Group has been deactivated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    IVR-5-VSAN_NO_LONGER_SEGMENTED: [chars]. 

Explanation    VSAN is no longer segmented. VSAN is added back to the topology graph and inter-VSAN traffic can now flow through this VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-5-VSAN_TOPOLOGY_ACTIVATED: Inter-VSAN Topology has been activated. 

Explanation    Inter-VSAN topology has been activated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

IVR-6

Error Message    IVR-6-DRAV_ASYNC_DOMAIN_RELEASE: [chars]. 

Explanation    A virtual domain finite state machine (DRAV FSM) has unconditionally released a domain because of a conflict after a fabric merge. The details are shown in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-6-DRAV_CRITICAL_RETRY_EXCEED: [chars]. 

Explanation    An attempt is being made to resend the DRAV FSM frames. The details are shown in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-6-DRAV_DOMAIN_ALLOC: Virtual domain [dec] for Native AFID: [dec] 
Native VSAN [dec]. 

Explanation    A virtual domain (indicated in the message) has been reserved for a device with native AFID and native VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message    IVR-6-DRAV_DOMAIN_RELEASE: Virtual domain [dec] for Native AFID: [dec] 
Native VSAN [dec]. 

Explanation    A virtual domain representing a native AFID/VSAN (DRAV) on a finite state machine (FSM) has unconditionally released a domain because of a conflict, a domain was unused, or a release request was received from the owner. The domain is indicated by the name shown in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-6-DRAV_TOPO_UPDATE: [chars]. 

Explanation    DRAV FSM topology has been updated as indicated by the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     IVR-6-LICENSE_VALID: A valid license for inter-VSAN Routing has been 
obtained. 

Explanation    A valid license for inter-VSAN routing has been obtained.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

IVR-7

Error Message    IVR-7-CFS_REQ_RCVD: [chars]. 

Explanation    CFS request is received. The WWN of the switch that originated this request and the rr-token of the request are provided in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-7-CFS_RESP_SENT: [chars]. 

Explanation    CFS response is sent. The rr-token of the corresponding request and the status are provided in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    IVR-7-IVR_ASSERTION_FAILED: Unexpected assertion failure in File 
[chars] at Line [dec]. 

Explanation    An internal assertion failed in inter-VSAN routing. This is a low-level debug message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

LC-FCFWD Messages

This section contains the line card Fibre Channel forwarding (LC-FCFWD) messages.

LC-FCFWD-3

Error Message     LC-FCFWD-3-ERROR: [chars]. 

Explanation    LC-FCWFD encountered an error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

LC-SPAN Messages

This section contains the line card switched port analyzer (LC-SPAN) messages.

LC-SPAN-3

Error Message     LC-SPAN-3-ERROR: [chars]. 

Explanation    The line card switched port analyzer (LC-SPAN) manager encountered an error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

LC_CFG Messages

This section contains the line card configuration manager (LC_CFG) messages.

LC_CFG-SLOT#-2

Error Message    LC_CFG-SLOT#-2-LC_CFG_ABORT: ERROR: lc_cfg_mgr aborted registration 
(code [dec]). 

Explanation    Lc_cfg_mgr exited on linecard.

Recommended Action    No action is required.

Error Message    LC_CFG-SLOT#-2-LC_CFG_EXITED: ERROR: lc_cfg_mgr exited on linecard 
(code [dec]). 

Explanation    The line card configuration manager exited on the line card.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    LC_CFG-SLOT#-2-LC2_CPU_ERRORS: [chars], Total IC [dec], DC [dec], Tag 
[dec], MBit [dec], SBit [dec], I30 [dec]. 

Explanation    The line card configuration manager detected CPU Cache errors.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

LC_PORT_CHANNEL Messages

This section contains the line card PortChannel (LC_PORT_CHANNEL) messages.

LC_PORT_CHANNEL-SLOT#-0

Error Message     LC_PORT_CHANNEL-SLOT#-0-HW_FAILURE: fatal error in configuring 
[chars]: [chars]. 

Explanation    Fatal hardware error in the PortChannel configuration.

Recommended Action    Reset the module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     LC_PORT_CHANNEL-SLOT#-0-IDX_FULL: D_IDX table full (current [dec], 
new [dec], total [dec]). 

Explanation    Major error in the PortChannel configuration.

Recommended Action    Reset the module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

LC_PORT_CHANNEL-SLOT#-3

Error Message     LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_ERROR: [chars]. 

Explanation    General error in the PortChannel configuration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 3.0(1).

Error Message     LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_IDXMAP_FAILURE: could not 
lookup port index for interface [chars]. 

Explanation    Could not look up the port index.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 3.0(1).

LC_PORT_MGR Messages

This section contains the line card port manager (LC_PORT_MGR) messages.

LC_PORT_MGR-SLOT#-2

Error Message    LC_PORT_MGR-SLOT#-2-LC_MTS_ERROR: An MTS error has occurred in 
([chars]) with the following conditions: opc=[dec] ssap=[hex] dsap=[hex] 
syserr=[hex]. 

Explanation    This is a software error in message communications between two applications.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

LC_RDL Messages

This section contains the line card remote domain lookup (LC_RDL) messages.

LC_RDL-3

Error Message     LC_RDL-3-SYSLOG_ALLOC_FAIL: : [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) memory allocation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec]. 

Explanation    The line card remote domain lookup (LC_RDL) experienced the context error shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_ERR: : [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) syslog errors are shown in the error message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_EXIT: : [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) exited on errors.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) initialization failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_MTS_ERR: : [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) messaging and transaction service (MTS) errors occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-3-SYSLOG_MTS_REG_FAILED: : [dec] [dec]. 

Explanation    The line card remote domain lookup (LC_RDL) context error occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

LC_RDL-6

Error Message     LC_RDL-6-SYSLOG_DEBUG_1: : [chars] [hex]. 

Explanation    The line card remote domain lookup (LC_RDL) debug logs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-6-SYSLOG_DEBUG_2: : [chars] [hex]. 

Explanation    The line card remote domain lookup (LC_RDL) debug logs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-6-SYSLOG_INFO: : [chars]. 

Explanation    The line card remote domain lookup (LC_RDL) debug logs.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LC_RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec]. 

Explanation    The line card remote domain lookup (LC_RDL) context error occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

LICMGR Messages

This section contains the license manager (LICMGR) messages.

LICMGR-2

Error Message     LICMGR-2-LOG_LIC_GRACE_EXPIRED:  Grace period expired for feature 
[chars]. 

Explanation    The unlicensed feature has exceeded its grace period. Applications using this license will be shut down immediately.

Recommended Action    Install the license file to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    LICMGR-2-LOG_LIC_EXIT:  License manager exiting: [chars]. 

Explanation    License manager is now exiting. The reason for the exit is shown in the message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

LICMGR-3

Error Message     LICMGR-3-LOG_LICAPP_NO_LIC:  Application [chars] running without 
[chars] license, shutdown  in [dec] days. 

Explanation    Application [chars1] has not been licensed. The application will work for a grace period of [dec] days after which it will be shut down unless a license file for feature [chars2] is installed.

Recommended Action    Install the license to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Error Message     LICMGR-3-LOG_LICAPP_TOO_MANY_LIC: Only [dec] licenses are supported 
for [chars] feature, where as [dec] licenses are installed. 

Explanation    More licenses are installed than allowed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(3).

Deprecated Cisco MDS SAN-OS Release 1.3(4b).

Error Message     LICMGR-3-LOG_LIC_FILE_MISSING:  License file(s) missing for feature 
[chars]. 

Explanation    One or more license files for the feature shown in the error message are missing and must be reinstalled.

Recommended Action    Install the license to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-3-LOG_LIC_INVALID_HOSTID:  Invalid license hostid VDH=[chars] 
for feature [chars]. 

Explanation    The feature has a license with an invalid license host ID. This can happen if a supervisor card with licensed features for one switch is installed on another switch.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-3-LOG_LIC_LICENSE_EXPIRED:  Evaluation license expired for 
feature [chars]. 

Explanation    The feature has exceeded its evaluation time period. The feature will be shut down after a grace period.

Recommended Action    Install the license to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-3-LOG_LIC_MESSAGE_ERROR:  could not handle message: [chars] of 
type [dec] from addr [dec]:[dec]. 

Explanation    Could not handle an interprocess communications (IPC) message, of the type shown in the error message, sent by a component running on the shown node and service access point (SAP).

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     LICMGR-3-LOG_LIC_NO_LIC:  No license(s) present for feature [chars]. 
Application(s)  shutdown in [dec] days. 

Explanation    The feature has not been licensed. The feature will work for a grace period, then any applications using the feature will be shut down.

Recommended Action    Install the license to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-3-LOG_LIC_SERVER_DOWN: License Server Down [dec]. 

Explanation    A connection to the license server could not be created.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     LICMGR-3-LOG_LIC_SPROM_LIC:  Feature [chars] issued [dec] licenses 
without a valid license file. 

Explanation    The feature has been licensed the number of times shown in the error message without a valid license file. This means one or more license files are missing for the feature and must be reinstalled.

Recommended Action    Install the license to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-3-LOG_LIC_TOO_MANY_LIC:  Only [dec] licenses are supported for 
[chars] feature, where as [dec] licenses are installed. 

Explanation    More licenses are installed than allowed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(3a).

LICMGR-6

Error Message     LICMGR-6-LOG_LICAPP_EXPIRY_WARNING:  Application [chars] evaluation 
license [chars] expiry in [dec] days. 

Explanation    Application will exceed its evaluation time period days and will be shut down unless a permanent license for the feature is installed.

Recommended Action    Install the license file to continue using the feature.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-6-LOG_LIC_FEATURE_CLEARED: Cleared [dec] license(s) for 
feature [chars]. 

Explanation    Uninstalled license(s) for the feature shown in the error message.

Recommended Action    Enter the show license usage command or use a similar Fabric Manager/Device Manager procedure to verify this license feature removal.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LICMGR-6-LOG_LIC_FEATURE_INSTALLED: Installed [dec] license(s) for 
feature [chars]. 

Explanation    Installed license(s) for the feature shown in the error message.

Recommended Action    Enter the show license usage command or use a similar Fabric Manager/Device Manager procedure to verify this license feature installation.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LICMGR-6-LOG_LIC_INVALID_HOSTID: Feature [chars] has an invalid 
license hostid. 

Explanation    The feature has an invalid license host ID. This can happen if a supervisor card with licensed features for one switch is installed on another switch.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-6-LOG_LIC_LICENSE_CLEARED: Cleared license file [chars]. 

Explanation    Uninstalled the named license file.

Recommended Action    Enter the show license command or use a similar Fabric Manager/Device Manager procedure to verify this license removal.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     LICMGR-6-LOG_LIC_LICENSE_CLEARED_ALL:  Cleared all licenses. 

Explanation    Cleared all license files.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     LICMGR-6-LOG_LIC_LICENSE_EXPIRED:  Evaluation license expired for 
feature [chars]. 

Explanation    The feature exceeded its evaluation time period and was shut down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 1.3(1).

Error Message     LICMGR-6-LOG_LIC_LICENSE_EXPIRY_WARNING:  Evaluation license for 
feature [chars] will expire in [dec] days. 

Explanation    The feature will exceed its evaluation time period in days and will be shut down.

Recommended Action    Install an appropriate license for this feature.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     LICMGR-6-LOG_LIC_LICENSE_INSTALLED: Installed license file [chars]. 

Explanation    Installed the named license file.

Recommended Action    Enter the show license command or use the similar Fabric Manager/Device Manager procedure to verify this license installation.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

MAC Messages

This section contains the MAC messages.

MAC-SLOT#-2

Error Message    MAC-SLOT#-2-MAC_INFO: [chars]

Explanation    MAC Informational message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

MCAST Messages

This section contains the multicast (MCAST) messages.

MCAST-2

Error Message    MCAST-2-SHUTDOWN: Process shutting down: [chars]. 

Explanation    The multicast process is shutting down.

Recommended Action    The action depends on the situation. The multicast process can shut down gracefully because of a system restart (in which case no action needs to take place) or because of a failure. The message associated with the syslog should be self explanatory. If the process can restart properly, there is no immediate harm for the system stability and the suggested action is to report the syslog event together with an explanation of the operations most recently performed on the system. If the component cannot restart properly, contact your support representative. If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

MCAST-4

Error Message     MCAST-4-ERROR: [chars]. 

Explanation    Multicast encountered a generic error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

MCAST-5

Error Message     MCAST-5-BAD_MSG: Received bad message: [chars]. 

Explanation    Multicast has received a malformed or unrecognizable message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MCAST-5-START: Process has been started. 

Explanation    The multicast process has started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

MODULE Messages

This section contains the module messages.

MODULE-2

Error Message    MODULE-2-LCM_UPGRADE_DONE_GENERAL_FAIL: Upgrade ready message fails 
seq [dec]. 

Explanation    Upgrade ready message failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-2-LCM_UPGRADE_OVER_FAIL: Upgrade over message returned [dec] 
[hex] for SAP [dec]. 

Explanation    Upgrade done message failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-2-LCM_UPGRADE_READY_FAIL: Upgrade ready message returned [dec] 
[hex] for SAP [dec]. 

Explanation    Upgrade ready message failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL: Upgrade ready message fails 
seq [dec]. 

Explanation    Upgrade ready message failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-2-MOD_DIAG_FAIL: Module [dec] reported failure on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error 
[hex]). 

Explanation    The module reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.

Recommended Action    Collect information about the module by entering the show module internal all module [decimaldigit] CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec]. 

Explanation    The module failed to download a new image from the supervisor module.

Recommended Action    Collect module information by entering the show module internal all module [decimaldigit] command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-2-MOD_FAIL: Initialization of module [dec] failed. 

Explanation    The module reported a failure during the initialization phase and will be powered down.

Recommended Action    Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-2-MOD_MAJORSWFAIL: Module [dec] reported a critical failure in 
service [chars]. 

Explanation    A critical failure caused by the service occurred in the module. The module restarted automatically.

Recommended Action    Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message    MODULE-2-MOD_MINORSWFAIL: Module [dec] reported a failure in service 
[chars]. 

Explanation    A non-critical failure in the service occurred on the module. The module will not be restarted.

Recommended Action    Collect module information by entering the show module internal all module command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     MODULE-2-MOD_NOT_ALIVE: Module [dec] not responding... resetting. 

Explanation    The module is not replying to the hello message. The module manager will reset the module.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-2-MOD_REGFAILED: Registration failed for module [dec]. 

Explanation    The module sent the registration message notifying a failure.

Recommended Action    Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-2-MOD_SOMEPORTS_FAILED: Module [dec] reported failure on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]). 

Explanation    Module reported a failure in the runtime diagnostic because of a failure in some of the ports.

Recommended Action    Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     MODULE-2-MOD_UNKNOWN: Module type [[dec]] in slot [dec] is not 
supported. 

Explanation    The software card ID of module [dec] is not supported by the supervisor.

Recommended Action    Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure. Update SPROM contents by entering the update sprom command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-2-XBAR_DIAG_FAIL: Xbar [dec] (serial: [chars]) reported failure 
on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device 
error [hex]). 

Explanation    The xbar in the slot reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.

Recommended Action    Collect information about the module by issuing the show module internal all xbar CLI command or by using a similar Fabric Manager procedure.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     MODULE-2-XBAR_FAIL: Initialization of xbar [dec] (serial: [chars]) 
failed. 

Explanation    Xbar reported a failure during the initialization phase and will be powered down.

Recommended Action    Collect information about the module by issuing the show module internal all xbar <modulenumber> CLI command or by using a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (serial: [chars]) reported 
failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] 
(error [hex]). 

Explanation    Xbar reported a failure in the runtime diagnostic because of failure in some of the ports.

Recommended Action    Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     MODULE-2-XBAR_UNKNOWN: Xbar type [[dec]] in slot [dec] is not 
supported. 

Explanation    The software card ID of xbar is not supported by the supervisor.

Recommended Action    Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

MODULE-3

Error Message     MODULE-3-MOD_SRG_NOT_COMPATIBLE: Module [dec] firmware is not 
compatible with supervisor, downloading new image. 

Explanation    The software version of the module is not supported by the supervisor module.

Recommended Action    Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

MODULE-4

Error Message    MODULE-4-MOD_WARNING: Module [dec] reported warnings on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error 
[hex]). 

Explanation    Module reported a warning in the runtime diagnostic because of a failure in some of the ports.

Recommended Action    Collect module information by entering the show module internal all module CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-4-XBAR_WARNING: Xbar [dec] (serial: [chars]) reported warnings 
on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device 
error [hex]). 

Explanation    Xbar reported a warning in the runtime diagnostic because of failure in some of the ports.

Recommended Action    Collect information about the module by issuing the show module internal all xbar [decimaldigit] CLI command or by using a similar Fabric Manager procedure.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

MODULE-5

Error Message     MODULE-5-ACTIVE_SUP_OK: Supervisor [dec] is active. 

Explanation    Module is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-5-MOD_DIAG_FAIL: Module [dec] reported failure on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]). 

Explanation    The module in the slot reported a failure in the runtime diagnostic. Module manager will power cycle the module.

Recommended Action    Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

Error Message    MODULE-5-MOD_OK: Module [dec] is online (serial: [chars]). 

Explanation    Module named is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    MODULE-5-MOD_MINORSWFAIL: Module [dec] reported a failure in service 
[chars]. 

Explanation    A non-critical failure caused by the service occurred in the module. The module will not be reset.

Recommended Action    Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

Error Message    MODULE-5-MOD_OK: Module [dec] is online (serial: [chars]). 

Explanation    Module named is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    MODULE-5-MOD_OK: Module [dec] is online. 

Explanation    Module is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-5-MOD_PURGE_CONFIG: Purging the configuration for module [dec]. 

Explanation    Notification is sent to remove module configurations.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-5-MOD_REINIT: Re-initializing module [dec]. 

Explanation    Module reported a failure during the initialization phase and will be reinitialized.

Recommended Action    Collect module information by entering the show module_internal all module command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-5-MOD_RESTART: Module [dec] is restarting after image 
download. 

Explanation    Module completed image download and restarted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-5-MOD_SOMEPORTS_FAILED: Module [dec] reported failure on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]). 

Explanation    Module reported a failure in the runtime diagnostic because of the failure of some of the ports.

Recommended Action    Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

Error Message    MODULE-5-MOD_STARTUP_CFG_MISMATCH: The startup configuration cannot be 
applied to a different module type for module [dec] (serial: [chars]). [chars] 
module is replacing [chars]. 

Explanation    The startup configuration for the module contains information about a different type of module instead of containing information about the current one.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     MODULE-5-MOD_WARNING: Module [dec] reported warnings on ports 
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]). 

Explanation    Module [dec] reported a warning in the runtime diagnostic because the failure of some of the ports.

Recommended Action    Collect module information by entering the show module internal all module [dec] command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Deprecated Cisco MDS SAN-OS Release 2.0(1b).

Error Message     MODULE-5-STANDBY_SUP_OK: Supervisor [dec] is standby. 

Explanation    Module is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    MODULE-5-XBAR_OK: Xbar [dec] is online (serial: [chars]). 

Explanation    Xbar is ready to be configured and to switch traffic.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    MODULE-5-XBAR_REINIT: Re-initializing xbar [dec] (serial: [chars]). 

Explanation    Xbar reported a failure during the initialization phase and will be rebooted.

Recommended Action    Collect information about the module by issuing the show module internal all xbar <modulenumber> CLI command or by using a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

MODULE-6

Error Message    MODULE-6-MOD_PURGE_CONFIG: Purging the configuration for module [dec]. 

Explanation    Notification is sent to remove module configurations.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    MODULE-6-MOD_REG_OK: Registration succeeded for module [dec]. 

Explanation    Module sent a successful registration message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NASB Messages

This section contains the Network-Accelerated Serverless Backup (NASB) messages.

NASB-SLOT#-5

Error Message    NASB-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN :[dec] VT pWWN :[chars] DPP 
died. 

Explanation    The data path processor (DPP) associated with the virtual target failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     NASB-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars] 
VT Activate failed. 

Explanation    The activate step for a virtual target failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     NASB-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN :[dec] VT pWWN :[chars] 
VT and NPort creation FAILED !!!. 

Explanation    The virtual target and N port creation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     NASB-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target : 
[chars] Deleted. 

Explanation    The virtual target in the associated VSAN is being destroyed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     NASB-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars] 
VSAN down. 

Explanation    The VSAN where the virtual target is configured is down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

NPC Messages

This section contains the N port creator (NPC) messages.

NPC-SLOT#-3

Error Message     NPC-SLOT#-3-LOG_NPC_ERR:  Nonrecoverable error: [chars]. 

Explanation    Errors caused the program to exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NPC-SLOT#-4

Error Message     NPC-SLOT#-4-LOG_NPC_WARNING:  Serious error: [chars]. 

Explanation    Serious errors that affect the all normal operations occurred.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NPC-SLOT#-5

Error Message     NPC-SLOT#-5-LOG_NPC_DEBUG:  Unexpected error: [chars]. 

Explanation    Unexpected errors occurred that affect some normal operations.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NPC-SLOT#-5-LOG_NPC_NVP_FSM:  Illegal event received: [chars]. 

Explanation    Illegal event received in N port creator virtual N port (NPC_NVP) finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NPC-SLOT#-5-LOG_NPC_VSAN_FSM:  Illegal event received: [chars]. 

Explanation    Illegal event received in the N port creator virtual N port (NPC_NVP) finite state machine (FSM).

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NPV Messages

This section contains the N-Port Virtualization(NPV) messages.

NPV-2

Following are critical-level NPV system log messages.

Error Message    NPV-2-NPV_DISABLE_FAILED: NPV could not disabled : [chars] [chars]. 

Explanation    NPM could not be disabled due to the reason specified.

Recommended Action    Try again.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-2-NPV_EXITED

Explanation    NPM process exited in file error system logs.

Recommended Action    .No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

NPV-3

Error Message    NPV-3-ACL_UPDATE_FAILED

Explanation    ACL update request initiated by the NPV process has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-F_RJT_SENT

Explanation    NPV Process sent a F_RJT frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-FC2_SEND_FAILED: [chars]. 

Explanation    NPV process could send an FC2 message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-FRAME_DISCARDED: [chars]. 

Explanation    NPV process discarded an FC2 frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-LCP_PROGRAMMING_FAILED: [chars]. 

Explanation    LCP programming request initiated by the NPV process has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-LS_RJT_SENT

Explanation    NPV Process sent a LS_RJT frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-LS_RJT_RCVD: [chars]. 

Explanation    NPV process received an LS_RJT frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-MALLOC_FAILED: [chars]. 

Explanation    An assertion failed in NPV code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-MTS_SEND_FAILED: [chars]. 

Explanation    NPV process could not send an MTS message.

Recommended Action    No action is required

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-NPIV_DISABLE_FAILED

Explanation    NPIV feature could not be disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-PORT_BRINGUP_FAILED

Explanation    NPV process has failed to bring up the port.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-PORT_REINIT_FAILED

Explanation    Port reinit request initiated by the NPV process has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-3-UNEXPECTED_EVENT: [chars]. 

Explanation    NPV process has received an unexpected event in the current state.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

NPV-5

Following are notification-level NPV system log messages:

Error Message    NPV-5-ASSERTION_FAILED

Explanation    An assertion failed in NPV code.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

NPV-6

Following are informational-level NPV system log messages:

Error Message    NPV-6-ABTS_SENT

Explanation    NPV process sent a ABTS frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-EXT_IF_SELECTED: [chars]. 

Explanation    NPV process has selected an external interface to forward either all frames received on a server interface or frames received from a specific port WWN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-LS_ACC_RCVD: [chars]. 

Explanation    NPV process received an LS_ACC frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-FDISC_RCVD

Explanation    NPV process received an FLOGI frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-FDISC_SENT

Explanation    NPV process sent an FDISC frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-FLOGI_RCVD

Explanation    NPV process received an FLOGI frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-LC_ACC_SENT

Explanation    NPV process sent a LS_ACC frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-LOGO_RCVD

Explanation    NPV process received an LOGO frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-LOGO_SENT

Explanation    NPV process sent a LOGO frame.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_NOTIF_RCVD

Explanation    NPV process received an MTS notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_NOTIF_SENT:[CHAR].

Explanation    NPV sent an MTS notification.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_REQ_RCVD

Explanation    NPV process received an MTS request.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_REQ_SENT

Explanation    NPV process received an MTS request.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_RESP_RCVD

Explanation    NPV process received an MTS response.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-MTS_RESP_SENT

Explanation    NPV process sent an MTS response.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-NPIV_DISABLED: [chars]. 

Explanation    NPIV feature has been disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-NPIV_ENABLED: [chars]. 

Explanation    NPIV feature has been enabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    NPV-6-SERVER_PROXY_LOGO_SENT

Explanation    NPV process sent a LOGO frame to core switch.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.2(1).

NTP Messages

This section contains the Network Time Protocol (NTP) messages.

NTP-2

Error Message    NTP-2-NTP_SYSLOG_CRIT_ERR: : [chars]. 

Explanation    A critical error occurred in NTP.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1.(2).

Error Message    NTP-2-NTP_SYSLOG_INIT_FAIL: : [chars] [chars]. 

Explanation    Network Time Protocol (NTP) initialization failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC[dec] for [chars]. 

Explanation    NTP did not receive response from the linecard for the request sent.

Recommended Action    No action is required.

NTP-3

Error Message     NTP-3-NTP_SYSLOG_ALLOC_FAIL: : [chars]. 

Explanation    Network Time Protocol (NTP) syslog allocation failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NTP-3-NTP_SYSLOG_ERR: : [chars]. 

Explanation    Network Time Protocol (NTP) syslog error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NTP-3-NTP_SYSLOG_ERR_EXT: : [chars] [dec]. 

Explanation    Network Time Protocol (NTP) syslog error exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NTP-3-NTP_SYSLOG_MTS_ERR: : [chars]. 

Explanation    Network Time Protocol (NTP) messaging and transaction service (MTS) error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NTP-6

Error Message     NTP-6-NTP_SYSLOG_CREATED: : [chars]; Slot No: [dec]. 

Explanation    Network Time Protocol (NTP) syslog created.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NTP-6-NTP_SYSLOG_EXIT: : [chars]. 

Explanation    Network Time Protocol (NTP) syslog exit.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     NTP-6-NTP_SYSLOG_WARN: : [chars]. 

Explanation    Network Time Protocol (NTP) syslog warning.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

NVP Messages

This section contains the virtual N port (NVP) messages.

NVP-6

Error Message     NVP-6-NVP_INFO: [chars]. 

Explanation    virtual N port (NVP) daemon informational message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     NVP-6-STARTING: deamon started. 

Explanation    The virtual N port (NVP) daemon successfully started.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

NVP-SLOT# Messages

This section contains the virtual N port slot (NVP-SLOT#) messages.

NVP-SLOT#-2

Error Message     NVP-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused 
critical error please reboot ILC. 

Explanation    The listed component caused a critical error.

Recommended Action    Restart the line card.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

PLATFORM Messages

This section contains the platform messages.

PLATFORM-0

Error Message     PLATFORM-0-CHASSIS_CLKSWITCH: Hardware clock switched to redundant 
clock-[dec]. 

Explanation    Clock module on chassis detected a failure and switched to the redundant clock module.

Recommended Action    Enter the show platform internal info command to collect more information or use a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-0-CHASSIS_CLKSW_MODULE_RESET: Modules reset due to clock 
switch. 

Explanation    The chassis clock source has been switched and all Generation 1 line cards will be reset. The system will automatically continue using a redundant clock module.

Recommended Action    Replace the failed clock module.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch. 

Explanation    Chassis clock source has failed and system will be reset. System will automatically start using the redundant clock module.

Recommended Action    Replace the failed clock module during the next maintenance window.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-FAIL_REMOVED: Fan module removed before [dec] seconds. 

Explanation    Fan module was removed. This could lead to temperature alarms.

Recommended Action    Replace the fan module immediately.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-MOD_TEMPMAJALRM: Module [dec] reported major temperature 
alarm. 

Explanation    Module in the slot exceeded a major temperature threshold.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-MOD_TEMPRECOVER: Module [dec] recovered from major 
temperature alarm. Minor temperature alarm pending. 

Explanation    Module recovered from a major temperature threshold. Minor threshold still exceeded.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-MOD_TEMPSHUTDOWN: Module [dec] powered down due to major 
temperature alarm. 

Explanation    Module shut down because temperature exceeded major threshold.

Recommended Action    Enter show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-0-SUP_SPROM_ERROR: Unable to read SPROM for Sup in slot [dec]. 

Explanation    The supervisor in the slot named was not able to read its SPROM.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-0-SUP_WRONGSLOTNUM: Supervisor powered up in WRONG SLOT:[dec] 
(Serial number [chars]). 

Explanation    The supervisor is coming up in wrong slot.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED: Failed to load linecard module 
drivers. 

Explanation    Failed while trying to load drivers.

Recommended Action    Image is possibly corrupt. Load a different image.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-SYS_RESET: [chars] System shutdown in [dec] seconds. 

Explanation    System shut down will occur in the number of seconds shown in the error message.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-0-SYS_SHUTDOWN: System shutdown in [dec] seconds due to major 
temperature alarm. 

Explanation    System shut down in seconds because of temperature exceeding major threshold.

Recommended Action    Use the showenvtemperature CLI command to collect more information.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-0-MDS9124: System shutdown in [dec] seconds due to less than 
4 fans operating. 

Explanation    System shutdown in seconds because of less than 4 fans operating.

Recommended Action    Enter a show env fan command to collect more information.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    PLATFORM-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in [dec] seconds 
due to fan removal. 

Explanation    System shut down will occur in the number of seconds shown because the fan has been removed.

Recommended Action    Enter the show env fan CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-0-SYS_SUP_DRIVER_LOAD_FAILED: Failed to load supervisor 
module drivers. 

Explanation    Failed while trying to load drivers.

Recommended Action    Image is possibly corrupt. Load a different image.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-0-XBAR_CARD_CLK_FAIL: Xbar card in slot:[dec] (Serial number 
[chars]) encountered clock failure. 

Explanation    The xbar in the slot named encountered clock failure.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-0-XBAR_CARD_INCOMPAT_CHASSIS: Xbar card in slot:[dec] (Part 
number [chars]) Incompatible with backplane chassis Part Num:[chars]. 

Explanation    The xbar in the slot named is incompatible with backplane chassis.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-0-XBAR_WRONGSLOTNUM: Xbar powered up in WRONG SLOT:[dec] 
(Serial number [chars]). 

Explanation    The xbar in the slot named powered up in wrong slot.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLATFORM-1

Error Message     PLATFORM-1-CASA_FAN_FAIL: Fan module [dec] Failed. 

Explanation    Fan module failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action    Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PLATFORM-1-FAN_FAIL: Fan module Failed. 

Explanation    Fan module failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action    Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-1-MDS9124_FAN_FAIL: Less than 4 required fans operating. 

Explanation    A fan module has failed leaving fewer than four total fans operating. This can lead to overheating and temperature alarms.

Recommended Action    The fan needs to be replaced. Use the show platform internal info CLI command to collect more information.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    PLATFORM-1-MOD_PWRDENY: Module [dec] cannot be powered up due to 
insufficient power (Serial No. [chars]). 

Explanation    Available power in power supplies is not sufficient to power up the module.

Recommended Action    Verify available power and current usage by entering the show env power CLI command or by using a similar Fabric Manager/Device Manager procedure. Refer to power supply documentation in the relevant hardware installation guide to learn how to increase power supply capacity.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-1-MDS9124_FAN_FAIL: Less than 4 required fans operating. 

Explanation    Fan module has failed leaving fewer than four total fans operating. This can lead to overheating and temperature alarms.

Recommended Action    Use the show platform internal info CLI command to collect more information. Fan needs to be replaced.

Introduced Cisco MDS SAN-OS Release 3.1(1).

Error Message    PLATFORM-1-XBAR_PWRDENY: Xbar [dec] can not be powered up due to 
insufficient power (Serial number [chars]). 

Explanation    Available power in power supplies is not sufficient to power up the xbar.

Recommended Action    Verify available power and current usage with the show env power CLI command or by using a similar Fabric Manager procedure. See the power supply document on how to increase power supply capacity.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLATFORM-2

Error Message    PLATFORM-2-CASA_FAN_FAIL: Fan module [dec] Failed. 

Explanation    Indicated fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action    Use the show platform internal info CLI command to collect more information or use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-CASA_FAN_OK: Fan module [dec] ok. 

Explanation    Fan module indicated is ok.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-CHASSIS_CLKMODFAULTY: Chassis clock module [dec] faulty. 

Explanation    Indicated clock module on chassis is faulty or has been removed.

Recommended Action    Enter the show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module [dec] ok. 

Explanation    Clock module on chassis is functioning properly.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is 
clock-[dec]. 

Explanation    The current chassis clock source is indicated.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-FAN_OK: Fan module ok. 

Explanation    Fan module is ok.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-FANLET_FAN_FAIL: Failed Fanlets for Fan [dec] ([chars] 
fan) : [chars]. 

Explanation    The specified fans have failed. This can lead to overheating and temperature alarms.

Recommended Action    Use the show platform internal info CLI command to collect more information or use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-FANMOD_FAN_FAIL: Fan module [dec] ([chars] fan) Failed. 

Explanation    Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action    Use the show platform internal info CLI command to collect more information, or use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-FANMOD_FAN_OK: Fan module [dec] ([chars] fan) ok. 

Explanation    Fan module is ok.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_ALL_PWRDN_NOXBAR: All modules powered down due to 
non-availability of xbar modules. 

Explanation    All modules in a switch have been powered down because all xbar modules are offline.

Recommended Action    Use the CLI commands show module, show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] to collect more information if you suspect a module has been powered down because of errors. At least one exbar module has to be up for switch modules to function.

Introduced    Cisco MDS SAN-OS Release 3.0(1).'

Error Message     PLATFORM-2-MOD_PWRDENY: Module [dec] can not be powered up due to 
insufficient power (Serial number [chars]). 

Explanation    Available power in power supplies is not sufficient to power up the module.

Recommended Action    Verify available power and current usage with the show env power CLI command or by using a similar Fabric Manager procedure. See the power supply document on how to increase power supply capacity.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_PWRFAIL: Module [dec] failed to power up (Serial number 
[chars]). 

Explanation    The module in the slot named failed to power up.

Recommended Action    Use the show platform internal all module [decimaldigit] CLI command to collect more information.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to 
IDPROM read error. 

Explanation    The module cannot be powered up because of IDPROM read error.

Recommended Action    Use the CLI commands show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] and show sprom module[dec][dec] to read module IDPROM contents to collect more information.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_PWRUP_XBAR: Modules powered up due to xbar 
availability. 

Explanation    Modules powered up because at least one xbar module is online.

Recommended Action    No action needed.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_TEMPMINALRM: Module [dec] reported minor temperature 
alarm (sensor-index [dec] temperature [dec]). 

Explanation    Module has exceeded a minor temperature threshold.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-MOD_TEMPOK: [chars] recovered from minor temperature alarm. 
Sensor=[dec] Temperature=[dec] MinThreshold=[dec]. 

Explanation    The module in the slot named recovered from a major temperature threshold alarm.

Recommended Action    Enter a showenvtemperature command to collect more information.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-MOD_TEMPRECOVER: [chars] recovered from major temperature 
alarm. Minor temperature alarm pending. Sensor=[dec] Temperature=[dec] 
MAJThreshold=[dec] MinThresh=[dec]. 

Explanation    The module in the slot named recovered from a major temperature threshold alarm and the minor threshold is still exceeded.

Recommended Action    Enter a showenvtemperature command to collect more information.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-PFM_LC_BOOT_DEV_ABSENT: No bootflash found in Module 
[dec]. 

Explanation    No bootflash found.

Recommended Action    Put bootflash in the module and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: Bootflash access error in Module 
[dec]. 

Explanation    Bad bootflash/corrupted file system.

Recommended Action    Try to put in a known good bootflash in the module and try again.

Error Message     PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: BAD Bootflash found in Module [dec]. 

Explanation    Bad bootflash found.

Recommended Action    Put a good bootflash in the module and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PFM_LC_MOD_POWERED_DOWN: Module [dec] Powered Down. Module 
is not supported in this chassis. (Chassis Incompatible card). 

Explanation    Module has been powered down because the card is not supported in this chassis.

Recommended Action    Use the show module CLI command to see the power down reason, or use a similar Fabric Manager procedure.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-PFM_NETBOOT_DISABLE: Netboot for supervisor module in slot 
[dec] is disabled due to incompatible platform. 

Explanation    Standby supervisor failed to power up.

Recommended Action    Try to replace the standby supervisor.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-PFM_LC_NETBOOT_FAIL: Netboot for Module [dec] failed. 

Explanation    Netboot failed.

Recommended Action    Replace the BIOS in the module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-2-PFM_LC_REGISTRATION_FAIL: Could not register with Module 
[dec]. 

Explanation    Module registration failed.

Recommended Action    Replace the module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PFM_LOW_MEMORY_CONDITION: Module [dec] is running low on 
memory. %ld percent used. 

Explanation    Supervisor is running low on memory.

Recommended Action    Switchover.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    PLATFORM-2-PFM_LC_STATUS: Module [dec] powered up with [dec] status. 

Explanation    Status for module that failed registration.

Recommended Action    Replace the module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PFM_PWR_MGMT_EPLD_VER_MISMATCH: Module [dec] Pwr Mgmt Epld 
(Version-[dec]) needs to be upgraded. 

Explanation    the ELPD needs to be upgraded. Using a wrong version of EPLD can result in unexplained behaviour.

Recommended Action    Upgrade the power managment EPLD. Refer to the Cisco MDS 9000 Family CLI Configuration Guide.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PFM_STDBY_POWERUP_FAIL: standby supervisor failed to power 
up.

Explanation    Standby supervisor failed to power up.

Recommended Action    Replace the standby supervisor.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PS_CAPACITY_DIFFER: Detected power supplies with differing 
capacity. It is recommended to have same capacity for both powersupplies otherwise 
it may cause service disruptions. 

Explanation    Detected a power supply that has a different capacity than an the other power supply.

Recommended Action    Refer tot he Cisco MDS 9000 Family CLI Configuration Guide for information on increasing or decreasing power supply capacity and configuring power supplies. Use the show environment power and show platform internal info to collect more information.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PS_DETECT: Power supply [dec] detected but shutdown (Serial 
number [chars]). 

Explanation    Power Supply is detected but has been shut down.

Recommended Action    Use the CLI commands show environment power and show platform internal info to collect more information, or use similar Fabric Manager procedures.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PS_FAIL: Power supply [dec] failed or shutdown (Serial No. 
[chars]). 

Explanation    Power supply failed or has been shut down.

Recommended Action    Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager or Device Manager procedure to collect more information. See the power supply documentation in the relevant hardware installation guide to learn more on increasing or decreasing power supply capacity and configuring power supplies.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed. 

Explanation    Fan module in the named power supply has failed.

Recommended Action    Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PLATFORM-2-PS_FANOK: Fan in Power supply [dec] ok. 

Explanation    Fan module in the named power supply is operating.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PS_OK: Power supply [dec] ok (Serial number [chars]). 

Explanation    Power Supply is ok.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-PS_MISMATCH: Detected power supply [chars]. This reduces 
the redundant power available to the system and can cause service disruptions 
(Serial No. [chars]). 

Explanation    Detected a new power supply that has reduced capacity compared to a previous power supply.

Recommended Action    Refer to power supply document on increasing or decreasing power supply capacity, configuring power supplies, and so on. Enter the show environment power and show platform internal info CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PS_REMOVE: Power supply [dec] removed (Serial number 
[chars]). 

Explanation    Power Supply is removed.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message     PLATFORM-2-PS_REMOVE_LAST: Unexpected removal of last power supply 
[dec]. (Serial No. [chars]). 

Explanation    Unexpected removal of the only power supply in the system.

Recommended Action    Power supply unit may be faulty. Contact your customer support representative to replace the unit.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-2-PS_UNKNOWN: Detected an unknown power supply [dec] for 
CISCO MDS 9500/9200 Multilayer Switches ((Serial number[chars]). 

Explanation    Unable to determine power supply type. Default power supply types will be assumed.

Recommended Action    Refer to the appropriate product hardware installation guide for information on increasing or decreasing power supply capacity and configuring power supplies.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-PS_UNSUPPORTED: Detected an unsupported power supply [dec] 
[chars] for CISCO MDS 9500/9200 Multilayer Switches (Serial number [chars]). 

Explanation    This power supply is not supported for the Cisco MDS 9500 or 9200 series of switches.

Recommended Action    Refer to the appropriate product hardware installation guide for information on increasing or decreasing power supply capacity and configuring power supplies.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-2-SYS_IDPROMBAD:  Chassis IDPROM [dec] data invalid. 

Explanation    The named chassis IDPROM contains invalid data.

Recommended Action    Use the show sprom module [decimaldigit] CLI command to read module IDPROM contents and collect more information. Or, use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-2-SYS_IDPROMBAD_RECOVER_FAIL: Chassis IDPROM [dec] data 
re-initialization Un-successful. Data is invalid. 

Explanation    Chassis IDPROM re-initialization was unsuccessful. The data is invalid.

Recommended Action    Us ethe 'show sprom module decimal digit 1 CLI command to read the module IDPROM contents and collect more information.

Introduced    Cisco MDS SAN-OS Release 3.0(2).

Error Message     PLATFORM-2-SYS_IDPROMBAD_RECOVER_PASS: Chassis IDPROM [dec] data 
re-initialized successfully. 

Explanation    Chassis IDPROM invalid data was succesfully re-initialized to valid.

Recommended Action    Us ethe 'show sprom module decimal digit 1 CLI command to read the module IDPROM contents and verify the information.

Introduced    Cisco MDS SAN-OS Release 3.0(2).

PLATFORM-3

Error Message     PLATFORM-3-MOD_PWRFAIL: Module [dec] failed to power up (Serial No. 
[chars]). 

Explanation    The module failed to power up.

Recommended Action    Enter the show platform internal all module [dec] CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-3-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to 
idprom read error. 

Explanation    The module cannot be powered up because of an IDPROM read error.

Recommended Action    Enter the show platform internal all module [dec] and show module internal all module [dec] show sprom module [dec][dec] CLI commands or use similar Fabric Manager/Device Manager procedures to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-3-SYS_IDPROMBAD:  Chassis idprom [dec] data invalid. 

Explanation    The chassis IDPROM contains invalid data.

Recommended Action    Enter the show sprom module [dec] CLI command or use a similar Fabric Manager/Device Manager procedure to read module idprom contents and collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-3-XBAR_PWRFAIL: Xbar [dec] failed to power up (Serial number 
[chars]). 

Explanation    The named xbar in the slot failed to power up.

Recommended Action    Use the show platform internal all module [decimaldigit] CLI command to collect more information or use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-3-XBAR_PWRIDPROMFAIL: Xbar [dec] failed to power up due to 
IDPROM read error. 

Explanation    The xbar named cannot be powered up because of an IDPROM read error.

Recommended Action    Use the CLI commands show platform internal all module [decimaldigit] and show module internal all module [decimaldigit] and show sprom xbar [dec] [dec] to read module IDPROM contents to collect more information (or use a similar Fabric Manager procedure).

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLATFORM-4

Error Message    PLATFORM-4-MOD_TEMPFAIL: [chars] temperature sensor [dec] failed. 

Explanation    The module in the slot named contains a faulty temperature sensor.

Recommended Action    Use the show env temperature CLI command to collect more information or use a similar Fabric Manager procedure.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLATFORM-5

Error Message    PLATFORM-5-CHASSIS_CLKMODOK: Chassis clock module [dec] ok. 

Explanation    Clock module on chassis is functioning properly.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-CHASSIS_CLKSRC: Current chassis clock source is 
clock-[dec]. 

Explanation    The current chassis clock source is shown in the message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-FAN_OK: Fan module ok. 

Explanation    Fan module is operating normally.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-MOD_DETECT: Module [dec] detected (Serial No. [chars]). 

Explanation    A new module has been detected.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-MOD_PWRDN: Module [dec] powered down (Serial No. [chars]). 

Explanation    The module is powered down.

Recommended Action    Enter the show module, show platform internal all module[dec] and show module internal all module [dec] CLI commands or use similar Fabric Manager/Device Manager procedure to collect more information if you suspect the module has been powered down because of errors.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-MOD_PWRUP: Module [dec] powered up (Serial No. [chars]). 

Explanation    The module is powered up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-MOD_REMOVE: Module [dec] removed (Serial No. [chars]). 

Explanation    The module has been removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-MOD_TEMPFAIL: Module [dec] temperature sensor failed. 

Explanation    Module contains a faulty temperature sensor.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-MOD_TEMPOK: Module [dec] recovered from minor temperature 
alarm. 

Explanation    Module exceeded a major temperature threshold.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-PS_CAPACITY_CHANGE: Power supply PS[dec] changed its 
capacity. possibly due to power cable removal/insertion (Serial number [chars]). 

Explanation    A power supply capacity change has been detected.

Recommended Action    Refer to power supply documentation on increasing and decreasing power supply capacity, configuring power supplies, and other information about power supplies. Use the show environment power CLI command and the show platform internal info CLI command to collect more information.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    PLATFORM-5-PS_DETECT: Power supply [dec] detected but shutdown (Serial 
No. [chars]). 

Explanation    Power supply is detected, but it is shut down.

Recommended Action    Enter the show environment power and show platform internal info CLI commands or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-PS_FANOK: Fan in Power supply [dec] ok. 

Explanation    Fan module in the named power supply is operating normally.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PLATFORM-5-PS_OK: Power supply [dec] ok (Serial No. [chars]). 

Explanation    Power supply is operating normally.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-PS_REMOVE: Power supply [dec] removed (Serial No. 
[chars]). 

Explanation    Power supply has been removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PLATFORM-5-SYS_SHUTDOWN: System shutdown in [dec] seconds due to major 
temperature alarm. 

Explanation    System shut down in seconds because the temperature exceeded a major threshold.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PLATFORM-5-XBAR_DETECT: Xbar [dec] detected (Serial number [chars]). 

Explanation    A new xbar in the slot named has been detected.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-5-XBAR_PWRDN: Xbar [dec] powered down (Serial number 
[chars]). 

Explanation    The xbar in the slot named is powered down.

Recommended Action    Perform a showmodulexbar','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodul e[decimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-5-XBAR_PWRUP: Xbar [dec] powered up (Serial number [chars]). 

Explanation    The xbar in the slot named is powered up.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PLATFORM-5-XBAR_REMOVE: Xbar [dec] removed (Serial number [chars]). 

Explanation    The xbar in the slot named has been removed.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLATFORM-7

Error Message    PLATFORM-7-PFM_CLOCK_UPD_FAIL: Clock update failed due to 
context-switch delay of [dec] msec. 

Explanation    System will shut down in seconds because of a clock update failure.

Recommended Action    Enter the show env temperature CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PLOG Messages

This section contains the persistent logger (PLOG) messages.

PLOG-4

Error Message    PLOG-4-PLOG_LC_EXIT: Persistent Logger encountered an error [dec]. 

Explanation    Persistent Logger encountered an error.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PLOG_SUP Messages

This section contains the persistent logger (PLOG_SUP) messages.

PLOG_SUP-4

Error Message    PLOG_SUP-4-PLOG_SUP_EXIT: Persistent Logger encountered an error 
[dec]. 

Explanation    Persistent Logger encountered an error.

Recommended Action    No action is required.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

PORT Messages

This section contains the port messages.

PORT-3

Error Message     PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] 
is not supported. 

Explanation    Transceiver (SFP) is not from an authorized vendor.

Recommended Action    Enter the show interface transceiver CLI command or use a similar Fabric Manager/Device Manager procedure to determine the transceiver being used. Contact your customer support representative for a list of authorized transceiver vendors.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT-5

Error Message    PORT-5-EC_DISABLED_AS_LICENSE_NOT_PRESENT: Extended credit feature 
has been disabled as Enterprise Package license could not be checked out. 

Explanation    The Enterprise Package license is not available. The extended credit feature has been disabled even though it was present in the startup configuration.

Recommended Action    Install the Enterprise Package license and re-enable the extended credit feature.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    PORT-5-IF_BRINGUP_ALLOWED_FCOT_CHECKSUM_ERR: Interface [chars] is 
allowed to come up even with SFP checksum error. 

Explanation    SFP checksum on this interface failed.

Recommended Action    Replace the SFP on this interface.

Introduced Cisco MDS SAN-OS Release 2.1(2).

Error Message    PORT-5-IF_BRINGUP_NOT_ALLOWED_PORT_CONFIG_FAILURE: Interface [chars] 
is not allowed to be operational due to port config failure for reason: [chars] 
([hex]). 

Explanation    Check interface configuration.

Recommended Action    Try to change the configuration on the interface with the current available hardware capability.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    PORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively 
down). 

Explanation    Interface has been configured to be administratively down.

Recommended Action    Enter the CLI commands config terminal, interface, no shutdown or use a similar Fabric Manager procedure to bring up the interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED: Interface [chars] is down 
(Error disabled - bit error rate too high). 

Explanation    The port has detected a bit error rate too high in frames received from attached device.

Recommended Action    Check the attached device and replace it if needed.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_BUNDLE_MISCFG: Interface [chars] is down (Isolation 
due to channel mis-configuration on local or remote switch). 

Explanation    One port across a link is part of a PortChannel while the other is not.

Recommended Action    While adding or deleting a member port from a PortChannel, both ports across the link should be added or deleted. No operation should be performed on either port until they are both added or deleted.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change). 

Explanation    FCIP interface temporarily down because of reconfiguration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel 
admin down). 

Explanation    This interface belongs to a PortChannel and the PortChannel is configured to be administratively down.

Recommended Action    Bring the interface up by entering the no shutdown CLI command or by using a similar Fabric Manager procedure.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface 
[chars] is down (Channel membership update in progress). 

Explanation    The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel.

Recommended Action    Try the configuration again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_DENIED_DUE_TO_PORT_BINDING: Interface [chars] is 
down(Suspended due to port binding). 

Explanation    The F port is suspended because it is being denied by port binding.

Recommended Action    Modify the port binding database to allow the host port to log in.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface 
[chars] is down (Isolation due to domain id assignment failure). 

Explanation    The interface is isolated because of a failure while assigning a domain.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is down 
(Isolation due to invalid fabric reconfiguration). 

Explanation    Invalid RCF received.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down 
(Isolation due to domain manager disabled). 

Explanation    The interface is isolated because the domain manager is disabled.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars] 
is down (Isolation due to domain manager other side not responding). 

Explanation    Remote end domain manager is not responding.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_DOMAIN_NOT_ALLOWED_ISOLATION: Interface [chars] is 
isolated (domain not allowed). 

Explanation    There are not enough allowed domains to merge the VSANs across the link.

Recommended Action    Ensure that all assigned domain IDs are in the configured allowed domains on both sides of the link.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     PORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars] 
is down (Isolation due to domain other side eport isolated). 

Explanation    This interface is isolated because the remote end is isolated.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down 
(Isolation due to domain overlap). 

Explanation    The interface is isolated because of a domain overlap.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_DPVM_VSAN_NOT_FOUND: Interface [chars] is down (dynamic 
vsan not present). 

Explanation    The specified dynamic VSAN is not configured on this switch.

Recommended Action    Configure the dynamic VSAN.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down 
(Isolation due to ELP failure). 

Explanation    Exchange link parameter (ELP) failed on the interface.

Recommended Action    Enter the show port internal info CLI command or use a similar Fabric Manager/Device Manager procedure to check the ELP failure reason field.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSF_PARAM_ERR: Interface 
[chars] is down (Isolation due to ELP failure: class F param error). 

Explanation    Exchange link parameter (ELP) failed on the interface because of a class F parameter error.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSN_PARAM_ERR: Interface 
[chars] is down (Isolation due to ELP failure: class N param error). 

Explanation    Exchange link parameter (ELP) failed on the interface because of a class N parameter error.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PAYLOAD_SIZE: Interface 
[chars] is down (Isolation due to ELP failure: invalid payload size). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid payload size.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PORT_NAME: Interface 
[chars] is down (Isolation due to ELP failure: invalid port name). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid port name.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_SWITCH_NAME: Interface 
[chars] is down (Isolation due to ELP failure: invalid switch name). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid switch name.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_TX_BBCREDIT: Interface 
[chars] is down (Isolation due to ELP failure: loopback detected). 

Explanation    Exchange link parameter (ELP) failed on the interface because loopback connection was detected.

Recommended Action    Connect to a port on another switch and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_LOOPBACK_DETECTED: Interface 
[chars] is down (Isolation due to ELP failure: invalid transmit B2B credit). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid transmit B2B credit.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_RATOV_EDTOV_MISMATCH: Interface 
[chars] is down (Isolation due to ELP failure: R_A_TOV or E_D_TOV mismatch). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an R_A_TOV or E_D_TOV time-out value mismatch.

Recommended Action    Configure R_A_TOV and E_D_TOV values correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_REVISION_MISMATCH: Interface 
[chars] is down (Isolation due to ELP failure: revision mismatch). 

Explanation    Exchange link parameter (ELP) failed on the interface because of a revision mismatch.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_CODE: 
Interface [chars] is down (Isolation due to ELP failure: invalid flow control 
code). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid flow control code.

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_PARAM: 
Interface [chars] is down (Isolation due to ELP failure: invalid flow control 
param). 

Explanation    Exchange link parameter (ELP) failed on the interface because of an invalid flow control parameter .

Recommended Action    Configure the attached switch port correctly and try again.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error Disabled 
- EPP Failure). 

Explanation    Trunk protocol failed.

Recommended Action    Enter the show port internal event-history msgs CLI command or use a similar Fabric Manager/Device Manager procedure to see the trunk protocol exchanges and determine why it failed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error 
disabled). 

Explanation    The interface encountered an error while configuring it.

Recommended Action    Enter the show port internal all interface CLI command or use a similar Fabric Manager/Device Manager procedure to collect more information about the failed interface. In most cases, you can recover by entering the shutdown and no shutdown CLI command or similar Fabric Manager/Device Manager procedure on the interface. If that does not work, remove and reinsert the fiber cable.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down 
(Isolation due to ESC failure). 

Explanation    Exchange switch parameter (ESC) failed on the interface.

Recommended Action    Enter the show port internal event-history CLI command or use a similar Fabric Manager/Device Manager procedure to determine the ESC protocol exchanges to determine how it failed.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port src 
interface down). 

Explanation    Ethernet link to which the FCIP interface is bound is down.

Recommended Action    Ensure that the Ethernet cable is connected and that the interface is administratively enabled.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port 
src interface link down). 

Explanation    Ethernet link to which the FCIP interface is bound is down.

Recommended Action    Ensure that the Ethernet cable is connected and the remote end is also active.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_FABRIC_BIND_FAILURE: Interface [chars] is 
down(Isolation due to fabric bind failure). 

Explanation    Fabric binding failed on this port.

Recommended Action    Check the fabric binding database to ensure that the remote port is allowed to connect to this port.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (Fcot not 
present). 

Explanation    The Fibre Channel optical transceiver (SFP) has been removed.

Recommended Action    Insert a Fibre Channel optical transceiver.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down 
(Error disabled - Fcot vendor not supported). 

Explanation    The Fibre Channel optical transceiver inserted is not a supported one.

Recommended Action    Contact your customer support representative for a list of authorized transceiver (SFP) vendors.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_FCSP_AUTHENT_FAILURE: Interface [chars] is down (FC-SP 
authentication failure). 

Explanation    The port failed Fibre Channel Security Protocol (FC-SP) authentication with its peer.

Recommended Action    Check the FC-SP configuration.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_FICON_BEING_ENABLED: Interface [chars] is down(FICON 
being enabled). 

Explanation    FICON is being enabled on the port.

Recommended Action    FICON enable takes some time. No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_FICON_NOT_ENABLED: Interface [chars] is down(Error 
disabled - ficon not enabled). 

Explanation    FICON is not enabled on the port.

Recommended Action    Enable FICON on the port.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_FICON_VSAN_DOWN: Interface [chars] is down(FICON VSAN 
down). 

Explanation    FICON is being enabled on the VSAN of this port. This is an intermediary state, whereby the port VSAN is being enabled to be a FICON VSAN.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware 
Failure). 

Explanation    The module hardware has failed.

Recommended Action    Enter the show module internal all module command or use a similar Fabric Manager procedure to collect more information about the failed module.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive). 

Explanation    The port VSAN has been suspended or deleted.

Recommended Action    Assign a new active port VSAN to the interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down 
(Error disabled - Incompatible admin port mode). 

Explanation    The configured mode is not supported on this interface.

Recommended Action    Enter the show port internal info command or use a similar Fabric Manager procedure to determine the list of modes supported on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is 
down (Error disabled - Incompatible admin port rxbbcredit). 

Explanation    The configured receive B2B credit size is not supported.

Recommended Action    Enter the show port internal info command or use a similar Fabric Manager procedure to get the allowed receive B2B credit size.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is 
down (Error disabled - Incompatible admin port rxbufsize). 

Explanation    The configured receive buffer size is not supported.

Recommended Action    Enter the show port internal info command or use a similar Fabric Manager procedure to get the allowed receive buffer size.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down 
(Error disabled - Incompatible admin port speed). 

Explanation    The configured speed is not supported on this interface.

Recommended Action    Enter the show port internal info command or use a similar Fabric Manager procedure to determine the range of speed supported on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down (Initializing). 

Explanation    The interface is in the process of coming up.

Recommended Action    If the interface is stuck in this state for a while, enter the show port internal event-history command or use a similar Fabric Manager procedure to determine what it is waiting for.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface 
removed). 

Explanation    Interface was removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_INVALID_ATTACHMENT: Interface [chars] is down(Invalid 
attachment). 

Explanation    The peer interface does not have the compatible security attributes.

Recommended Action    Ensure that the peer interface has security attributes compatible with the local interface.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_INVALID_CONFIG: Interface [chars] is down(Error 
disabled - Possible PortChannel misconfiguration). 

Explanation    The local and peer interface have a PortChannel membership misconfiguration.

Recommended Action    Ensure that both the local and peer interfaces are either both members of the same PortChannel or are both not part of any PortChannel.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_INVALID_FABRIC_BINDING: Interface [chars] is 
down(Invalid fabric binding exchange). 

Explanation    Fabric binding failed.

Recommended Action    Check the fabric binding database.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link failure). 

Explanation    The physical link has gone down.

Recommended Action    Ensure that the cable is connected and the remote end is not shut down.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_LOCALLY_DISRUPTIVE_RECONFIGURATION: Interface [chars] 
is down (fcdomain applied a locally disruptive reconfiguration). 

Explanation    Fcdomain applied a locally disruptive reconfiguration. The local domain became invalid.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.0(1).

Error Message    PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag 
failure). 

Explanation    Diagnostics failed on the interface.

Recommended Action    Enter the attach module command or use a similar Fabric Manager procedure to connect to the module to collect more information about the failed interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down 
(Isolation due to port loopback to same switch). 

Explanation    The interface is looped back to another interface on the same switch.

Recommended Action    Check the connectivity of this interface and ensure that it is connected to another switch.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module 
removed). 

Explanation    Interface is down because the module was removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non 
participating). 

Explanation    The loop interface has been put into nonparticipating mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_NONE: Interface [chars] is down (None). 

Explanation    There is no apparent reason the interface is down.

Recommended Action    Enter the show port internal all interface command or use a similar Fabric Manager procedure to determine why the interface went down.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_NOS_RCVD: Interface [chars] is down (NOS received). 

Explanation    The physical link has gone down.

Recommended Action    Ensure that the cable is connected and the remote end is not shut down.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT-5-IF_DOWN_NO_TRUNK_OPER_VSANS_ISOLATION: Interface [chars] is 
down(Isolation due to no common VSANs with peer on trunk). 

Explanation    The TE port is isolated because there are no common VSANs to be brought up with the peer port.

Recommended Action    Check that there are common VSANs configured and allowed to come up between the ports.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline). 

Explanation    The interface has been placed into the offline state.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_OHMS_EXTERNAL_LB_TEST: Interface [chars] is 
down(External loopback test). 

Explanation    The interface is down because it is running external loopback tests.

Recommended Action    Wait until the tests complete.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_OLS_RCVD: Interface [chars] is down (OLS received). 

Explanation    The physical link has gone down.

Recommended Action    Verify that the cable is connected and the remote end is not shut down.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent 
interface down). 

Explanation    Parent interface is down.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. closed 
by peer). 

Explanation    The FCIP peer connected to this interface closed the TCP connection.

Recommended Action    Enter the show interface command or use a similar Fabric Manager procedure to provide the peer IP address of this FCIP interface. Check to see why the peer closed the TCP connection.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. reset 
by peer). 

Explanation    TCP connection to the FCIP peer got reset.

Recommended Action    Enter the show interface and show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Check to see why the peer reset the TCP connection.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_PORT_ACT_LICENSE_NOT_AVAILABLE: Interface [chars] is 
not allowed to come up (port activation license not available. 

Explanation    Assign a port activation license to this port or install additional port activation licenses as needed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    PORT-5-IF_DOWN_PORT_BIND_FAILURE: Interface [chars] is down(Isolation 
due to port bind failure). 

Explanation    Port binding failed on this port.

Recommended Action    Check the port binding database to ensure that the remote port is allowed to connect to this port.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_PORT_BLOCKED: Interface [chars] is down(Port blocked 
due to FICON). 

Explanation    The port has been blocked by the FICON configuration.

Recommended Action    Unblock the port in the FICON configuration.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message     PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down 
(No operational members). 

Explanation    This is a PortChannel interface and all its members are operationally down.

Recommended Action    Enable at least one of the PortChannel members.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is 
down (Isolation due to port VSAN mismatch). 

Explanation    The interface is isolated because of a mismatch in the configured port VSAN of the local and remote ends.

Recommended Action    Configure the port VSAN of the local and remote interfaces to be the same and enter the shutdown and no shutdown CLI commands or use a similar Fabric Manager/Device Manager procedure to bring up the ports.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in 
progress). 

Explanation    There is an RCF in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port 
software failure). 

Explanation    The software servicing the data path on the port has failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is down(Tunnel 
source module not online). 

Explanation    The module that has the source port of this FCIP interface is not online.

Recommended Action    The module that has the source port for the FCIP link is coming online. Enter the show module CLI command or use a similar Fabric Manager/Device Manager procedure to find the module status.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down (Tunnel 
port src interface unbound). 

Explanation    The FCIP link port source interface is not bound.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel src 
port removed). 

Explanation    The link source port of this FCIP interface has been removed. The source interface with the IP address that matches the IP address of the bound entity is removed. This happens normally because the module on which the source interface exists is removed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended). 

Explanation    This interface belongs to a PortChannel and has been suspended because of an error while bringing it up.

Recommended Action    In most cases, you can recover by entering the shutdown and no shutdown CLI commands or by using a similar Fabric Manager/Device Manager procedure. If this happens again, enter the show port internal all interface command or use a similar Fabric Manager procedure on the interface to gather more information.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended 
due to incompatible mode). 

Explanation    This interface belongs to a PortChannel and the operational mode of the interface is different from that of the PortChannel.

Recommended Action    Change the mode and the trunking mode of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down 
(Suspended due to incompatible speed). 

Explanation    This interface belongs to a PortChannel and the operational speed of the interface is different from that of the PortChannel.

Recommended Action    Change the speed of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down (Suspended 
due to incompatible remote switch WWN). 

Explanation    This interface belongs to a PortChannel and the remote switch WWN of the interface is different from that of the PortChannel.

Recommended Action    Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is down(TCP 
conn. closed - Keep alive expired). 

Explanation    The TCP session to the FCIP peer was closed because of the loss of the TCP keep alive.

Recommended Action    You may have lost IP connection. Enter the show interface and show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter the traceries ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connectivity to the peer.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP conn. 
closed - retransmit failure). 

Explanation    Interface is down buckeye it reached the maximum allowed retransmission failures.

Recommended Action    This may be because of a loss of IP connectivity. Enter the show interface, show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter the traceroute ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connectivity to the peer.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is 
down(TCP conn. closed - Persist timer expired). 

Explanation    TCP session to the FCIP peer closed because the TCP persist timer expired.

Recommended Action    You may have lost IP connection. Enter the show interface, show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FC IP peer. Enter the traceroute ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connection to the peer.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_TOO_MANY_INVALID_FLOGIS: Interface [chars] is 
down(Suspended due to too many invalid flogis. 

Explanation    The port is suspended because of receiving a large number of invalid FLOGIs.

Recommended Action    Check the host bus adapter (HBA) and enter the shutdown and no shutdown CLI commands or use a similar Fabric Manager/Device Manager procedure on the port.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Error Message    PORT-5-IF_DOWN_TOO_MANY_INTR: Interface [chars] is down (Error 
disabled - too many interrupts). 

Explanation    The port has received too many hardware interrupts.

Recommended Action    Check the device attached to the port and replace it if needed.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message    PORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down 
(Linecard upgrade in progress). 

Explanation    Upgrade of the line card software is in progress.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_VIRTUAL_IVR_DOMAIN_OVERLAP_ISOLATION: Interface 
[chars] is down (Isolation due to virtual IVR domain overlap). 

Explanation    Isolated because of a virtual IVR domain overlap.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.1(1a).

Error Message     PORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down 
(Isolation due to VSAN mismatch). 

Explanation    This is a trunking interface and the VSANs configured do not match the VSANs configured on the remote end.

Recommended Action    Check the VSANs configured on the local end with the remote end.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is 
down (Isolation due to zone merge failure). 

Explanation    The interface was isolated because of a failure during zone merge.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is 
down (Isolation due to remote zone server not responding). 

Explanation    The interface was isolated because of a remote zone server not responding.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-IF_REINITED_ON_COMPAT_FAILURE: Interface [chars] reinited as 
one or more configurations changed during compatibility check. 

Explanation    Interface has been re-initialized due to rollback failure. In Generation 2 line cards, compatibility checking involves reserving required resources in a line card. When a compatibility check fails, a rollback is performed to restore the resources of the interface. Rollback failures require modification of the current configuration of the interface and reinitializing the interface.

Recommended Action    Modify interface configurations and retry compatibility check.

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PORT-5-IF_TRUNK_DOWN: Interface [chars], VSAN [chars] is down 
([chars]). 

Explanation    The interface is trunking. The VSAN is down because of the reason shown in the error message.

Recommended Action    Enter the show interface, show port internal info interface vsan and show port internal event-history interface vsan CLI commands or use a similar Fabric Manager/Device Manager procedure to determine why this VSAN is down on this interface.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_TRUNK_UP: Interface [chars], VSAN [chars] is up. 

Explanation    The interface is trunking, and the VSAN is up.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT-5-IF_UP: Interface [chars] is up [chars]. 

Explanation    Interface is up in the mode specified, if applicable.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT-5-MODULE_BRINGUP_NOT_ALLOWED: Not allowing module [dec] to come 
up for reason: [chars] ([hex]). 

Explanation    Module is not allowed to be operational due to the current system state.

Recommended Action    Check the global index allocation using the show port index-allocation CLI command. Also, check the module.'

Introduced    Cisco MDS SAN-OS Release 3.0(1).

Error Message    PORT-5-MODULE_INDEX_RESTORE_ERROR: Error in restoring indices for 
module [dec]: reason [chars] ([hex]). 

Explanation    Restore of module index may fail due to overlap of indices.

Recommended Action    No action is required.

Error Message    PORT-5-MODULE_UNLIMITED_OSM_SEQ_FAILED: Enable/Disable of unlimited 
oversubscription failed for module [dec]. 

Explanation    Interfaces of the module may be in an indeterminate state.

Recommended Action    Reload the module.

Introduced Cisco MDS SAN-OS Release 3.1(1).

PORT-Resources Messages

This section contains the port resources (PORT-RESOURCES) messages.

Error Message    PORT-RESOURCES-3-PRM_MSG_SEND_FAILURE: failed to send [chars] to sap 
[dec]: [chars]. 

Explanation    An attempt to send a message failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 3.1(2).

Error Message    PORT-RESOURCES-5-INVALID_PORT_ACTIV_PKG_LICENSE_FILE_INSTALLED: 
Invalid on demand port activation license file is installed for module [dec]. 

Explanation    Interfaces may not acquire port activation licenses during installation.

Recommended Action    Install a valid port activation license file.

Introduced Cisco MDS SAN-OS Release 3.1(1).

PORT-SECURITY Messages (Deprecated)

This section contains the port security (PORT-SECURITY) messages. These messages were deprecated in Cisco MDS SAN-OS Release 1.3(4a). They were replaced by the "PORT_SECURITY Messages" section.

PORT-SECURITY-2

Error Message     PORT-SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec] 
for [chars]. 

Explanation    Memory allocation failed for the entity and size shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT-SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to 
[chars]. 

Explanation    The feature is unavailable and will be disabled.

Recommended Action    Install the correct license and reenable.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

PORT-SECURITY-3

Error Message    PORT-SECURITY-3-BINDING_CONFLICT: [chars] in VSAN [dec]. 

Explanation    An already logged in device is in conflict with the port security manager (PSM) active binding configurations. The error message indicates the WWN of the login entity, interface and VSAN.

Recommended Action    Use the autolearn feature with activation. This message is informational in nature, and the device will not be logged out. However, it will be denied login when it attempts to log in the next time.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT-SECURITY-3-BINDING_VIOLATION: [chars] in VSAN [dec]. 

Explanation    A login occurred that violates the port security manager (PSM) binding configurations. The error message indicates the WWN of the login entity and the VSAN.

Recommended Action    Only entries in the activated database of PSM can log in. Change the configuration and activate it again.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT_SECURITY-3-CFS_NOTIF_ERR: [chars]. 

Explanation    An error occurred during the processing of a CFS notification. [chars] indicates the actual cause for the error.

Recommended Action    Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Introduced Cisco MDS SAN-OS Release 3.2(1).

Error Message    PORT-SECURITY-3-DB_ERR: [chars]. 

Explanation    An error occurred during a port security manager (PSM) database operation. The error message indicates the reason for the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-EFMD_FC2_OPER_FAILED: [chars]. 

Explanation    The exchange fabric membership data (EFMD) Fibre Channel Layer 2 (FC-2) operation failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-EFMD_INIT_FAILED: [chars]. 

Explanation    The exchange fabric membership data (EFMD) initialization failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars]. 

Explanation    Received a corrupted exchange fabric membership data (EFMD) request packet.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-INIT_FAIL: [chars]. 

Explanation    An error happened during port security manager initialization. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message    PORT-SECURITY-3-LEARNT_BINDING_CONFLICT: [chars] in VSAN [dec]. 

Explanation    An already logged in device that is learned during activation is in conflict with the port security manager active binding configurations. The error message indicates the WWN of the login entity, interface, and VSAN.

Recommended Action    Copy the active database to the configuration database and reactivate. Not doing so could result in unexpected login rejects later with this interface.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-MTS_ERR: [chars]. 

Explanation    An error occurred in processing a messaging and transaction services (MTS) message. The error message indicates the error that occurred.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-PSS_ERR: [chars]. 

Explanation    An error occurred during a port security manager persistent storage service (PSS) operation. The error message indicates the persistent storage service (PSS) operation that caused the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT-SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version 
[dec].[dec].[dec], expected version [dec].[dec].[dec]. 

Explanation    There was a mismatch in the persistent storage service (PSS) version. The error message indicates the PSS service, its current version number, and the expected version.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

PORT-SECURITY-4

Error Message     PORT-SECURITY-4-ACTIVATION_FAIL: [chars] in VSAN [dec]. 

Explanation    Activation of bindings failed because of the reason shown in the error message in the VSAN.

Recommended Action    Correct the error and reactivate it.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

PORT-SECURITY-6

Error Message     PORT-SECURITY-6-INFO: [chars]. 

Explanation    An event happened that affects the port security manager. The error message indicates the event.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.3(1).

Deprecated Cisco MDS SAN-OS Release 1.3(4a).

PORT_CHANNEL Messages

This section contains the PortChannel (PORT_CHANNEL) messages.

PORT_CHANNEL-1

Error Message     PORT_CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed 
[[chars]]. 

Explanation    Module configuration failed.

Recommended Action    The module is automatically reset. If the problem persists, contact your customer support representative.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec]). 

Explanation    There is not enough memory.

Recommended Action    Check if the system is low on memory and reset the switch if necessary.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for 
[chars] [[chars]]. 

Explanation    Parameter mapping failed.

Recommended Action    The specified service is misbehaving. Check its status.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [chars]: 
[chars]. 

Explanation    Failed to send a multicast message to all modules, usually because some module went down.

Recommended Action    Enter the show port-channel consistency CLI command or use a similar Fabric Manager/Device Manager procedure to check consistency.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-2

Error Message     PORT_CHANNEL-2-RESET_MODULE: reset module [dec] for not responding or 
returning error. 

Explanation    A module is reset for not responding or returning an error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-3

Error Message     PORT_CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible. 

Explanation    Compatibility check failed when adding ports to a PortChannel.

Recommended Action    Make sure the compatibility parameters are consistent while adding ports to a PortChannel, or use the force option.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-3-GENERAL_ERROR: [chars]. 

Explanation    General error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: 
[chars]. 

Explanation    Failed to send a message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found. 

Explanation    Cannot find a PortChannel in its database, which indicates an inconsistency with an external component.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], 
state [chars]]. 

Explanation    Some operation timed out.

Recommended Action    Execute the show port-channel consistency CLI command or use a similar Fabric Manager/Device Manager procedure to check all module connectivity and consistency.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-4

Error Message     PORT_CHANNEL-4-PORT_CFG_DELETED: [chars] removed from PortChannel 
[dec] (different module inserted). 

Explanation    Port is removed from a PortChannel because a different module was inserted to the same slot.

Recommended Action    The system has lost some ports from the PortChannel. Add ports in the new module to the same PortChannel.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally 
individual. 

Explanation    The port is operating as an individual link even though it is locally or remotely configured to be part of a PortChannel.

Recommended Action    Check the configuration of the port locally and remotely to ensure that it can operate as part of a PortChannel.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     PORT_CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of 
PortChannel. 

Explanation    Cannot find the port in the PortChannel database, which indicates an inconsistency with an external component.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-4-RACE_WARN: [chars]. 

Explanation    Warning of a possible race condition.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from 
[chars]. 

Explanation    Received an unexpected response and discarded it.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-5

Error Message    PORT_CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]. 

Explanation    The autocreate process on the port failed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 2.0(1b).

Error Message     PORT_CHANNEL-5-CREATED: [chars] created. 

Explanation    A PortChannel was created.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-5-DELETED: [chars] deleted. 

Explanation    A PortChannel was deleted.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-5-FOP_CHANGED: [chars]: first operational port changed 
from [chars] to [chars]. 

Explanation    The first operational port in a PortChannel was changed.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message    PORT_CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come online 
because port channel interface <port-channel number

Explanation    The port-channel number configured on the switch is larger than 128.

Recommended Action    Delete the set of port channel interface <port-channel interface

Error Message     PORT_CHANNEL-5-PORT_ADDED: [chars] added to [chars]. 

Explanation    Ports were added to a PortChannel.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]. 

Explanation    Ports were removed from a PortChannel.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-6

Error Message     PORT_CHANNEL-6-PORT_DOWN: [chars]: [chars] is down. 

Explanation    Port went down in a PortChannel.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-6-PORT_UP: [chars]: [chars] is up. 

Explanation    Port came up in a PortChannel.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-6-RESYNC: resyncing [chars] with all modules. 

Explanation    Resynchronizing modules with the supervisor module after an error or switchover.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

PORT_CHANNEL-7

Error Message     PORT_CHANNEL-7-GSYNC_DONE: global synchronization is done. 

Explanation    PortChannel manager finished global synchronization.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-GSYNC_REQ: requesting global synchronization. 

Explanation    PortChannel manager requested a global synchronization from the active supervisor.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-START_ACTIVE: started in active mode. 

Explanation    PortChannel manager started in active mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-START_DEFAULT: started with default configuration. 

Explanation    PortChannel manager started with the default configuration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-START_STANDBY: started in standby mode. 

Explanation    PortChannel manager started in standby mode.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-START_STATEFUL: started statefully. 

Explanation    PortChannel manager started with the running configuration.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PORT_CHANNEL-7-START_STATELESS: started statelessly. 

Explanation    PortChannel manager started with the startup configuration.

Recommended Action    No action is required.

PORT_SECURITY Messages

This section contains the port security (PORT_SECURITY) messages.

PORT_SECURITY-2

Error Message     PORT_SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec] 
for [chars]. 

Explanation    Memory allocation failed for the entity and size shown in the error message.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to 
[chars]. 

Explanation    The feature is unavailable and will be disabled now.

Recommended Action    Install the correct license and reenable.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-BINDING_CONFLICT: [chars] in VSAN [dec]. 

Explanation    An already logged in device is in conflict with the port security manager active binding configuration. The error message indicates the WWN of the login entity, interface and the VSAN.

Recommended Action    For port security, the autolearn feature can be used with activation to prevent this. This violating device or switch will be logged out.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-BINDING_VIOLATION: [chars] in VSAN [dec]. 

Explanation    A login occurred that violates the port security manager (PSM) binding configuration. The error message indicates the WWN of the login entity and the VSAN.

Recommended Action    Only entries in the activated database of PSM can log in. Change the configuration and activate it again.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-DB_ERR: [chars]. 

Explanation    An error occurred during a port security manager database operation. The error message indicates the reason for the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-EFMD_FC2_OPER_FAILED: [chars]. 

Explanation    The exchange fabric membership data (EFMD) Fibre Channel Layer 2 (FC-2) operation failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-EFMD_INIT_FAILED: [chars]. 

Explanation    The exchange fabric membership data (EFMD) initialization failed.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars]. 

Explanation    Received a corrupted exchange fabric membership data (EFMD) request packet.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-INIT_FAIL: [chars]. 

Explanation    An error happened during the port security manager initialization. The error message indicates the reason for failure.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-LEARNT_BINDING_CONFLICT: [chars] in VSAN [dec]. 

Explanation    An already logged in device that is learned during activation is in conflict with the port security manager active binding configuration. The error message indicates the WWN of the login entity, interface, and VSAN.

Recommended Action    Copy the active database to the configuration database and reactivate. Not doing so could result in unexpected login rejects later in that interface.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-MTS_ERR: [chars]. 

Explanation    An error occurred in processing of a message transaction service (MTS) message. The error message indicates the error that occurred.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-PSS_ERR: [chars]. 

Explanation    An error occurred during a port security manager persistent storage service (PSS) operation. The error message indicates the PSS operation that caused the error.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version 
[dec].[dec].[dec], expected version [dec].[dec].[dec]. 

Explanation    There was a mismatch in the persistent storage service (PSS) version. The error message indicates the PSS service, its current version number, and the expected version.

Recommended Action    If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-4-ACTIVATION_FAIL: [chars] in VSAN [dec]. 

Explanation    Activation of bindings failed in the VSAN because of the reason shown in the error message.

Recommended Action    Correct the error and reactivate it.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

Error Message     PORT_SECURITY-6-INFO: [chars]. 

Explanation    An event happened that affects the port security manager. The error message indicates the event.

Introduced Cisco MDS SAN-OS Release 1.3(4a).

PROC_MGR Messages

This section contains the process manager (PROC_MGR) messages.

PROC_MGR-SLOT#-2

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_APP_CRIT_ERROR: ERROR: Critical error 
determined for app ([chars]) status=[dec] signal=[dec]. 

Explanation    Application caused critical error.

Recommended Action    Restart the line card.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_APP_EXITED: ERROR: Application ([chars]) 
exited with status=[dec] signal=[dec]. 

Explanation    Application exited.

Recommended Action    Check the application.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_COMP_CATASTROPHIC_ERROR: ERROR: Component 
([chars]) caused critical error and linecard will be rebooted.

Explanation    Component caused critical error.

Recommended Action    Restart the line card.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_COMP_CRIT_ERROR: ERROR: Critical error 
determined for component ([chars]) errno=[dec]. 

Explanation    Critical error for component.

Recommended Action    Restart the line card.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_COMP_DEP_FAIL: ERROR: Dependency failure - 
Component ([chars]) depends on ([chars]). 

Explanation    Component dependency failure.

Recommended Action    Check whether the component exists.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_COMP_NOT_INSTALLED: ERROR: Component 
([chars]) could not be installed errno=[dec]. 

Explanation    Component not installed.

Recommended Action    Check whether the component exists.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_COMP_TIMEOUT: ERROR: Component ([chars]) 
did not exit and time out occurred. 

Explanation    Component initialization timed out.

Recommended Action    Check the component.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_ERROR: [chars]. 

Explanation    Process manager error.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_INFO: [chars]. 

Explanation    Process manager informational message.

Recommended Action    No action is required.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_MTS_CORE_CLIENT_FAIL: ERROR: MTS message to 
core_client FAILED errno=[dec]. 

Explanation    Message to core client failed.

Recommended Action    Restart the line card.

Introduced Cisco MDS SAN-OS Release 1.2(2a).

Error Message     PROC_MGR-SLOT#-2-PROC_MGR_QUIT: Process manager quitting because: 
[chars]. 

Explanation    Process manager is quitting.

Recommended Action