S to T

This chapter includes system messages for the Cisco NX-OS MDS 9000 families of switches. The messages are listed in alphabetical order by the system facility that produces them. Within each system facility section, messages are listed alphabetically by severity and mnemonics. Each message is followed by an explanation and a recommended action.

SABRE_APP Messages

This section contains the SABRE_APP messages.

SABRE_APP-SLOT#-2

Message SABRE_APP-SLOT#-2-SABRE_APP_EXITED: Sabre driver application exited (syserr = [dec], errno = [dec])

Explanation Sabre driver application exited

Recommended Action No action is required.

SAC_USD Messages

This section contains the SAC_USD messages.

SAC_USD-2

Message SAC_USD-2-JTAG_CHECK_FAILED: Xbar Driver JTAG ID check failed for slot:[dec] asic:[dec]

Explanation Xbar Driver JTAG ID check failed

Recommended Action No action is required.

Message SAC_USD-2-SAC_ACCESS_FAILED: Xbar Driver Failed to access reg for [chars]

Explanation Xbar Driver Access failed

Recommended Action No action is required.

Message SAC_USD-2-SAC_CATASTROPHIC: Xbar Driver catastrophic failure: [chars]

Explanation Xbar Driver catastrophic error

Recommended Action No action is required.

Message SAC_USD-2-SAC_INTR_OCCURRED: Xbar ASIC interrupt occurred: [chars]

Explanation Interrupt occurred

Recommended Action No action is required.

Message SAC_USD-2-SAC_INTR_THRESHLD: Xbar ASIC interrupt threshold reached: [chars]

Explanation Interrupt threshold reached

Recommended Action No action is required.

Message SAC_USD-2-SAC_INTR: Xbar ASIC interrupt occurred: [chars]

Explanation Interrupt occurred on the xbar

Recommended Action No action is required.

Message SAC_USD-2-SAC_MALLOC_FAILED: Xbar Driver memory allocation failed

Explanation Xbar Driver Access failed

Recommended Action No action is required.

Message SAC_USD-2-SHUTDOWN: Xbar Driver software process exiting: [chars]

Explanation Xbar Driver shutting down

Recommended Action No action is required.

Message SAC_USD-2-SYNC_FAILED: Xbar Driver sync failed: [chars]

Explanation Xbar Driver Sync failed for the xbar channel

Recommended Action No action is required.

SAC_USD-3

Message SAC_USD-3-EN_DATA_FAILED: Xbar Driver enable data failed for slot:[dec] asic:[dec] channel:[hex]

Explanation Xbar Driver Enable Data path failed for the xbar channel

Recommended Action No action is required.

Message SAC_USD-3-FPOE_DB_ECC: Xbar Driver FPOE DB ECC error in [chars]

Explanation FPOE DB ECC error

Recommended Action No action is required.

SAC_USD-5

Message SAC_USD-5-STARTING: Xbar Driver process starting

Explanation Xbar Driver process is being started

Recommended Action No action is required.

Message SAC_USD-5-XBAR_FLOW_CTRL_DIS_EN: XBAR Multicast Flow Control [chars]

Explanation Sacramento xbar multicast flow control on Stage3 ports

Recommended Action No action is required.

SAC_USD-6

Message SAC_USD-6-DIS_DATA: Xbar Driver disable datapath done for slot:[dec] asic:[dec] channel:[hex]

Explanation Disabled Data path successfully for the xbar channel

Recommended Action No action is required.

Message SAC_USD-6-EN_DATA: Xbar Driver enable datapath done for slot:[dec] asic:[dec] channel:[hex]

Explanation Enabled Data path successfully for the xbar channel

Recommended Action No action is required.

Message SAC_USD-6-SAC_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

Message SAC_USD-6-SPINE_HW_INIT: Xbar Driver HW initialization has been done for Fabric-Slot:[dec] Asic:[dec]

Explanation Xbar Driver HW initialization has been called [dec]

Recommended Action No action is required.

Message SAC_USD-6-SYNC_DONE: Xbar Driver sync done for slot:[dec] asic:[dec] channel:[hex]

Explanation Sync Completed successfully for the xbar channel

Recommended Action No action is required.

SAL Messages

This section contains the SAL messages.

SAL-5

Message SAL-5-SAL_DISABLED: SAL Disabled

Explanation SAL Service Disabled

Recommended Action No action is required.

Message SAL-5-SAL_ENABLED: SAL Enabled

Explanation SAL Service enabled

Recommended Action No action is required.

SANTAP Messages

This section contains the SANTAP messages.

SANTAP-SLOT#-2

Message SANTAP-SLOT#-2-AVT_CREATE_FAILED: AVT PWWN: [chars], NWWN: [chars], Vsan: [dec], Host: [chars], Tgt: [chars], TgtVsan: [dec], RC: [chars]

Explanation AVT create failed because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-AVT_SCSI_FAILED: AVT PWWN: [chars], Host: [chars], AVT Lun: 0x%Ld AVT Vsan: [dec], OPC: [hex] RC: [chars]

Explanation SCSI command to AVT is invalid Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-COMMIT_FAILED: Commit Failed, status: [dec] token = [dec], vtUid = 0x%Lx, lunId = 0x%Lx

Explanation ISAPI Commit Failed, number of ITLs exceeded limit for the DPP

Recommended Action No action is required.

Message SANTAP-SLOT#-2-CVT_CREATE_FAILED: CVT PWWN: [chars], NWWN: [chars], Vsan: [dec], RC: [chars]

Explanation CVT create failed because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-DVT_CREATE_FAILED: DVT PWWN: [chars], FEVsan: [dec], BEVsan: [dec], io_tmo: [dec], app_io_tmo: [dec], RC: [chars]

Explanation DVT create failed because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-DVT_DELETE_FAILED: DVT PWWN: [chars], RC: [chars]

Explanation DVT delete failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-DVT_LUN_CREATE_FAILED: DVT: [chars], Host: [chars], DVTLun: 0x%LX, TGTLun: 0x%LX, HIIndex: [dec], Expected HIIndex: [dec], RC: [chars]

Explanation DVT LUN create failed because of sanity checks. Please check reason code for exact failure

Recommended Action No action is required.

Message SANTAP-SLOT#-2-FIT_EXISTS_ON_DIFFERENT_DPP_ERR: CONFIG Error: Cannot Create FIT on DPP [dec] for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Same Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] is logged in to another DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a different DPP [dec]

Explanation Same HOST cannot log into two DVTs which are on different DPPs

Recommended Action No action is required.

Message SANTAP-SLOT#-2-FIT_EXISTS_ON_DIFFERENT_PORT_ERR: CONFIG Error: Cannot Create FIT on Ifindex [hex]. Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] logged in to DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a different if index [hex]

Explanation Same HOST cannot log into two DVTs which are on different ports

Recommended Action No action is required.

Message SANTAP-SLOT#-2-HOST_PWWN_EXISTS_IN_BE_VSAN: WARNING:: Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] Exists in BackEnd Vsan [dec], cannot create FIT for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation FIT cannot be created, as Host exists in the Backend Vsan.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-INTERNAL_ERR: [chars]

Explanation Santap Internal Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ISAPI_CRIT_PROCESS_CRASH: [chars]. [chars]. SANTAP VM Size: [dec]kB

Explanation ISAPI critical error - process crash.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-PSS_DELETE_AVT_REC: AVT PWWN: [chars], NWWN: [chars], Vsan: [dec], Host: [chars], Tgt: [chars], TgtVsan: [dec], RC: [chars]

Explanation AVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-PSS_DELETE_CVT_REC: CVT PWWN: [chars], NWWN: [chars], Vsan: [dec], RC: [chars]

Explanation CVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-PSS_DELETE_DVT_REC: DVT PWWN: [chars], FEvsan: [dec], BEVsan: [dec], io_tmo: [dec], app_io_tmo: [dec], RC: [chars]

Explanation DVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-SANTAP_UNPROVISIONING_NOT_SUPPORTED_DURING_PSS_RECOVERY: Santap can not be unprovisioned during pss recovery. Please wait for Santap to recover and retry.

Explanation Santap can not be unprovisioned during pss recovery. Please wait for Santap to recover and retry.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-SANTAP_VERSION_NOT_SUPPORTED: Santap feature is not supported in this version of NX-OS. Please refer to NX-OS release notes for more detail.

Explanation Santa feature is not supported in this version of NX-OS. Please refer to NX-OS release notes for more detail.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_AVT_DELETED: Santap: AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (avt vsan [dec]) deleted

Explanation Santap AVT is deleted as part of Unprovisioning or VSAN Delete

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_AVT_LUN_DELETED: Santap: AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (avt lun 0x%Lx) deleted

Explanation Santap avt lun is deleted as part of Previsioning or VSAN Delete or CLI

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_CVT_DELETED: Santap: CVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (cvt vsan [dec], name [chars]) deleted

Explanation Santap CVT is deleted as part of Unprovisioning or VSAN Delete

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_DVT_DELETED: Santap: DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (FE vsan [dec], BE vsan [dec]) deleted

Explanation Santap DVT is deleted as part of Unprovisioning or VSAN Delete

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_DUPLICATE_AVT_REC: PSS Error: Deleting duplicate AVT %Lx PSS record

Explanation Duplicate AVT Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_DUPLICATE_CVT_IN_VSAN: PSS Error: VSAN: [dec] already has CVT %Lx. Deleting CVT %Lx PSS record

Explanation Multiple CVT in VSAN Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_DUPLICATE_DVT_REC: PSS Error: Deleting duplicate DVT %Lx PSS record

Explanation Duplicate DVT Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_NO_DVT_AVT_ERR: DVT %Lx does not exist for AVT

Explanation No DVT for AVT Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_NO_HIFIT_AVT_ERR: HI %Lx does not exist for AVT %Lx

Explanation No HI for AVT Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_NO_VSAN_DEL_AVT: PSS Error: VSAN: [dec] deleted. Deleting AVT %Lx PSS record

Explanation VSAN Deleted Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_NO_VSAN_DEL_CVT: PSS Error: VSAN: [dec] deleted. Deleting CVT %Lx PSS record

Explanation VSAN Deleted Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_GLOBAL_NO_VSAN_DEL_DVT: PSS Error: VSAN: [dec] deleted. Deleting DVT %Lx PSS record

Explanation VSAN Deleted Error

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_HOST_PURGED_FROM_DVT: Santap: Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] removed from DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (FE vsan [dec], BE vsan [dec]).

Explanation Santap Host Initiator is removed from DVT

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_32BIT_LUNS_PER_HOST_REACHED: MAX_32bit_LUNS_PER_HOST([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx

Explanation System limit reached for the number of Luns per Host. More Luns cannot be added at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_DVT_LUNS_PER_LC_REACHED: MAX_DVT_LUNS_PER_LC([dec]) limit reached. Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Cannot Install Lun 0x%Lx

Explanation System limit reached for the number of Luns per LC. More Luns cannot be added at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_HOSTS_PER_DVT_REACHED: MAX_HOST_PER_DVT([dec]) limit reached for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Reject Plogi/Prli from Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation System limit reached for the number of Hosts logging into DVT. More Hosts cannot be configured at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_ITLS_PER_DPP_REACHED: MAX_LUNS_PER_DPP([dec]) limit reached on DPP [dec] for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx

Explanation System limit reached for the number of ITLs per DPP. More Luns cannot be added at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_LUNS_PER_DVT_REACHED: MAX_LUNS_PER_DVT([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx

Explanation System limit reached for the number of Luns per DVT. More Luns cannot be added at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_MAX_LUNS_PER_HOST_REACHED: MAX_LUNS_PER_HOST([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx

Explanation System limit reached for the number of Luns per Host. More Luns cannot be added at this point.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_REPORT_LUNS_FAILED_ZONE_MISCONFIG: ZONE MISCONFIG: Report Luns Failed for Host: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Tgt: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], dd-sts [hex], scsi-sts [hex], isapi-sts [hex]

Explanation Report Luns Failed for the specified Host, Target pair due to missing zone. Please check the zone configuration.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_REPORT_LUNS_FAILED: Report Luns Failed for Host: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Tgt: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], dd-sts [hex], scsi-sts [hex], isapi-sts [hex]

Explanation Report Luns Failed for the specified Host, Target pair. Please check the configuration.

Recommended Action No action is required.

Message SANTAP-SLOT#-2-ST_SES_DELETED: Santap: Ses [dec] deleted

Explanation Santap ses is deleted as part of Unprovisioning or VSAN Delete or CLI

Recommended Action No action is required.

SANTAP-SLOT#-4

Message SANTAP-SLOT#-4-INTERNAL_WARNING: [chars]

Explanation Santap Internal Warning

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_16_BIT_LUNS_PRESENT: 16 Bit luns installed (current num luns [dec]) for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx !!

Explanation Cannot Install 16bit and 32 bit luns for the same Host-Target pair

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_32_BIT_LUNS_PRESENT: 32 Bit luns installed (current num luns [dec]) for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx !!

Explanation Cannot Install 16 bit and 32 bit luns for the same Host-Target pair

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_LUN_BLK_SIZE_GREATER_THAN_FIVE_TWELVE: Lun Block Size 0x%Lx detected is greater than 512 for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.

Explanation Santap does not support Luns with block size greater than 512

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_LUN_DEVICE_TYPE_NOT_SUPPORTED: Lun Device Type [dec] detected is not supported for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.

Explanation Santap does not support devices other than DASD and ArrCntl.

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_LUN_SIZE_GREATER_THAN_2_POW_48: Lun Size 0x%Lx detected is greater than 2 power 48 for Host [hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.

Explanation Santap does not support Luns greater than 2 power 48

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_MISSING_LUN_IN_TARGET_AVT_LUN_EXISTS: Warning: Lun 0x%Lx deleted on Target but AVT LUN 0x%Lx exists for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Please remove relevant avtluns, as Lun no longer exists on Target

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_MISSING_LUN_IN_TARGET_SES_EXISTS: Warning: Lun 0x%Lx deleted on Target but Session [dec] exists for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Please remove relevant sessions, as Lun no longer exists on Target

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_NEAR_MAX_HOSTS_PER_DVT: Warning: Approaching MAX_HOSTS_PER_DVT([dec]) for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Existing num hosts [dec]

Explanation Please be wary of the number of hosts logging in.

Recommended Action No action is required.

Message SANTAP-SLOT#-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning: Approaching MAX_LUNS_PER_HOST([dec]) limit for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Existing num luns [dec]

Explanation Please be wary of the number of luns configured for this host.

Recommended Action No action is required.

SANTAP-SLOT#-5

Message SANTAP-SLOT#-5-SANTAP_INFO: [chars]

Explanation SANTAP notification.

Recommended Action No action is required.

SANTAP-SLOT#-6

Message SANTAP-SLOT#-6-FIT_CREATE_ERROR_TARGET_OFFLINE: Target Offline, Cannot Create FIT in vsan [dec] for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] and DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation FIT Cannot be created as the target is offline

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_COUNTER_RESET: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] current thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has reset avt lun mask pacing counter

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_DISABLED: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] current thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has disabled avt lun mask pacing

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_ENABLED: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] current thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has enabled avt lun mask pacing

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_EXCL_MASK_IN_PARAM_MODIFIED: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has modified excl mask in threshold

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_MASK_ALL_OUT_PARAM_MODIFIED: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has modified mask all out threshold

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_MASK_PACING_MASK_OUT_PARAM_MODIFIED: Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]

Explanation User has modified mask out threshold

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_RECOVER_VSAN_DATABASE: Attempting VSAN database resync

Explanation Santap force recovery of vsans has been attempted by user. This will attempt to bring back santap vsan database in sync with the switch

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_RESYNC_VTS_IN_VSAN: ReSync Vsan [dec], changing state from [chars] to [chars]. All the VTs in this vsan will be resynced

Explanation Santap force recovery of vsans has been attempted by user. This will attempt to bring back santap vt in sync with ISAPI

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_SCP_PACING_COUNTER_RESET: Current outstanding scp [dec] reset counter [dec] threshold [dec]

Explanation User has reset scp pacing

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_SCP_PACING_DISABLED: Current outstanding scp [dec] reset counter [dec] threshold [dec]

Explanation User has disabled scp pacing

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_SCP_PACING_ENABLED: Current outstanding scp [dec] reset counter [dec] threshold [dec]

Explanation User has enabled scp pacing

Recommended Action No action is required.

Message SANTAP-SLOT#-6-ST_SCP_PACING_PARAM_MODIFIED: Current outstanding cps [dec] reset counter [dec] pacing enabled? [dec], new threshold [dec]

Explanation User has modified the scp pacing threshold

Recommended Action No action is required.

SAN_EXT_TUNER Messages

This section contains the SAN_EXT_TUNER messages.

SAN_EXT_TUNER-3

Message SAN_EXT_TUNER-3-SAN_EXT_TUNER_LICENSE_EXPIRED: SAN Extension License expired - Disabling SAN Extension Tuner

Explanation SAN Extension License expired/not present - Disabling SAN Extension Tuner

Recommended Action No action is required.

SCHEDULER Messages

This section contains the SCHEDULER messages.

SCHEDULER-2

Message SCHEDULER-2-SCH_SYSLOG_MALLOC_ERR: Out of memory: [chars]

Explanation Process memory exhausted. Possible memory leak.

Recommended Action Contact TAC

Message SCHEDULER-2-SCH_SYSLOG_MTS_ERR: MTS error: [chars]

Explanation MTS operation failure

Recommended Action Contact TAC

Message SCHEDULER-2-SCH_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec]

Explanation Error while performing snapshot I/O to PSS

Recommended Action Contact TAC

Message SCHEDULER-2-SCH_SYSLOG_SDWRAP_ERR: Debug infrastructure initialization failed: [chars]

Explanation Debug infrastructure failed to initialize

Recommended Action Contact TAC

SCHEDULER-3

Message SCHEDULER-3-SCH_ERR: [chars]

Explanation Scheduler error

Recommended Action No action is required.

Message SCHEDULER-3-SCH_SYSLOG_FILE_ERR: [chars] Error: [chars]

Explanation File handling error

Recommended Action No action is required.

Message SCHEDULER-3-SCH_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] Error:[dec]

Explanation Error while performing I/O to PSS

Recommended Action Contact TAC

Message SCHEDULER-3-SCH_SYSLOG_USER_ERR: Description: Failed to execute job for user id [chars] Error:[dec]

Explanation Error while attempting to execute job for user. Possibly, the user is removed from the system.

Recommended Action Ensure the user exists. Make sure he is not a remotely authenticated user.

SCHEDULER-4

Message SCHEDULER-4-SCH_WARN: [chars]

Explanation Scheduler warning

Recommended Action No action is required.

SCHEDULER-6

Message SCHEDULER-6-SCH_MSG: [chars]

Explanation Scheduler Message

Recommended Action No action is required.

SCM Messages

SCM-2

Message SCM-2-SCMLCINSERTFAIL: [chars]

Explanation SCSI-TARGET

Recommended Action NONE

SCSI-TARGET Messages

This section contains the SCSI-TARGET messages.

SCSI-TARGET-2

Message SCSI-TARGET-2-PROC_OPEN_VHBA_DEVICE_FAIL: Failed to communicate with SCSI-target driver error: [hex]

Explanation SCSI-target process failed to communicate with its peer kernel driver [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'show scsi-target internal driver'

Message SCSI-TARGET-2-PROC_SET_SCSI_INDEX_FAIL: Failed to set SCSI index SCSI-target driver error: [hex]

Explanation SCSI-target process failed to set SCSI index with its peer kernel driver [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'show scsi-target internal driver'.

Message SCSI-TARGET-2-PROC_WWNM_GET_WWN_FAIL: Failed to get local controller pwwn from WWN Manager error: [hex] response: [hex]

Explanation SCSI-target process used wwnm_bwt_get_local_controller_wwn() api for the port wwn and it failed due to error [hex], response code [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using commands 'show process scpu' and 'show system internal sysmgr service all'. See WWN Manager system error codes for reason.

Message SCSI-TARGET-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex]

Explanation SCSI-target process pss initialization failure due to error [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.'

SCSI-TARGET-3

Message SCSI-TARGET-3-PROC_VSAN_GET_RATOV_FAIL: Failed to get vsan attribute RATOV from VSAN Manager, error: [hex]

Explanation SCSI-target process used the vsan_get_global_value() api for RATOV and it failed due to error [hex].

Recommended Action This is a non-fatal error. The default value for RATOV is used. Collect more information using commands 'show process cpu' and 'show system internal sysmgr service all'. See Vsan Manager system error codes for reason.

Message SCSI-TARGET-3-PSS_CREATE_FAIL: pss create runtime database failed due to error: [hex]

Explanation SCSI-target process pss create runtime database failure due to error [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [hex]

Explanation SCSI-target process pss delete runtime entry key [hex] failure due to error [hex].

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to error: [hex]

Explanation SCSI-target process pss set runtime max key failure due to error [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to error: [hex]

Explanation SCSI-target process pss set runtime max value failure due to error [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: [hex]

Explanation SCSI-target process pss open runtime database failure due to error [hex]. No SCSI discovery can be performed.

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to error: [hex]

Explanation SCSI-target process pss reload runtime database failure due to error [hex].

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to uri: [chars] failed due to error: [hex]

Explanation SCSI-target process pss snapshot of runtime debug to uri [string] failed due to error [hex].

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] failed due to error: [hex]

Explanation SCSI-target process pss snapshot of runtime to uri [string] failed due to error [hex].

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

Message SCSI-TARGET-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] failed due to error: [hex]

Explanation SCSI-target process pss store runtime entry key [hex] value [hex] failure due to error [hex].

Recommended Action Collect more information using command 'showflash'. See Pss System Error Codes For Reason.

SCSI-TARGET-7

Message SCSI-TARGET-7-SCSI_TARGET_DISCOVERED: SCSI-target discovered VSAN:[dec] FCID:[hex] prlisparm:[hex]

Explanation SCSI-target process discovered VSAN [dec] FCID [hex] prli service parameter [hex].

Recommended Action None

SDV Messages

This section contains the SDV messages.

SDV-2

Message SDV-2-RANDNUM_FAIL: Random number generation failed

Explanation Random number generation failed. Process has to exit due to FIPS compliance

Recommended Action No action is required.

SDV-3

Message SDV-3-ACL_CACHE_ERROR: ACL CACHE ERR, Trying to prig with no interface list

Explanation A Null interface list was generated for a ACL entry

Recommended Action No action is required.

Message SDV-3-ACL_ERROR: ACL API, [chars], failed with error [hex]

Explanation SDV invoked ACL API and received the error code. [chars] describes the API and 0x[hex] specifies the error.

Recommended Action No action is required.

Message SDV-3-ALLOC_FAILED: Failed for type [dec] size [dec]

Explanation SDM process could not allocate heap memory. [dec] is the memory type and [dec] is the size of memory

Recommended Action No action is required.

Message SDV-3-ASSERTION_FAILED: [chars]:[dec]

Explanation SDM process has hit an assert condition at file [chars] line number [dec]

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.

Message SDV-3-AUTO_FAILOVER_ERROR: [chars]

Explanation SDV Virtual-device failed to auto-fail over due to [chars]

Recommended Action No action is required.

Message SDV-3-BCAST_NOT_SUPPORTED: Broadcast attribute will be ignored for SDV devices

Explanation Broadcast attribute will be ignored for SDV devices

Recommended Action No action is required.

Message SDV-3-ENQUEUE_EVENT_FAIL: Unable to enqueue event into state machine

Explanation Unable to enqueue event into state machine

Recommended Action No action is required.

Message SDV-3-FCID_REWRITE_REQUEST_TO_ACL_FAILED: fcid rewrite [chars] request vsan [dec] vdev_id [dec] failed:[chars].

Explanation This happens when either after SDV retried the request few times or ACL experienced error while processing the request.

Recommended Action No action is required.

Message SDV-3-INIT_FAIL: [chars]

Explanation SDM process in it has failed due to [chars]

Recommended Action No action is required.

Message SDV-3-INTERNAL_ERR: [chars]

Explanation SDM process encountered an internal error due to [chars]

Recommended Action No action is required.

Message SDV-3-LOCK_FAILED: [chars]

Explanation An error occurred while acquiring the lock. The reason for the failure: [chars]

Recommended Action No action is required.

Message SDV-3-MERGE_ACTIVATION_FAILED: [chars]

Explanation Error while activating the merged SDV database due to [chars]

Recommended Action No action is required.

Message SDV-3-MERGE_CAP_FAILED: [chars]

Explanation SDV fabric merge failed because of incompatible capabilities [chars]

Recommended Action Compare SDV configuration in both fabrics and resolve the conflicts if any and commit the changes.

Message SDV-3-MERGE_FAILED: [chars]

Explanation SDV fabric merge failed due to [chars]

Recommended Action Check the error using show sdv merge status vsan <vsan-id

Message SDV-3-MTS_ERR: [chars]

Explanation SDM process encountered an MTS error due to [chars]

Recommended Action No action is required.

SDV-4

Message SDV-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING: failed:[chars]. Retrying the request again.

Explanation This happens when either any of the linecard being upgraded or ACL experienced error while processing the request.

Recommended Action No action is required.

SDV-6

Message SDV-6-INTERNAL_ERR_INFO: [chars]

Explanation SDM process encountered ignorable error due to [chars]

Recommended Action No action is required.

SDV-7

Message SDV-7-SRVCREATED: SDM Process started

Explanation SDM process has started

Recommended Action No action is required.

SECURITYD Messages

This section contains the SECURITYD messages.

SECURITYD-2

Message SECURITYD-2-FIPS_BYPASS_SELF_TEST_STATUS: FIPS Bypass self-test status: [chars]

Explanation Status of FIPS self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_CRNG_SELF_TEST_STATUS: FIPS CRNG self-test status: [chars]

Explanation Status of FIPS self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_CRYPTO_SELF_TEST_STATUS: FIPS [chars] Crypto self-test status: [chars]

Explanation Status of FIPS [chars] self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_IMAGE_INTEGRITY_SELF_TEST_STATUS: FIPS Image Integrity self-test status: [chars]

Explanation Status of FIPS [chars] self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_POST_ERROR_MSG: [chars]

Explanation Fips post Message

Recommended Action No action is required.

Message SECURITYD-2-FIPS_POST_MAINTENANCE: FIPS Test failed. Moving to maintenance mode

Explanation FIPS Test failed. Moving to maintenance mode

Recommended Action No action is required.

Message SECURITYD-2-FIPS_POST_TEST_FAILED: FIPS crypto-test failure: [dec]

Explanation FIPS crypto-test failed [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_POWERUP_SELF_TESTS_STATUS: FIPS power-up self-test status: [chars]

Explanation Status FIPS self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_POWERUP_SELF_TEST_STATUS: FIPS [chars] power-up self-test status: [chars]

Explanation Status of FIPS [chars] power-up self-test [chars]

Recommended Action No action is required.

Message SECURITYD-2-FIPS_SELF_TEST_FAILED: FIPS self-test failure: [chars]: [chars]

Explanation FIPS self-test failed [chars] for service [chars]

Recommended Action No action is required.

Message SECURITYD-2-PROGRAM_EXIT: security/accounting daemon exiting: [chars]

Explanation Security/accounting daemon is exiting.

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.

SECURITYD-3

Message SECURITYD-3-SECURITY_ERR_MSG: [chars]

Explanation Security Message

Recommended Action No action is required.

Message SECURITYD-3-NVRAMFAILURE: nvram failure

Explanation Nvram can not be read/written to. Hence accounting log can not be stored there

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.

SECURITYD-6

Message SECURITYD-6-ACCOUNTING_MESSAGE: [chars]

Explanation Accounting Message

Recommended Action No action is required.

Message SECURITYD-6-CHANGE_PASSWD: changing passwd for [chars]

Explanation Changing passwd for [chars]

Recommended Action No action is required.

Message SECURITYD-6-DELETE_STALE_USER_ACCOUNT: deleting expired user account:[chars]

Explanation Deleting expired user account of [chars]

Recommended Action No action is required.

Message SECURITYD-6-FIPS_MODE_SET_FAILED: Error when setting FIPS mode: [chars]

Explanation FIPS mode failed [chars]

Recommended Action No action is required.

Message SECURITYD-6-FIPS_MODE_SET: FIPS mode is [chars] for service [chars]

Explanation FIPS mode is changed [chars] [chars]

Recommended Action No action is required.

Message SECURITYD-6-FIPS_POST_INFO_MSG: [chars]

Explanation Fips post Information Message

Recommended Action No action is required.

Message SECURITYD-6-SECURITY_INFO_MSG: [chars]

Explanation Security Info Message

Recommended Action No action is required.

SECURITYD-7

Message SECURITYD-7-SECURITY_DBG_MSG: [chars]

Explanation Security Debug Message

Recommended Action No action is required.

SENSOR_USD Messages

This section contains the SENSOR_USD messages.

SENSOR_USD-2

Message SENSOR_USD-2-SNSM_SYSLOG_INIT_FAILED: Sensor Mgr Initialization failed. Component [chars]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down: [chars]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation failed

Explanation Sensor Manager syslog message

Recommended Action No action is required.

SENSOR_USD-3

Message SENSOR_USD-3-MSG_SNSM_SYS_MEM_ALOC_FAILURE: Sensor Mgr Error in allocing mem: [dec], Error code = [dec]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_API_CALL_FAILURE: Sensor Mgr Error in [chars] call errno=[dec]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_SYSLOG_BAD_MTS_MSG: Sensor Mgr Received bad MTS message: [dec]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_SYSLOG_MTS_PROCESS_ERROR: Sensor Mgr Error in processing MTS message: [dec], Error code = [hex]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_SYS_DEQUE_PENDING_QUE_FAILURE: Sensor Mgr Error in Dequing pend Que: %p, Error code = [hex]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_SYS_ENQUE_PENDING_QUE_FAILED: Sensor Mgr Error in queuing to pending queue: %p, Error code = [hex]

Explanation Sensor Manager syslog message

Recommended Action No action is required.

Message SENSOR_USD-3-SNSM_SYS_MTS_RECV_FAILURE: Sensor Mgr Error in receving MTS mesg

Explanation Sensor Manager syslog message

Recommended Action No action is required.

SENSOR_USD-5

Message SENSOR_USD-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started

Explanation Sensor Manager syslog message

Recommended Action No action is required.

SENSOR_MGR Messages

This section contains the SENSOR_MGR messages.

SENSOR_MGR-2

Message SESSION-MGR-2-DB_UNLOCK_FAILED: Failed to unlock the database for session:[chars]

Explanation Session-Manager failed to unlock the database for session: [chars]

Recommended Action No action is required.

SENSOR_MGR-3

Message SESSION-MGR-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec] size [dec]

Explanation Session-mgr process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]

Recommended Action No action is required.

SENSOR_MGR-4

Message SESSION-MGR-4-ISSU_FAILED: [chars]:[hex]

Explanation Session manager failed ISSU because of [string] and error: [hex]

Recommended Action No action is required.

SENSOR Messages

This section contains the SENSOR messages.

SENSOR-0

Message SENSOR-0-DC3_SENSOR_MSG: [chars]

Explanation SENSOR log emergency message

Recommended Action No action is required.

SENSOR-3

Message SENSOR-3-DC3_SENSOR_MSG1: [chars]

Explanation SENSOR log message

Recommended Action No action is required.

SESSION-MGR Messages

This section contains the SESSION-MGR messages.

SESSION-MGR-2

Message SESSION-MGR-2-DB_UNLOCK_FAILED: Failed to unlock the database for reason:[chars]

Explanation Session-Manager failed to unlock the database for session: [chars]

Recommended Action No action is required.

SESSION-MGR-3

Message SESSION-MGR-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec] size [dec]

Explanation Session-mgr process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]

Recommended Action No action is required.

SESSION-MGR-4

Message SESSION-MGR-4-ISSU_FAILED: [chars]:[hex]

Explanation Session manager failed ISSU because of: [string] and error: [hex]

Recommended Action No action is required.

SFC Messages

This section contains the SFC messages.

SFC-3

Message SFC-3-ERROR: [chars]

Explanation SCSI Flow Client encountered an 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.

SFM Messages

This section contains the SFM messages.

SFM-2

Message SFM-2-NO_LICENSE_WARNING: SCSI Flow Manager is shutting down as no license is available.

Explanation License required for continued SCSI Flow Manager operation is not available.

Recommended Action No action is required.

SFM-6

Message SFM-6-LICENSE_VALID: A valid license for SCSI Flow Manager has been obtained

Explanation A valid license for SCSI Flow Manager has been obtained

Recommended Action No action is required.

SIM Messages

This section contains the SIM messages.

SIM-2

Message SIM-2-IF_CRITICAL_FAILURE: (Debug syslog) Critical failure: [chars], [chars]

Explanation There was a critical failure in the component.

Recommended Action Please follow instructions on the syslog.

Message SIM-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled. Reason:[chars])

Explanation The interface encountered an error while configuring it

Recommended Action In most cases, you can recover using following commands 'config terminal', 'interface [char]', 'shutdown', 'noshutdown' on the interface or removing and re-inserting the fibre optic cable.'

Message SIM-2-IF_DOWN_LINK_FAILURE_CRIT: 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

Message SIM-2-SEQ_TIMEOUT: Component [chars] timed out on response to opcode [chars] ([chars])

Explanation Some component did not respond to a request in stipulated time.

Recommended Action None

Message SIM-2-SYSLOG_SIM_CRITICAL: Critical failure: [chars]

Explanation There was a critical failure in the component.

Recommended Action Please collect system tech-support

SIM-3

Message SIM-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface [chars] is down (Channel error disabled)

Explanation This interface belongs to a PortChannel and the PortChannel is error disabled

Recommended Action Perform 'shut' and 'noshutdown' on the Port Channel interface that it belongs to

Message SIM-3-IF_ERROR_VLANS_REMOVED: VLANs [chars] on Interface [chars] are removed from suspended state.

Explanation The VLANs on an interface are being removed from the suspended state

Recommended Action No action is required.

Message SIM-3-IF_ERROR_VLANS_SUSPENDED: VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])

Explanation The VLANs on an interface are being suspended due to some protocol action

Recommended Action No action is required.

Message SIM-3-IF_SFP_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message SIM-3-IF_SFP_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message SIM-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported

Explanation The transceiver for the interface specified in the Message is not a Cisco supported module

Recommended Action Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced

Message SIM-3-IF_XCVR_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message SIM-3-IF_XCVR_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

SIM-4

Message SIM-4-IF_NON_QUALIFIED_TRANSCEIVER: Non-qualified transceiver on interface [chars] was detected

Explanation The transceiver for the interface specified has not been qualified on this platform for this software release

Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details

Message SIM-4-IF_SFP_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message SIM-4-IF_XCVR_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

SIM-5

Message SIM-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]

Explanation Interface is admin up

Recommended Action No action is required.

Message SIM-5-IF_BANDWIDTH_CHANGE: Interface [chars], bandwidth changed to [chars] Kbit

Explanation Bandwidth of the interface (port channel) has changed and this change is updated

Recommended Action No action is required.

Message SIM-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down)

Explanation Interface has been configured to be administratively down

Recommended Action Perform noshutdown

Message Message SIM-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change)

Explanation FCIP interface temporarily down due to reconfiguration

Recommended Action No action is required.

Message SIM-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 Perform 'noshutdown' on the Port Channel interface that it belongs to

Message SIM-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 Retry the configuration again

Message SIM-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.

Message SIM-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.

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

Explanation Isolated due to domain manager being disabled

Recommended Action No action is required.

Message SIM-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 not responding

Recommended Action No action is required.

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

Explanation Isolating this interface due to the remote end being isolated

Recommended Action No action is required.

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

Explanation Isolated due to domain overlap

Recommended Action No action is required.

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

Explanation ELP failed on the interface

Recommended Action Check the output of 'show port internal info' in the 'ELP failure reason' field'

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

Explanation Trunk protocol failed

Recommended Action 'show port internal event-history msgs' will indicate the trunk protocol exchanges to determine why it failed

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

Explanation ESC failed on the interface

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

Message SIM-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, the interface is administratively enabled

Message SIM-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

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

Explanation The FCOT has been removed

Recommended Action Insert an FCOT

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

Explanation Fcot inserted is not a supported one

Recommended Action Please contact customer support for a list of authorized transceiver vendors

Message SIM-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)

Explanation The modules hardware has failed

Recommended Action Collect more information about failed module using command 'show module internal all module'

Message SIM-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

Message SIM-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 Perform a 'show port internal info' to determine the list of modes supported on this interface

Message SIM-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 Get the allowed receive B2B credit size from 'show port internal info'

Message SIM-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''

Message SIM-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 Perform a 'show port internal info' to determine the range of speed supported on this interface

Message SIM-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, check the output of 'show port internal event-history' to determine what it is waiting for.

Message SIM-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)

Explanation Interface removed

Recommended Action No action is required.

Message SIM-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

Message SIM-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure)

Explanation Diag failed on the interface

Recommended Action Collect more information about failed interface using command

Message SIM-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

Message SIM-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.

Message SIM-5-IF_DOWN_NONE: Interface [chars] is down ([chars])

Explanation Interface is down with a possible reason.

Recommended Action Collect more information about port using command 'show port internal info /event-history' to determine why it went down

Message SIM-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating)

Explanation The loop port has been put into non participating mode

Recommended Action No action is required.

Message SIM-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.

Message SIM-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down)

Explanation Parent interface is down

Recommended Action No action is required.

Message SIM-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 This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection

Message SIM-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 The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection

Message SIM-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

Message SIM-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 perform a shutdown' and a 'noshutdown'

Message SIM-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.

Message SIM-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.

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

Explanation Module that has the tunnel source port of this FCIP interface is not fully online

Recommended Action The module that has the tunnel src port is coming online. Please use show mod to find module status

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

Explanation Tunnel port source interface unbound

Recommended Action No action is required.

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

Explanation Tunnel source port of this FCIP interface has been removed

Recommended Action The src interface with ip address that matches the ip address of the bound entity is removed. This happens normally due to the module on which the src interface exists is removed

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

Message SIM-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 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

Message SIM-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended)

Explanation This interface belongs to a PortChannel and has been suspended due to an error while bringing it up

Recommended Action Perform a 'shutdown' and a 'noshutdown'.If this happens again obtain output of 'show port internal info/event-history' on the interface

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

Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Interface is down due to maximum retransmission failure

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ipaddr

Message SIM-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 TCP persist timer expired

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Upgrade of the linecard software is in progress

Recommended Action No action is required.

Message SIM-5-IF_DOWN_VRF_UNUSABLE: Interface [chars] is down (Vrf down)

Explanation The VRF for which this interface is a member is removed

Recommended Action No action is required.

Message SIM-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 with the VSANs configured on the remote end

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

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

Explanation Isolated due to a failure during zone merge

Recommended Action No action is required.

Message SIM-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.

Message SIM-5-IF_DUPLEX: Interface [chars], operational duplex mode changed to [chars]

Explanation Operational duplex mode has changed when link came up

Recommended Action No action is required.

Message SIM-5-IF_ERRDIS_RECOVERY: Interface [chars] is being recovered from error disabled state (Last Reason:[chars])

Explanation Interface is being recovered from error disabled state

Recommended Action No action is required.

Message SIM-5-IF_HARDWARE: Interface [chars], hardware type changed to [chars]

Explanation There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed

Recommended Action No action is required.

Message SIM-5-IF_L2MP_MODE: Interface [chars], l2mp-mode changed to [chars]

Explanation The l2mp-mode on the port has changed

Recommended Action No action is required.

Message SIM-5-IF_RX_FLOW_CONTROL: Interface [chars], operational Receive Flow Control state changed to [chars]

Explanation Operational receive flow control has changed when link came up

Recommended Action No action is required.

Message SIM-5-IF_TRUNK_DOWN: Interface [chars], vlan [chars] down

Explanation Interface [chars] is trunking, VLANs [chars] are down

Recommended Action The following commands will help determine why this VSAN is down on this interface: show interface, show port internal info interface VSAN, show port internal event-history interface vsan

Message SIM-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up

Explanation Interface [chars] is trunking, VLANs [chars] are up

Recommended Action No action is required.

Message SIM-5-IF_TX_FLOW_CONTROL: Interface [chars], operational Transmit Flow Control state changed to [chars]

Explanation Operational transmit flow control has changed when link came up

Recommended Action No action is required.

Message SIM-5-IF_UP: Interface [chars] is up [chars]

Explanation Interface is up in mode specified, if applicable

Recommended Action No action is required.

Message SIM-5-SPEED: Interface [chars], operational speed changed to [chars]

Explanation Operational speed has changed when link came up

Recommended Action No action is required.

Message SIM-5-STORM_CONTROL_ABOVE_THRESHOLD: Traffic in port [chars] exceeds the configured threshold [chars]

Explanation Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped

Recommended Action Identify source of traffic storm

Message SIM-5-STORM_CONTROL_BELOW_THRESHOLD: Traffic in port [chars] has fallen below the configured threshold [chars]

Explanation Traffic on specified port has returned to within configured storm-control threshold

Recommended Action No action is required.

 

SKSD Messages

This section contains the SKSD messages.

SKSD-2

Message SKSD-2-SKSD_CRYPT_SERVICE_CRIT: Encryption-Service: [chars]

Explanation Encryption Service critical errors.

Recommended Action No action is required.

SKSD-3

Message SKSD-3-SKSD_CRYPT_SERVICE_ERR: Encryption-Service: [chars]

Explanation Encryption Service errors.

Recommended Action No action is required.

Message SKSD-3-SKSD_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode: [chars]

Explanation FIPS mode initialization error

Recommended Action No action is required.

Message SKSD-3-SKSD_FIPS_MODE_SELFTEST: FIPS POST for [chars] [chars]

Explanation FIPS Selftest Result

Recommended Action No action is required.

SKSD-4

Message SKSD-4-SKSD_CRYPT_SERVICE_WARN: Encryption-Service: [chars]

Explanation Encryption Service warnings.

Recommended Action No action is required.

SKSD-5

Message SKSD-5-SKSD_CRYPT_SERVICE_NOTICE: Encryption Service: [chars]

Explanation Encryption Service updates.

Recommended Action No action is required.

Message SKSD-5-SKSD_EXIT: Keystore Application Exiting: [chars]

Explanation Keystore Program exiting

Recommended Action No action is required.

Message SKSD-5-SKSD_FUNC: Keystore Operation: [chars]

Explanation Keystore Event upon a receiving a request

Recommended Action No action is required.

Message SKSD-5-SKSD_HW_INIT: Hardware Keystore Init done

Explanation Hardware Keystore Init completed

Recommended Action No action is required.

Message SKSD-5-SKSD_HW_RESET: Hardware Reset: [chars]

Explanation Hardware Reset

Recommended Action No action is required.

Message SKSD-5-SKSD_HW: Smartcard: [chars]

Explanation Smartcard Presence

Recommended Action No action is required.

Message SKSD-5-SKSD_INIT: Keystore Application Init: [chars]

Explanation Keystore Program Init

Recommended Action No action is required.

Message SKSD-5-SKSD_KEY_ADD: Key added

Explanation Key added to keystore

Recommended Action No action is required.

Message SKSD-5-SKSD_KEY_DELETE: Key deleted

Explanation Key deleted from keystore

Recommended Action No action is required.

Message SKSD-5-SKSD_MKEY_INSTALL: Installing a Master Key on the smartcard(s)

Explanation Installing a new Master Key on the smartcard(s)

Recommended Action No action is required.

Message SKSD-5-SKSD_SUP_STATE: Supervisor card new state: [dec]

Explanation Supervisor state change

Recommended Action No action is required.

Message SKSD-5-SKSD_SW_INIT: Software Keystore Init done

Explanation Software Keystore Init completed

Recommended Action No action is required.

SKSD-6

Message SKSD-6-SKSD_CRYPT_SERVICE_INFO: Encryption Service: [chars]

Explanation Encryption Service informational updates.

Recommended Action No action is required.

SKT_USD Messages

This section contains the SKT_USD messages.

SKT_USD-2

Message SKT_USD-2-SKT_RF_CRC_ERR: [chars]

Explanation Skytrain received packet(s) from fabric with CRC error

Recommended Action No action is required.

SKT_USD-6

Message SKT_USD-6-SKT_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

SKYLINE_APP Messages

This section contains the SKYLINE_APP messages.

SKYLINE_APP-SLOT#-2

Message SKYLINE_APP-SLOT#-2-SKYLINE_APP_EXITED: Skyline driver application exited (syserr = [dec], errno = [dec])

Explanation Skyline driver application exited

Recommended Action No action is required.

SME_CPP Messages

This section contains the SME_CPP messages.

SME_CPP-2

Message SME_CPP-2-IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED: [chars] cannot be bound as the interfaces reached the maximum IT Nexus limit

Explanation IT Load Balancing failed

Recommended Action No action is required.

Message SME_CPP-2-LOG_ERR_SME_CTRL_LUN_PATH_MISCONFIG: Control LUN [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that are not configured.

Explanation A single lun with multiple paths has some non configured paths. Please configure all lun paths.

Recommended Action No action is required.

Message SME_CPP-2-LOG_ERR_SME_DIFF_LUN_MISCONFIG: Lun [chars] and [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] configured as one device.

Explanation Two different luns configured as one device. Please fix configuration.

Recommended Action No action is required.

Message SME_CPP-2-LOG_ERR_SME_LICENSE_EXPIRED: SME License expired - Disabling [chars]

Explanation SAN Media Encryption License expired/not present - Disabling SME

Recommended Action No action is required.

Message SME_CPP-2-LOG_ERR_SME_TAPE_LUN_PATH_MISCONFIG: Tape Drive [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that are not configured.

Explanation A single lun with multiple paths has some non configured paths. Please configure all lun paths.

Recommended Action No action is required.

Message SME_CPP-2-LOG_ERR_SME_TOM_ABORTED: SME Cluster [chars] Message Id: [hex] aborted

Explanation An SME Cluster Message was aborted by the Cluster process

Recommended Action No action is required.

Message SME_CPP-2-LOG_WARN_SME_LICENSE_GRACE: No SME License. Feature will be shut down after a grace period of approximately [dec] days

Explanation SAN Media Encryption feature on grace period. Please acquire actual license.

Recommended Action No action is required.

Message SME_CPP-2-SME_INIT_FAILED: Initialization failed for SME: [chars], Reason: [hex]

Explanation Initialization failed for SME

Recommended Action No action is required.

SME_CPP-3

Message SME_CPP-3-LOG_ERR_SME_DBSYBC_REJECT: SME Database Synchronization [chars] for a New Cluster (Id 0x%llx) Rejected; Reason - [chars].

Explanation A switch can be part of only one SME cluster

Recommended Action No action is required.

Message ME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_NOT_FOUND: crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not find coned ([chars] if_index: [hex])

Explanation The data preparation failed since crypto node assigned for data preparation is not found

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_OVERLOAD: crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not be assigned a crypto node ([chars] if_index: [hex]) due to max limit. current active sessions: [dec]

Explanation The data preparation failed since crypto node is already handling maximum number of data preparation sessions

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_NAME_MISMATCH: The KMC DG: [chars] and CD NAME: [chars] corresponding to VID: [chars] PID: [chars] DID: [chars] doesn’t match cdisk DG: [chars] and CD NAME: [chars]

Explanation The discovered vendor id information not match the crypto disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_VPD_FIXED: The VPD of cdisk DG: [chars] CD NAME: [chars] has been changed to VPD in KMC VID: [chars] PID: [chars] DID: [chars] and old VPD of disk has been removed

Explanation The vendor id information has been modified to be consistent with KMC

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_VPD_MISMATCH: The VID:[chars] PID:[chars] DID: [chars] of cdisk DG: [chars] CD NAME: [chars] does not match VPD in KMC VPD: [chars] PID: [chars] DID: [chars]

Explanation The discovered vendor id information not match the crypto disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL1: ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VPD mismatch disk. Disk VPD VID: [chars] PID: [chars] DID: [chars] ITL VID: [chars] PID: [chars] DID: [chars]

Explanation The given path does not belong to the configured disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL2: ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars] belongs to a different cdisk DG: [chars] CD NAME: [chars]

Explanation The given path does not belong to the configured disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL3: CFG ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars] doesn’t belong to DG: [chars] CD NAME: [chars] whose VID: [chars] PID: [chars] DID: [chars]

Explanation The given path does not belong to the disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL4: CFG ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] of DG: [chars] CD: [chars] has VID: [chars] PID: [chars] DID: [chars] belonging to DG: [chars] CD NAME: [chars]

Explanation The given path does not belong to the disk

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CLUSTER_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] and security mode [dec], but the DPP has state from a previous instance of a cluster [chars] with ID [chars] and security mode [dec].

Explanation DPP has persistent state about a previous cluster membership incarnation, but the interface is part of a different cluster.

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE2: but the DPP has a different certificate (len [dec] fingerprint [chars]).

Explanation DPP has persistent state about a previous cluster membership with a different crypto node identity.

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE: SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars] with certificate (len [dec] fingerprint [chars]).

Explanation DPP has persistent state about a previous cluster membership with a different crypto node identity.

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars], but the DPP is identified as [chars].

Explanation DPP has persistent state about a previous cluster membership on a different switch or module.

Recommended Action No action is required.

Message SME_CPP-3-LOG_ERR_SME_IT_NEX_USED_FOR_DP: IT CL: [chars] H: [chars] T: [chars] VSAN: [dec] has PATH lunid: [chars] for disk (dg: [chars] cd: [chars]) so rediscover not issued

Explanation The IT nexus is currently in use by data preparation so rediscover not permitted since it disrupts data preparation. Please stop data preparation first

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_CDISK_DP_FAILED: SME cdisk ([chars]) data preparation failed ([chars]), disk-group ([chars]), cluster (name [chars], id %llx)

Explanation SME cdisk data preparation failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_DISK_ASL_FAILED: [chars]

Explanation SME KMC disk asl token generation failed for the given device discovery info

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KEY_CREATE_FAILED: Key creation ([chars]) failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME key creation failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_DELETE_ALL_KEYS_FAILED: Delete all keys in cluster failed to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC delete keys failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_DELETE_KEYS_FAILED: Delete keys for [chars] failed to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC delete keys failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_KEEPALIVE_FAILED: Keepalive to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC Keepalive failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_KEY_ENTITY_LOOKUP_FAILED: Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC key lookup failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_KEY_LOOKUP_FAILED: Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC key lookup failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_KEY_UPDATE_FAILED: Key updates ([chars]) to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC key updates failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_KMC_MODIFY_DISK_STATUS_FAILED: Key ([chars]) update disk status in KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC disk status update failed

Recommended Action No action is required.

Message SME_CPP-3-LOG_SME_REPLACE_SMARTCARD_ABORT: Replace smartcard process (type [chars]) aborted [chars] with reason ([chars]) in SME cluster (name [chars], id %llx)

Explanation SME KMC connection up

Recommended Action No action is required.

Message SME_CPP-3-SME_FIPS_MODE_ERROR: SME FIPS error: [chars]

Explanation SME module FIPS mode error

Recommended Action No action is required.

Message SME_CPP-3-SME_MAX_CLUSTERS_LIMIT_EXCEEDED: SME maximum clusters limit of [dec] exceeded

Explanation The maximum SME clusters limit exceeded

Recommended Action No action is required.

SME_CPP-5

Message SME_CPP-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface [chars] exceeded the optimum IT Nexus limit

Explanation Interface Flow Limit

Recommended Action No action is required.

Message SME_CPP-5-LOG_ERR_SME_INTF_MISMATCH_NOT_PART_OF_ANY_CLUSTER: SME interface [chars] not part of any cluster, but the DPP has state from a previous instance of a cluster [chars] with ID [chars].

Explanation DPP has persistent state about a previous cluster membership incarnation, but the interface is not part of any cluster.

Recommended Action No action is required.

Message SME_CPP-5-LOG_ERR_SME_INTF_MISMATCH_NOT_PROVISIONED: SME is not provisioned on slot [dec], but the DPP has state from a previous instance as a crypto node [chars] of a cluster [chars] with ID [chars].

Explanation DPP has persistent state about a previous cluster membership incarnation, but the switch has not provisioned the interface for SME.

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_CDISK_DP_SUCCESS: SME cdisk ([chars]) data preparation succeeded, disk-group ([chars]), cluster (name [chars], id %llx)

Explanation SME cdisk data preparation succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_CLUSTER_INTF_ADDED: SME interface now part of cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len [dec] fingerprint [chars]).

Explanation Interface added to cluster successfully

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_CLUSTER_INTF_REMOVED: SME interface now removed from cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len [dec] fingerprint [chars]).

Explanation Interface removed from cluster successfully

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_INTERFACE_DOWN: SME Interface ([chars]) DOWN

Explanation SAN Interface was brought down

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_INTERFACE_UP: SME Interface ([chars]) is UP

Explanation SAN Interface was brought up

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_IT_NEXUS_FAILURE: [chars]. [chars] bind failure. Reason: [chars]: [hex]

Explanation SME IT Nexus bind failed

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KEY_CREATE_SUCCESS: Key created ([chars]) successfully in SME cluster (name [chars], id %llx)

Explanation SME key creation succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_CONNECTION_DOWN: Connection to KMC server [chars] is down with reason ([chars]) from local switch in SME cluster (name [chars], id %llx)

Explanation SME KMC connection down

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_CONNECTION_INIT_FAIL: Connection initialization to KMC server [chars] from local switch in SME cluster (name [chars], id %llx) failed with error ([chars])

Explanation SME KMC connection initialization failed.

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_CONNECTION_INIT_PASS: Connection initialization to KMC server [chars] from local switch in SME cluster (name [chars], id %llx) succeeded

Explanation SME KMC connection initialization succeeded.

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_CONNECTION_UP: Connection to KMC server [chars] is up from local switch in SME cluster (name [chars], id %llx)

Explanation SME KMC connection up.

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_DELETE_ALL_KEYS_SUCCESS: Delete all keys in cluster to KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC delete keys succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_DELETE_KEYS_SUCCESS: Delete keys for [chars] to KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC delete keys succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_KEY_ENTITY_LOOKUP_NOKEY: Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)

Explanation SME KMC key lookup resulted in no key

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_KEY_ENTITY_LOOKUP_SUCCESS: Key ([chars]) lookup from KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC key lookup succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_KEY_LOOKUP_SUCCESS: Key ([chars]) lookup from KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC key lookup succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_KEY_UPDATE_SUCCESS: Key updates ([chars]) to KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC key updates succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_KMC_MODIFY_DISK_STATUS_SUCCESS: Key ([chars]) update disk status in KMC server succeeded, SME cluster (name [chars], id %llx)

Explanation SME KMC disk status update succeeded

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_MASTER_KEY_REKEYED: Master Key rekeyed successfully in SME cluster (name [chars], id %llx)

Explanation SME Master Key rekeyed

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_COMMIT: Replace smartcard process (type [chars]) committed [chars] in SME cluster (name [chars], id %llx)

Explanation SME KMC connection up

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_START: Replace smartcard process (type [chars]) initiated [chars] in SME cluster (name [chars], id %llx)

Explanation SME KMC connection up

Recommended Action No action is required.

Message SME_CPP-5-LOG_SME_TAPE_VOLUME_GROUP_REKEYED: Tape volume group ([chars]) rekeyed successfully in SME cluster (name [chars], id %llx)

Explanation SME Master Key rekeyed

Recommended Action No action is required.

Message SME_CPP-5-SME_DISABLED: SME Disabled

Explanation SME Service Disabled

Recommended Action No action is required.

Message SME_CPP-5-SME_DISK_DP_WAIT_KMC: crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting KMC validation of VPD

Explanation The data preparation is waiting for validation of VPD with KMC

Recommended Action No action is required.

Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_ADD: crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting paths to be added

Explanation The data preparation is waiting for paths to be added to the crypto disk

Recommended Action No action is required.

Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_CFG: crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting for the path (fabric: [chars] hwwn: 0x%Lx twwn: 0x%Lx vsan: [dec] lun_id: [chars]) to be added

Explanation The data preparation is waiting for discovered path to be added

Recommended Action No action is required.

Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_DISC: (DG: [chars] CD NAME: [chars]) is waiting for configured path (fabric: [chars] hwwn: 0x%Lx twwn: 0x%Lx vsan: [dec] lun_id: [chars]) to be discovered

Explanation The data preparation is waiting for configured path to be discovered

Recommended Action No action is required.

Message SME_CPP-5-SME_ENABLED: SME Enabled

Explanation SME Service enabled

Recommended Action No action is required.

SME_CPP-SLOT#-2

Message SME_CPP-SLOT#-2-LOG_ERR_SME_DEVICE_MISCONFIG: Different configured Devices under same physical LUN - Old Cluster Name:[chars] New Cluster Name:[chars] Old Group Name:[chars] New Group Name:[chars] Old Device Name:[chars] New Device Name:[chars]

Explanation Different configured devices under same physical LUN

Recommended Action No action is required.

Message SME_CPP-SLOT#-2-LOG_ERR_SME_ITL_MISCONFIG: Different physical LUNs under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:[chars] Serial Num:[chars] Serial Num:[chars]

Explanation Different physical LUNs under same Tape Device

Recommended Action No action is required.

Message SME_CPP-SLOT#-2-LOG_ERR_SME_LUN_MISCONFIG: Different physical LUNs under same ITL - Old Serial Num:[chars] New Serial Num:[chars]

Explanation Different physical LUNs under same ITL

Recommended Action No action is required.

Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_BYPASS_ENC: Bypassing encryption for partly written tape - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]

Explanation This tape is currently not being encrypted

Recommended Action No action is required.

Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_CTH_FAIL: Bypassing encryption for current tape on failed CTH verification - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]

Explanation This tape is currently not being encrypted because CTH verification has failed in DPP

Recommended Action No action is required.

Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_KEY_ERR: Getting tape keys from SUP failed - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]

Explanation There was a failure retrieving keys from SUP for this tape

Recommended Action No action is required.

SME_CPP-SLOT#-3

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISC_TIMEOUT: Module:[dec] Host-Target:[chars]

Explanation Discovery on this IT Nexus is taking too long, please check status

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CAP_CHANGED: capacity changed for lun VID: [chars] PID: [chars] DID: [chars] previous max_lba: 0x%Lx blk_sz: [dec] discovered max_lba: [hex] blk_sz: [dec] on ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx

Explanation The capacity of the disk seems to have changed

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CPP_ITL_MISCONFIG: Disk ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx has been misconfigured under a non disk lun

Explanation Disk ITL has been misconfigured under non disk lun

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CPP_IT_MISCONFIG: Tape device has been misconfigured under disk IT nexus [chars] hence skipping discovery of ITLs under this IT nexus

Explanation Remove misconfigured disk path under the tape device

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CRYPTO_UPDATE_ITL_AUTH_FAIL: ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx with discovered VID: [chars] PID: [chars] DID: [chars] marked by SUP as failed authentication

Explanation SUP detected authentication failure on path

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ENTITY_INVALID: disk entity index invalid from KMC (cluster: [chars] DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]

Explanation KMC returned an invalid disk entity index

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_INVALID_CAPACITY: Disk capacity not supported.IT nexus:[chars] LUN Id:0x%Lx VID: [chars] PID : [chars] max_lba=[hex] max_lba64=0x%Lx

Explanation The reported disk capacity is zero

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ITL_CREATE_VPD_MISMATCH: ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx VID: [chars] PID: [chars] DID: [chars] doesnt match cdisk DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]

Explanation The configured path does not belong to this disk

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ITL_MISCONFIG: ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx part of DG: [chars] CD NAME: [chars] is misconfigured as the ITL VPD VID: [chars] PID: [chars] DID: [chars] belongs to a different cdisk DG: [chars] CD NAME: [chars]

Explanation The configured path does not belong to this disk

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_KEY_INVALID: (CLUSTER: [chars] DG: [chars] CD NAME: [chars] keytype: [dec] keyguid: [chars] invalid

Explanation KMC returned an invalid disk key

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_KMC_VERIFY_PENDING: cluster: [chars] DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]

Explanation Vpd of the discovered path pending verification with KMC

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_MISCONFIG: A disk device misconfiguration under disk config - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Lx

Explanation A disk device misconfigured under disk config

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_PHYENCRYPT_FAILED: CL: [chars] DG: [chars] CD: [chars] VID: [chars] PID: [chars] DID: [chars] ISAPI_PhyCopyEncrypt() failed isapi status: [dec] copy status: [hex] scsi status: [hex] data preparation failed

Explanation ISAPI_PhyCopyEncrypt() failed causing data preparation to fail

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_VPD_CHANGED: VID, PID and DID changed on ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx previous VID: [chars] PID : [chars] DID: [chars] current VID: [chars] PID: [chars] DID: [chars]

Explanation The VPD of the disk seems to have changed

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_VPD_MISMATCH: ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx failed authentication DISK VPD(VID id: [chars] PID: [chars] DID: [chars]) ITL(VID: [chars] PID: [chars] DID: [chars])

Explanation The configured path does not belong to this disk

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_DP_TEST_IO_ERR: IT nexus [chars] lun [chars] isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]

Explanation ITL DP TEST IO failure, please check status

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_ITL_CPP_ERR: Module:[dec] Host-Target [chars] LunID:[chars]

Explanation ITL failure seen on CPP, please check status

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_IT_NEXUS_UNSUPPORTED: IT nexus [chars] has both disks and tapes which is an unsupported configuration

Explanation IT nexus has an unsupported mix of tape and disk devices

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_NON_DISK_MISCONFIG: A non-disk device misconfigured under disk config - Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Lx

Explanation A non disk device misconfigured under disk config

Recommended Action No action is required.

Message SME_CPP-SLOT#-3-LOG_ERR_SME_NON_TAPE_MISCONFIG: A non-tape device misconfigured under tape config - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Ld

Explanation A disk misconfigured under tape config

Recommended Action No action is required.

SME_CPP-SLOT#-4

Message SME_CPP-SLOT#-4-LOG_WARN_SME_MAX_BLOCK_LEN: Maximum block length [dec] of tape drive is 256K or less - [chars] LunID:[chars] VendorID:[chars] ProdID:[chars] Serial Num:[chars] Cluster:[chars] Tape Device:[chars]

Explanation This tape drive may not operate correctly with SME

Recommended Action No action is required.

SNMPD Messages

This section contains the SNMPD messages.

SNMPD-1

Message SNMPD-1-ALERT: SNMP log alert: [chars]

Explanation SNMP log alert message.

Recommended Action No action is required.

SNMPD-2

Message SNMPD-2-CRITICAL: SNMP log critical: [chars]

Explanation SNMP log critical message.

Recommended Action No action is required.

SNMPD-3

Message SNMPD-3-ERROR: SNMP log error: [chars]

Explanation SNMP log Message.

Recommended Action No action is required.

SNMPD-4

Message SNMPD-4-WARNING: SNMP log warning: [chars]

Explanation SNMP log warning message.

Recommended Action No action is required.

SNMPD-5

Message SNMPD-5-NOTIFICATION: SNMP log notification: [chars]

Explanation SNMP log notification message.

Recommended Action No action is required.

SNMPD-6

Message SNMPD-6-INFO: SNMP log informational: [chars]

Explanation SNMP log info message.

Recommended Action No action is required.

SNMPD-7

Message SNMPD-7-DEBUG: SNMP log debugging: [chars]

Explanation SNMP log debug message.

Recommended Action No action is required.

SPAN Messages

This section contains the SPAN messages.

SPAN-2

Message SPAN-2-MEM_FULL: Memory allocation failed

Explanation Memory allocation failed

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.

SPAN-3

Message SPAN-3-IPC_FAIL: IPC Error

Explanation Internal IPC error

Recommended Action No action is required.

Message SPAN-3-SYSINFO_TIMEOUT: Span timed out waiting for response from port manager for sys info

Explanation Span request for critical system information from port manager timed out. So, span on the new active is exiting and system manager will restart Span.

Recommended Action No action is required.

SPAN-5

Message SPAN-5-ATL_VSAN_DEFAULT_ALL: Default to all VSANs for SPAN egress session

Explanation Generation 2 fabric switches support only one VSAN filter for egress SPAN session. If no or more than one VSANs are specified, SPAN will default to use all VSANs for the egress SPAN session

Recommended Action No action is required.

Message SPAN-5-SPAN_CFG_REJECT_SRC_VSAN_FILTER_NOT_SUPPORTED: Source interface [[chars]] in dir [[chars]] removed from session [[dec]].

Explanation Interface level VSAN filters is not supported

Recommended Action No action is required.

Message SPAN-5-SPAN_CFG_REJECT_VSAN_SRC_PRESENT: Source VSAN [[dec]] removed from session [[dec]].

Explanation Source VSANs are removed from the session as mixing of interface and VSANs is not supported.

Recommended Action No action is required.

Message SPAN-5-SPAN_PSS_CORRUPTION: Span is starting stateless due to PSS corruption

Explanation Due to unrecoverable PSS corruption error, SPAN starts stateless without any configuration

Recommended Action No action is required.

Message SPAN-5-STATELESS_RESTART_ON_ACTIVE: Span is restarting as Span on active sup was restarted stateless.

Explanation Due to unrecoverable error, Span on active supervisor was restarted stateless. So, the standby Span restarts to get in sync with the stateless Span on active.

Recommended Action No action is required.

Message SPAN-5-STATELESS_RESTART: Span is restarting stateless.

Explanation Due to unrecoverable error, Span is starting stateless. The currently active sessions will not be preserved. The user will have to reenter all the configuration.

Recommended Action No action is required.

SPAN-6

Message SPAN-6-SESSION_DOWN: Session [dec] is inactive ([chars])

Explanation Session [dec] is inactive now. Traffic for this session is no longer spanned

Recommended Action Check the reason for session inactive using command 'show span session' and take corresponding action.

Message SPAN-6-SESSION_UP: Session [dec] is active, destination SD port [chars]

Explanation Session [dec] is active now. You can monitor Spanned traffic at the destination SD port

Recommended Action No action is required.

Message SPAN-6-STATELESS_SWITCHOVER: Span is starting stateless after switchover.

Explanation Active sessions are not preserved across switchover. Span is starting stateless and the configuration will be reapplied to get back the active configuration.

Recommended Action No action is required.

SPI Messages

This section contains the SPI messages.

SPI-SLOT#-2

Message SPI-SLOT#-2-SPI_INFO: [chars]

Explanation SPI Informational message

Recommended Action No action is required.

STATSCLIENT Messages

This section contains the STATSCLIENT messages.

STATSCLIENT-2

Message STATSCLIENT-2-STATSCL_CRIT: [chars]

Explanation StatsClient Critical Message

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.

STATSCLIENT-3

Message STATSCLIENT-3-STATSCL_ERR2: [chars] [dec] [dec]

Explanation StatsClient 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.

Message STATSCLIENT-3-STATSCL_ERR: [chars] [dec]

Explanation StatsClient 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.

STATSCLIENT-6

Message STATSCLIENT-6-STATSCL_INFO: [chars]

Explanation StatsClient Flow Message

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.

STATSPROFILER Messages

This section contains the STATSPROFILER messages.

STATSPROFILER-2

Message STATSPROFILER-2-IF_CRITICAL_FAILURE: (Debug syslog) Critical failure: [chars], [chars]

Explanation There was a critical failure in the component.

Recommended Action Please follow instructions on the syslog.

Message STATSPROFILER-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled. Reason:[chars])

Explanation The interface encountered an error while configuring it

Recommended Action Collect more information about failed interface using command show port internal all interface [char]'. In most cases, you can recover using a 'shutdown' followed a 'noshutdown' on the interface on the interface or removing and re-inserting the fibre optic cable.

Message STATSPROFILER-2-IF_DOWN_LINK_FAILURE_CRIT: 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

Message STATSPROFILER-2-SEQ_TIMEOUT: Component [chars] timed out on response to opcode [chars] ([chars])

Explanation Some component did not respond to a request in stipulated time.

Recommended Action None

Message STATSPROFILER-2-SYSLOG_STATSPROFILER_CRITICAL: Critical failure: [chars]

Explanation There was a critical failure in the component.

Recommended Action Please collect system tech-support

STATSPROFILER-3

Message STATSPROFILER-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface [chars] is down (Channel error disabled)

Explanation This interface belongs to a PortChannel and the PortChannel is error disabled

Recommended Action Perform 'shut' and 'no shutdown' on the Port Channel interface that it belongs to

Message STATSPROFILER-3-IF_ERROR_VLANS_REMOVED: VLANs [chars] on Interface [chars] are removed from suspended state.

Explanation The VLANs on an interface are being removed from the suspended state

Recommended Action No action is required.

Message STATSPROFILER-3-IF_ERROR_VLANS_SUSPENDED: VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])

Explanation The VLANs on an interface are being suspended due to some protocol action

Recommended Action No action is required.

Message STATSPROFILER-3-IF_SFP_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message STATSPROFILER-3-IF_SFP_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message STATSPROFILER-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported

Explanation The transceiver for the interface specified in the Message is not a Cisco supported module

Recommended Action Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced

Message STATSPROFILER-3-IF_XCVR_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message STATSPROFILER-3-IF_XCVR_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

STATSPROFILER-4

Message STATSPROFILER-4-IF_NON_QUALIFIED_TRANSCEIVER: Non-qualified transceiver on interface [chars] was detected

Explanation The transceiver for the interface specified has not been qualified on this platform for this software release

Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details

Message STATSPROFILER-4-IF_SFP_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message STATSPROFILER-4-IF_XCVR_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

STATSPROFILER-5

Message STATSPROFILER-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]

Explanation Interface is admin up

Recommended Action No action is required.

Message STATSPROFILER-5-IF_BANDWIDTH_CHANGE: Interface [chars], bandwidth changed to [chars] Kbit

Explanation Bandwidth of the interface (port channel) has changed and this change is updated

Recommended Action No action is required.

Message STATSPROFILER-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down)

Explanation Interface has been configured to be administratively down

Recommended Action Perform 'noshutdown'

Message STATSPROFILER-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change)

Explanation FCIP interface temporarily down due to reconfiguration

Recommended Action No action is required.

Message STATSPROFILER-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel admin down)

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

Recommended Action Perform 'no shutdown' on the Port Channel interface that it belongs to

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

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

Recommended Action Retry the configuration again

Message STATSPROFILER-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.

Message STATSPROFILER-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.

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

Explanation Isolated due to domain manager being disabled

Recommended Action No action is required.

Message STATSPROFILER-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 not responding

Recommended Action No action is required.

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

Explanation Isolating this interface due to the remote end being isolated

Recommended Action No action is required.

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

Explanation Isolated due to domain overlap

Recommended Action No action is required.

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

Explanation ELP failed on the interface

Recommended Action Check the output of 'show port internal info' in the 'ELP failure reason' field

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

Explanation Trunk protocol failed

Recommended Action 'show port internal event-history msgs' will indicate the trunk protocol exchanges to determine why it failed

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

Explanation ESC failed on the interface

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

Message STATSPROFILER-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, the interface is administratively enabled

Message STATSPROFILER-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

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

Explanation The FCOT has been removed

Recommended Action Insert an FCOT

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

Explanation Fcot inserted is not a supported one

Recommended Action Please contact customer support for a list of authorized transceiver vendors

Message STATSPROFILER-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)

Explanation The modules hardware has failed

Recommended Action Collect more information about failed module using command 'show module internal all module'

Message STATSPROFILER-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

Message STATSPROFILER-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 Perform a 'show port internal info' to determine the list of modes supported on this interface

Message STATSPROFILER-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 Get the allowed receive B2B credit size from 'show port internal info'

Message STATSPROFILER-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'

Message STATSPROFILER-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 Perform a 'show port internal info' to determine the range of speed supported on this interface

Message STATSPROFILER-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, check the output of 'show port internal event-history' to determine what it is waiting for.

Message STATSPROFILER-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)

Explanation Interface removed

Recommended Action No action is required.

Message STATSPROFILER-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

Message STATSPROFILER-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure)

Explanation Diag failed on the interface

Recommended Action Collect more information about failed interface using command 'attach module' to connect to module

Message STATSPROFILER-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

Message STATSPROFILER-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.

Message STATSPROFILER-5-IF_DOWN_NONE: Interface [chars] is down ([chars])

Explanation Interface is down with a possible reason.

Recommended Action Collect more information about port using command 'show port internal info/event-history' to determine why it went down

Message STATSPROFILER-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating)

Explanation The loop port has been put into non participating mode

Recommended Action No action is required.

Message STATSPROFILER-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.

Message STATSPROFILER-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down)

Explanation Parent interface is down

Recommended Action No action is required.

Message STATSPROFILER-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 This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection

Message STATSPROFILER-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 The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection

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

Explanation This is a Port Channel interface and all its members are operationally down

Recommended Action Enable at least one of the PortChannel members

Message STATSPROFILER-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 perform a 'shutdown' and a 'noshutdown'

Message STATSPROFILER-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.

Message STATSPROFILER-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.

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

Explanation Module that has the tunnel source port of this FCIP interface is not fully online

Recommended Action The module that has the tunnel src port is coming online. Please use show mod to find module status

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

Explanation Tunnel port source interface unbound

Recommended Action No action is required.

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

Explanation Tunnel source port of this FCIP interface has been removed

Recommended Action The src interface with ip address that matches the ip address of the bound entity is removed. This happens normally due to the module on which the src interface exists is removed

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

Message STATSPROFILER-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 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

Message STATSPROFILER-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended)

Explanation This interface belongs to a PortChannel and has been suspended due to an error while bringing it up

Recommended Action Perform a 'shutdown' and a 'no shutdown'. If this happens again obtain output of 'show port internal info/event-history' on the interface

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

Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Interface is down due to maximum retransmission failure

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

Message STATSPROFILER-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 TCP persist timer expired

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Upgrade of the linecard software is in progress

Recommended Action No action is required.

Message STATSPROFILER-5-IF_DOWN_VRF_UNUSABLE: Interface [chars] is down (Vrf down)

Explanation The VRF for which this interface is a member is removed

Recommended Action No action is required.

Message STATSPROFILER-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 with the VSANs configured on the remote end

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

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

Explanation Isolated due to a failure during zone merge

Recommended Action No action is required.

Message STATSPROFILER-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.

Message STATSPROFILER-5-IF_DUPLEX: Interface [chars], operational duplex mode changed to [chars]

Explanation Operational duplex mode has changed when link came up.

Recommended Action No action is required.

Message STATSPROFILER-5-IF_ERRDIS_RECOVERY: Interface [chars] is being recovered from error disabled state (Last Reason:[chars])

Explanation Interface is being recovered from error disabled state.

Recommended Action No action is required.

Message STATSPROFILER-5-IF_HARDWARE: Interface [chars], hardware type changed to [chars]

Explanation There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed.

Recommended Action No action is required.

Message STATSPROFILER-5-IF_L2MP_MODE: Interface [chars], l2mp-mode changed to [chars]

Explanation The l2mp-mode on the port has changed

Recommended Action No action is required.

Message STATSPROFILER-5-IF_RX_FLOW_CONTROL: Interface [chars], operational Receive Flow Control state changed to [chars]

Explanation Operational receive flow control has changed when link came up

Recommended Action No action is required.

Message STATSPROFILER-5-IF_TRUNK_DOWN: Interface [chars], vlan [chars] down

Explanation Interface [chars] is trunking, VLANs [chars] are down

Recommended Action The following commands will help determine why this VSAN is down on this interface: show interface, show port internal info interface VSAN, show port internal event-history interface vsan

Message STATSPROFILER-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up

Explanation Interface [chars] is trunking, VLANs [chars] are up.

Recommended Action No action is required.

Message STATSPROFILER-5-IF_TX_FLOW_CONTROL: Interface [chars], operational Transmit Flow Control state changed to [chars]

Explanation Operational transmit flow control has changed when link came up

Recommended Action No action is required.

Message STATSPROFILER-5-IF_UP: Interface [chars] is up [chars]

Explanation Interface is up in mode specified, if applicable.

Recommended Action No action is required.

Message STATSPROFILER-5-SPEED: Interface [chars], operational speed changed to [chars]

Explanation Operational speed has changed when link came up.

Recommended Action No action is required.

Message STATSPROFILER-5-STORM_CONTROL_ABOVE_THRESHOLD: Traffic in port [chars] exceeds the configured threshold [chars]

Explanation Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped.

Recommended Action Identify source of traffic storm.

Message STATSPROFILER-5-STORM_CONTROL_BELOW_THRESHOLD: Traffic in port [chars] has fallen below the configured threshold [chars]

Explanation Traffic on specified port has returned to within configured storm-control threshold.

Recommended Action No action is required.

STP Messages

This section contains the STP messages.

STP-2

Message STP-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.

Explanation A BPDU was received in the interface specified in the Message that has the spanning tree BPDU Guard feature enabled. As a result, the interface was administratively shut down.

Recommended Action Either remove the device sending BPDUs or disable the BPDU Guard feature. The BPDU Guard feature can be locally configured on the interface or globally configured on all ports that have port-fast enabled. After the conflict has been resolved, re-enable the interface by entering the <CmdBold>

Message STP-2-BLOCK_DETECTED_PVST_PEER: Blocking port [chars] [PVST peer detected].

Explanation The listed interface received SSTP BPDU indicating that peer is running PVST and will be held in spanning tree blocking state until the interface stops receiving SSTP BPDUs

Recommended Action Either enable PVST simulation configuration for the interface or make sure the port peer is not PVST switch

Message STP-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent local vlan.

Explanation The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the Port VLAN ID (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of the listed interface.

Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.

Message STP-2-BLOCK_PVID_PEER: Blocking [chars] on [chars]. Inconsistent peer vlan.

Explanation The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the port VLAN Id (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of interface on the peer switch to which the listed interface is connected.

Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.

Message STP-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port [chars] [chars].

Explanation BPDUs were not received from a neighboring switch on the interface that has spanning tree Bridge Assurance configured. As a result, the interface was moved to the spanning tree Blocking state

Recommended Action LOG_STD_NO_ACTION

Message STP-2-BRIDGE_ASSURANCE_UNBLOCK: Bridge Assurance unblocking port [chars] [chars].

Explanation The interface listed in the message has been restored to normal spanning tree state after receiving BPDUs from the neighboring L2 switch/bridge

Recommended Action LOG_STD_NO_ACTION

Message STP-2-DISPUTE_CLEARED: Dispute resolved for port [chars] on [chars].

Explanation The listed interface has stopped receiving Inferior BPDUs with designated role and state as learning and/or forwarding. The Dispute has been resolved and if the port is still designated, it will be taken out of the blocking state as and when appropriate.

Recommended Action LOG_STD_NO_ACTION

Message STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars].

Explanation The spanning tree has detected a Dispute on this interface. The BPDU received from the peer is Inferior with designated role and state as learning and/or forwarding. Since this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as disputed in order to prevent possible loops from being created

Recommended Action Issue the <CmdBold>

Message STP-2-IPC_PROCESSING_ERR: Error in processing IPC message: Opcode = [dec], Error code = [hex]

Explanation STP encountered an error in processing an MTS message. The error and message are specified in the Message

Recommended Action No action is required.

Message STP-2-L2GW_BACKBONE_BLOCK: L2 Gateway Backbone port inconsistency blocking port [chars] on [chars].

Explanation A BPDU was received on the listed interface which advertises a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as L2 Gateway Backbone port inconsistent in order to prevent a suboptimal spanning tree topology to form.

Recommended Action Issue the <CmdBold>

Message STP-2-L2GW_BACKBONE_UNBLOCK: L2 Gateway Backbone port inconsistency cleared unblocking port [chars] on [chars].

Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge. The L2 Gateway Backbone port inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate.

Recommended Action LOG_STD_NO_ACTION

Message STP-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on [chars].

Explanation The spanning tree message age timer has expired because and no BPDUs were received from the designated bridge. Since this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as loop guard inconsistent in order to prevent possible loops from being created

Recommended Action Issue the <CmdBold>

Message STP-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars].

Explanation The spanning tree loop guard configuration for the listed interface has been changed. If enabled, the interface will be put into blocking state and marked as loop guard inconsistent when the message age timer expires because no BPDU were received from the designated bridge. This feature is mainly used to detect unidirectional links

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required.

Message STP-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on [chars].

Explanation The listed interface has received a BPDU and therefore if the inconsistency was due to an unidirectional link failure, now the problem is not there anymore. The loop guard inconsistency is cleared for the interface which is taken out of the blocking state if appropriate.

Recommended Action LOG_STD_NO_ACTION

Message STP-2-PVSTSIM_FAIL: Blocking [chars] port [chars]: Inconsistent [chars] PVST BPDU received on VLAN [dec], claiming root [chars]

Explanation When a MST switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently better than all the PVST+ messages if the port is designated or consistently worse than all the PVST+ messages if the port is root. If this constraint is not respected, the port on the MST switch is blocked in order to prevent a potential bridging loop

Recommended Action When STP is converging after a new switch, or switch port is added to the topology, this condition may happen transiently. The port unblocks automatically in such cases. If the port remains blocked, identify the root bridge as reported in the message, and configure a worse or better priority for the VLAN spanning tree consistent with the CIST role on the port of the MST switch. There could be more inconsistencies than the message indicates, and the port will not recover until all such inconsistencies are cleared. If you cannot determine which other VLANs have inconsistencies, disable and reenable the port. This message will appear again and specify another VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.

Message STP-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port [chars].

Explanation The listed interface is no longer receiving PVST BPDUs advertising an information inconsistent with the CIST port information. The PVST Simulation Inconsistency is cleared and the interface returns to normal operation

Recommended Action LOG_STD_NO_ACTION

Message STP-2-RANDNUM_FAIL: [chars]

Explanation There was a critical error during random number generation. [chars] indicates details of the error

Recommended Action No action is required.

Message STP-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars] [chars].

Explanation The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU is discarded.

Recommended Action No action is required.

Message STP-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].

Explanation The listed interface received a SSTP BPDU that is tagged with a VLAN id that does not match the VLAN id on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.

Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.

Message STP-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars].

Explanation A BPDU was received on the listed interface which advertizes a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as root guard inconsistent in order to prevent a suboptimal spanning tree topology to form.

Recommended Action Issue the <CmdBold>

Message STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars].

Explanation The spanning tree root guard configuration for the listed interface has been changed. If enabled, any BPDU received on this interface which advertizes a superior spanning tree root bridge to that already in use will cause the interface to be put into blocking state and marked as root guard inconsistent.

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required.

Message STP-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on [chars].

Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge. The root guard inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate.

Recommended Action LOG_STD_NO_ACTION

Message STP-2-SET_PORT_STATE_FAIL: Port state change req to PIXM failed, status = [hex] [[chars]] vdc [dec], tree id [dec], num ports [dec], ports [chars] state [chars], opcode [chars], msg id ([dec]), rr_token [hex]

Explanation The port set port state has failed. check port

Recommended Action LOG_STD_NO_ACTION

Message STP-2-SET_PORT_STATE_TIMEOUT: Port state change req to PIXM timedout after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars] state [chars], opcode [chars], msg id ([dec]), rr_token [hex]

Explanation The port set port state has timedout. check port

Recommended Action LOG_STD_NO_ACTION

Message STP-2-STP_INIT: STP initialization of [chars] [chars]

Explanation STP initialization failed

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.

Message STP-2-STP_ISSU_LC_RESET: STP resetting LC [dec] to prevent Loops during ISSU caused by a topology change in the network. Peer on [chars] [chars] could not be Disputed

Explanation This can happen as a result of a topology change in the network while the Linecard was undergoing ISSU. Since STP cannot change the port state to blocking on the Linecard undergoing ISSU, it will first try to prevent the Loop by causing a Dispute on the peer ports forcing them into blocking state. But if the peer does not support Dispute mechanism, and STP detects a potential Loop, it will reset the Linecard to prevent the Loop

Recommended Action LOG_STD_NO_ACTION

Message STP-2-UNBLOCK_CONSIST_PORT: Unblocking port [chars] on [chars]. Port consistency restored.

Explanation The Port VLAN ID and/or Port Type inconsistencies have been resolved and spanning tree will now unblock the listed interface of the listed spanning tree instance as appropriate.

Recommended Action LOG_STD_NO_ACTION

Message STP-2-UNBLOCK_DETECTED_PVST_PEER: Unblocking port [chars] [PVST peer detected].

Explanation The listed interface has stopped receiving SSTP BPDUs and so will be restored to normal spanning tree state

Recommended Action LOG_STD_NO_ACTION

Message STP-2-VLAN_PORT_LIMIT_EXCEEDED: The number of vlan-port instances exceeded [[chars] mode] recommended limit of [dec]

Explanation The total number of individual VLAN ports, in the spanning tree mode specified in the Message, has exceeded the limit specified in the Message. VLANs can be counted more than once; if VLAN 1 is carried on 10 interfaces, it will count as 10 VLAN ports. Note that bundling is ignored for purposes of this count; if 8 interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as 1 VLAN ports.

Recommended Action Reduce the number of trunks and VLANs configured in the switch. Keep the VLAN port count below the recommended limit specified in the configuration documentation. Enter the <CmdBold>

Message STP-2-VPC_PEERSWITCH_CONFIG_DISABLED: vPC peer-switch configuration is disabled. Please make sure to change spanning tree bridge priority as per the recommended guidelines.

Explanation The vPC peer-switch configuration has been changed. If enabled, please make sure to configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make sure to change spanning tree bridge priority as per the recommended guidelines.

Recommended Action Verify that this is the desired configuration and follow the vPC peer-switch recommended guidelines.

Message STP-2-VPC_PEERSWITCH_CONFIG_ENABLED: vPC peer-switch configuration is enabled. Please make sure to configure spanning tree bridge priority as per recommended guidelines to make vPC peer-switch operational.

Explanation The vPC peer-switch configuration has been changed. If enabled, please make sure to configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make sure to change spanning tree bridge priority as per the recommended guidelines.

Recommended Action Verify that this is the desired configuration and follow the vPC peer-switch recommended guidelines.

Message STP-2-VPC_PEER_LINK_INCONSIST_BLOCK: vPC peer-link detected [chars] blocking [chars] [chars].

Explanation VPC Peer-link detected the STP inconsistency mentioned in the message. This will impact the STP topology for vPCs and can cause frame duplications. As a result, the interface was moved to the spanning tree Blocking state

Recommended Action LOG_STD_NO_ACTION

Message STP-2-VPC_PEER_LINK_INCONSIST_ERRDISABLE: vPC Peer-link detected [chars]. Disabling [chars].

Explanation VPC Peer-link detected the STP inconsistency mentioned in the message. This will impact the STP topology for vPCs and can cause frame duplications. As a result, the vPC Peer-link was administratively shut down.

Recommended Action Please resolve the inconsistency reported in this message on the vPC Peer link. After the conflict has been resolved, re-enable the interface by entering the <CmdBold>

Message STP-2-VPC_PEER_LINK_INCONSIST_UNBLOCK: vPC peer-link inconsistency cleared unblocking [chars] [chars].

Explanation VPC Peer-link inconsistency is cleared and the vPC interface listed in the message has been restored to normal spanning tree state.

Recommended Action LOG_STD_NO_ACTION

STP-3

Message STP-3-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent port type.

Explanation The listed interface is being held in spanning tree blocking state until the port type inconsistency is resolved.

Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.

Message STP-3-PORT_SELF_LOOPED: Received BPDU src mac same as that of port. Port self loopback detected. Port [chars] being disabled

Explanation The source MAC address contained in a BPDU received on the listed interface matches the MAC address assigned to that interface This indicates the possibility that a port is looped back to itself, possibly due to a diagnostic cable being plugged in. The interface will be administratively shutdown.

Recommended Action Check the interface configuration and any cable plugged into the interface. Once problem resolved, re-enable interface by doing a no shutdown in the interface configuration. Copy the Message as it is printed and also copy the output of a show interface for the interface listed in the Message.

Message STP-3-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk [chars] [chars].

Explanation A SSTP BPDU was received on the listed interface that was not operationally a trunk.

Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (none, ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.

STP-4

Message STP-4-FORWARDTIME_CONFIG_CHANGE: Forward Delay time change to [dec] seconds for instance [chars] is not recommended as it can cause STP data loops during High Availability Dual-Supervisor Switchover and In-Service Software Upgrade

Explanation It is strongly recommended to avoid changing forward delay time value to less than the default value of 15 seconds since it can cause STP data loops during High Availability Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release notes.

Recommended Action Please change the forward delay time to be greater than or equal to the default value of 15 seconds

Message STP-4-HELLOTIME_CONFIG_CHANGE: Hello time change to [dec] seconds for instance [chars] is not recommended as it can trigger STP Topology Changes during High Availability Dual-Supervisor Switchover and In-Service Software Upgrade

Explanation It is strongly recommended to avoid changing Hello time value to less than the default value of 2 seconds since it can trigger STP Topology change during High Availability Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release notes.

Recommended Action Please change the hello time to be greater than or equal to the default value of 2 seconds.

Message STP-4-MAC_ADDR_FLUSH_REQ_TIMEOUT: MAC Address Flush req to L2FM timedout after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars], opcode [chars], msg id ([dec]), rr_token [hex]

Explanation The MAC Address Flush Request to L2FM has timedout. check port

Recommended Action LOG_STD_NO_ACTION

STP-6

Message STP-6-FIRST_BPDU_TX: First BPDU transmitted

Explanation First BPDU transmitted.

Recommended Action No action is required.

Message STP-6-MST_DIGEST: MST digest changed to [chars], pre-std digest changed to [chars]

Explanation MST Region configuration has changed

Recommended Action LOG_STD_NO_ACTION

Message STP-6-MST_PORT_BOUNDARY: Port [chars] [chars] as MST Boundary port

Explanation MST Boundary port status of the specified port is changed

Recommended Action LOG_STD_NO_ACTION

Message STP-6-MST_PORT_PRE_STANDARD: Port [chars] [chars] as MST Pre-standard port.

Explanation MST pre-standard status of the specified port is changed

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_ADDED: Interface [chars], added to [chars] with role [chars], state [chars], cost [dec], priority [dec], link-type [chars]

Explanation This spanning tree port has been added

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_COST: Port [chars] instance [chars] cost changed to [dec]

Explanation The spanning tree port cost has changed for the specified port

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_DELETED: Interface [chars], removed from [chars]

Explanation This spanning tree port has been deleted

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_LINK_TYPE: Port [chars] instance [chars] link changed to [chars]

Explanation The spanning tree port link type has changed for the specified port

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_PRIORITY: Port [chars] instance [chars] priority changed to [dec]

Explanation The spanning tree port priority has changed for the specified port

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_RANGE_ADDED: Interface [chars] added to [chars] with cost [dec], priority [dec], link-type [chars]

Explanation This spanning tree port has been added

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_RANGE_DELETED: Interface [chars] removed from [chars]

Explanation This range spanning tree logical ports has been deleted

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_RANGE_ROLE: new_role= [chars] interface= [chars] [chars]

Explanation The role of the range of spanning tree logical ports has changed

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_RANGE_STATE: new_state= [chars] interface= [chars] [chars]

Explanation The range of Spanning-Tree logical ports have changed state.

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_ROLE: Port [chars] instance [chars] role changed to [chars]

Explanation The spanning tree port role has changed for the specified port

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PORT_STATE: Port [chars] instance [chars] moving from [chars] to [chars]

Explanation The Spanning-Tree port has changed state.

Recommended Action LOG_STD_NO_ACTION

Message STP-6-PRESTD_NEIGH: This switch has received a pre-standard MST BPDU on port [chars]: Invoking pre-standard MST BPDU transmission on this port.

Explanation The switch has received a pre-standard MST BPDU on a port. The switch will automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs.

Recommended Action LOG_STD_NO_ACTION

Message STP-6-ROOT: Root bridge for [chars] changed to [chars]

Explanation The spanning tree root bridge has changed

Recommended Action LOG_STD_NO_ACTION

Message STP-6-SERVICE_UP: Initialized [chars]

Explanation STP line 2.

Recommended Action No action is required.

Message STP-6-STATE_CREATED: Internal state created [chars]

Explanation STP has created its internal state stateless/stateful [chars].

Recommended Action No action is required.

SVC_BATTERY Messages

This section contains the SVC_BATTERY messages.

SVC_BATTERY-SLOT#-2

Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_OPERATIONAL: Battery [dec] temperature [dec] C is outside the operational range (-10C to 65C).

Explanation The battery temperature is outside the operational range (-10C to 65C).

Recommended Action Verify fan operation with [show environment fan], and take action to cool down the switch.

Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_PRESENT: Battery [dec] is not present.

Explanation The line card does not have sufficient number of batteries. Two batteries are needed.

Recommended Action Remove the line card and plug in batteries in the battery slots that are empty.

Message SVC_BATTERY-SLOT#-2-CHARGING_DISABLED: Temperature outside permitted range for battery charging (5C-40C).

Explanation The temperature of the linecard is not within the range to permit battery charging.

Recommended Action Make sure the temperature of the linecard is between 5C and 40C

Message SVC_BATTERY-SLOT#-2-CHARGING_FAILURE: Charging failure in battery [dec] ([hex]).

Explanation The module encountered failures while charging a battery.

Recommended Action Replace the battery.

Message SVC_BATTERY-SLOT#-2-CLOCK_INCORRECT: System clock is running behind, battery conditioning will be affected.

Explanation The Vegas system clock is running behind the actual time. This will affect the battery conditioning.

Recommended Action Use clock set CLI command to set the correct time

Message SVC_BATTERY-SLOT#-2-COMMUNICATION_FAILURE: Communication failure with battery [dec].

Explanation The module encountered failures while communicating with a battery.

Recommended Action Replace the battery.

Message SVC_BATTERY-SLOT#-2-CONDITIONING_DISABLED: Temperature outside permitted range for battery conditioning (5C-40C).

Explanation The temperature of the linecard is not within the range to permit battery conditioning.

Recommended Action Make sure the temperature of the linecard is between 5C and 40C

Message SVC_BATTERY-SLOT#-2-DISCHARGING_FAILURE: Discharging failure in battery [dec] ([hex]).

Explanation The module encountered failures while discharging a battery.

Recommended Action Replace the battery.

SVC_BATTERY-SLOT#-4

Message SVC_BATTERY-SLOT#-4-BATTERY_CAPACITY_LOW: Battery capacity is below the required threshold.

Explanation The battery is lower than the required threshold.

Recommended Action Make sure the temperature is within the range to allow charging.

SVC_BATTERY-SLOT#-6

Message SVC_BATTERY-SLOT#-6-BATTERY_CAPACITY_OK: Battery capacity is above the required threshold.

Explanation The battery is above the required threshold.

Recommended Action No action is required.

Message SVC_BATTERY-SLOT#-6-CONDITIONING_CANCELLED: Temperature outside permitted range for battery conditioning (5C-40C). Battery [dec] conditioning canceled.

Explanation The temperature of the linecard is not within the range to permit battery conditioning.

Recommended Action Make sure the temperature of the linecard is between 5C and 40C

Message SVC_BATTERY-SLOT#-6-CONDITIONING_COMPLETED: Conditioning of battery [dec] completed successfully.

Explanation Conditioning process started for a battery is completed successfully.

Recommended Action No action is required.

Message SVC_BATTERY-SLOT#-6-CONDITIONING_RESUMED: Conditioning of battery [dec] resumed.

Explanation Conditioning process for a battery is resumed.

Recommended Action No action is required.

Message SVC_BATTERY-SLOT#-6-CONDITIONING_STARTED: Conditioning of battery [dec] started.

Explanation Conditioning process started for a battery

Recommended Action No action is required.

SVC Messages

This section contains the SVC messages.

SVC-0

Message SVC-0-NODE_EMERG_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

SVC-1

Message SVC-1-NODE_ALERT_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

SVC-2

Message SVC-2-NODE_CRIT_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

Message SVC-2-SVC_SYSLOG_INIT_FAILED: Initialization failed for SVC: [chars], Reason: [hex]

Explanation Initialization failed for SVC

Recommended Action No action is required.

Message SVC-2-SVC_SYSLOG_NO_PORT_CHAN: Too many PortChannels allocated by user for interface [chars]

Explanation SVC interface needs PortChannels to operate. Too many PortChannels have been allocated by the user for the interface to operate correctly.

Recommended Action Please delete unneeded user configured PortChannels and shutdown the SVC interface. Once complete, please bring the SVC interface back up.

Message SVC-2-SVC_SYSLOG_PATH_FAILURE: System health detected SVC packet path failure for [chars].

Explanation The CSM has been brought down by the System Health monitor. System Health has detected a failure in the packet path between the SVC interface on the CSM and the backplane. This System Health test is run periodically.

Recommended Action Issue a “no shutdown” on the SVC interface to bring the node back online. If a subsequent packet path failure occurs, the CSM module should be replaced.

Message SVC-2-SVC_SYSLOG_URIFS_FAILURE: [chars] is unreachable for reason: [chars]

Explanation SVC interface modflash is not accessible. Modflash is the name of the filesystem local to the SVC interface, and is typically used for core dumps and temporary file transfers.

Recommended Action Please shutdown and bring up the SVC interface in question to regain access to the modflash filesystem.

SVC-3

Message SVC-3-NODE_ERR_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_ACTIVATE_CLUSTER_IP_FAILED) Activate cluster IP failed [chars]

Explanation Unable to activate the cluster IP for the config node. It will not be possible to execute configuration commands.

Recommended Action 1. Shutting the interfaces of the node will force this node out of the cluster and cause another node to become the config node, which should restore the ability to execute configuration commands. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_FAILURE) Battery Failed [chars]

Explanation The battery module on the Caching Services Module has failed. The nodes on the CSM will have shutdown. Other log entries may accompany this error.

Recommended Action Reload the Caching Services Module. If the error persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DISK_FAILURE) Internal Disk Drive Failed [chars]

Explanation The internal disk drive for the node on the Caching Services Module has failed. The node will have shutdown. Other log entries may accompany this error.

Recommended Action Reload the Caching Services Module. If the error persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DUMP_RESTORE_FAILED) Restore of hardened data failed [chars]

Explanation Restore of customer data failed. This error will be accompanied by other log entries.

Recommended Action Examine the log for other error entries and follow the actions recommended. If no other entries are found: 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INVALID_BATT_CAPACITY) Get battery capacity failed [chars]

Explanation The process was unable to get the battery capacity. Possibly due to communication failures with the CPP processor in the line card. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_OPEN_COMMITTED_FILE_FAILED) Error attempting to open file [chars]

Explanation Process was unable to open the committed file. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_SET_BATT_THRESHOLD_FAILED) Set battery threshold failed [chars]

Explanation The process was unable to set the battery threshold. Possibly due to fatal communication failures with the power management module in the line card or the power management module has crashed. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_NODE_DISENFRANCHISED) Node missing [chars]

Explanation A node is missing from the cluster.

Recommended Action 1. If it is not obvious which node in the cluster has failed, check the status of the nodes and find the node with a status of offline. 2. Repair the failing node. 3. When the repair has been completed, this error will automatically be marked as fixed. 4. Check the node status. If all the nodes in the cluster are now online, but the error in the log has not been marked as fixed, manually mark the error as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_CLUSTER_PATH_FAILURE) Cluster path failure [chars]

Explanation A cluster path has failed. The node is unable communicate with all the other nodes in the cluster.

Recommended Action 1. Repair the fibre-channel network fabric. 2. Check the status of the node port. If the status of the port shows as online, mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_CPU_QUANTITY) Processor change detected [chars]

Explanation The Caching Services Module is failing.

Recommended Action 1. Replace the Caching Services Module. 2. Check node status. If all nodes show a status of online, mark the error you have just repaired fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_DISK_FULL) Node hard disk full [chars]

Explanation The error that is logged in the cluster error log indicates a software problem in the cluster.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Delete files from the /dumps directory. 3. Run a configuration dump and a logged data dump. Save the dump data. 4. Ask IBM Product Support for assistance. 5. Mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_FAIL) Logical Fibre Channel port reported failed [chars]

Explanation No active/functioning logical FC port was detected by the software.

Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_QUANTITY) Logical Fibre Channel port missing [chars]

Explanation No active/functioning FC port was detected by the software.

Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_PORT_QUANTITY) Logical Fibre Channel port reported not operational [chars]

Explanation No active/functioning logical FC port was detected by the software.

Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_NODE_WARMSTART) Node warmstarted due to software error [chars]

Explanation The error that is logged in the cluster error log indicates a software problem in the cluster.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_POWER_DOMAIN) Power domain error [chars]

Explanation The two nodes in an IO group are on the same Caching Services Module.

Recommended Action Determine what the configuration should be. Remove one of the nodes and add a node to the IO group which is not on the same Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MDISK_GROUP_OFFLINE) A Managed Disk group is offline [chars]

Explanation An Mdisk group is offline.

Recommended Action 1. Repair the enclosure or disk controller. 2. Start a cluster discovery operation. 3. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MED_ERRS_TOO_HIGH) Media errors on back-end Managed Disk [chars]

Explanation Media errors on backend managed disk.

Recommended Action 1. Repair the enclosure or disk controller. 2. Include the managed disk into the cluster. 3. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_BASE_EVENT_RESOURCE_RAN_OUT) Software error [chars]

Explanation The error that is logged in the cluster error log indicates a software problem in the cluster.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_CONTROLLER_CONFIG_INVALID) Incorrect controller configuration [chars]

Explanation Incorrect disk controller configuration.

Recommended Action 1. Using service documentation for the disk controller, check that the correct configuration is set up for the disk controller. See also the IBM Total Storage SAN Volume Controller for Cisco MDS 9000: Configuration Guide. 2. Mark the error you have just repaired as fixed. 3. Start a cluster discovery operation.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_DEVICE_PORT_LOGIN_LOSS) Number of controller logins reduced [chars]

Explanation The number of controller logins has been reduced. One possible cause is that the user intentionally reconfigured the system.

Recommended Action 1. Check whether the controller has regained connectivity. If it has not, check the cable connection to the remote-device port. 2. If all logins to a remote-device port have failed and you cannot solve the problem by changing cables, check the condition of the remote-device port and the condition of the remote device. 3. Start a cluster discovery operation. 4. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_DEVICE_RESOURCE_RAN_OUT) Too many controllers were presented to the cluster [chars]

Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.

Recommended Action 1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERP) Error Recovery Procedure occurred [chars]

Explanation A managed disk error recovery procedure (ERP) has occurred. This error has been reported because a large number of disk error recovery procedures have been performed by the disk controller. The problem is probably caused by a failure of some other component on the SAN.

Recommended Action 1. View the error log entry and determine the managed disk that was being accessed when the problem was detected. (Note that the sense data from the disk controller is recorded in the cluster error log and can be accessed there. This data is not available in the switch system log.) 2. Perform the disk controller problem determination and repair procedures for the mdisk determined in step 1. 3. Perform fibre channel switch problem determination and repair procedures for the fibre channel switches containing the node, and connected to the disk controller that is managing the mdisk, and any fibre channel switches in the fibre channel path between those switches. 4. If any problems are found and resolved in steps 2 and 3, mark this error as fixed. 5. If no switch or disk controller failures were found in steps 2 and 3, take an error log dump. Call your hardware support center.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERROR) Managed Disk I/O error [chars]

Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.

Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, included the managed disks and then mark the error as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD) Managed Disk error count threshold exceeded [chars]

Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.

Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, included the managed disks and then mark the error as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_TIMEOUT_OVERALL) Timeout due to excessive processing time [chars]

Explanation A managed disk has timed out. This error has been reported because a large number of disk timeout conditions have been detected. The problem is probably caused by a failure of some other component on the SAN.

Recommended Action 1. Repair problems on all disk controllers and switches on the same SAN as this cluster. 2. If problems are found, mark this error as fixed. 3. If no switch or disk controller failures can be found, take an error log dump and call your hardware support center.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LOCAL_PORT_EXCLUDED) Local FC port excluded [chars]

Explanation A local fibre-channel port has been excluded.

Recommended Action 1. Repair the fibre-channel network fabric. 2. Check the status of the disk controller. If all disk controllers 3. show good status, mark the error you have just repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LOGIN_EXCLUDED) Login excluded [chars]

Explanation Login has been excluded.

Recommended Action 1. In the sequence shown, exchange the FRUs for new FRUs: Fibre Channel cable, switch to remote port. 2. Start a cluster discovery operation to recover the login. 3. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LUN_RESOURCE_RAN_OUT) Too many LUNs were presented to a node [chars]

Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.

Recommended Action 1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_ACCESS_INVALID) Access beyond end of disk, or Managed Disk missing [chars]

Explanation The error that is logged in the cluster error log indicates a software problem either in the cluster, or in a disk enclosure or disk controller that is connected to the node.

Recommended Action 1. Ensure that the software is at the latest level on the cluster and on the disk controllers. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_DEVICE_PORT_EXCLUDED) Remote Port excluded for a specific Managed Disk and Node [chars]

Explanation A remote fibre-channel port has been excluded.

Recommended Action 1. View the error log. Note the Mdisk ID associated with the error code. 2. Using the Mdisk ID, determine the failing disk controller. 3. Refer to the service documentation for the disk enclosure or disk controller and the fibre-channel network fabric to resolve the reported problem. 4. Start a cluster discovery operation to recover the excluded fibre-channel port. 5. Include the managed disk that you noted in step 1. 6. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 7. If all disk controllers do not show a good status, contact the IBM support center to resolve the problem with the disk controller.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_EXCLUDED) Managed Disk excluded due to excessive errors, or all device ports excluded [chars]

Explanation A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.

Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If all managed disks show a status of excluded, included the managed disks and then mark the error as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_INITIALISE_INVALID) Invalid blocksize, capacity or LUN identity has changed during Managed Disk initialisation [chars]

Explanation Access beyond end of disk. The initialization of the managed disk has failed.

Recommended Action 1. Check the status of the managed disk and of the managed-disk group. 2. Include the managed disk into the cluster. 3. Check the managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed. 4. If not all managed disks show a status of online, check the status of the disk controller.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_RESOURCE_RAN_OUT) Too many Managed Disks were presented to the cluster [chars]

Explanation The configuration is not valid. Too many devices have been presented to the cluster or node.

Recommended Action 1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_CREATION_FAILURE) A suitable Managed Disk for use as a Quorum Disk was not found [chars]

Explanation No Mdisk is suitable for use as a quorum disk. When a cluster is created three disks are automatically selected as quorum disks. A quorum disk is needed to enable a tie-break when some cluster members are missing. To become a quorum disk: The Mdisk must be accessible by all nodes in the cluster and the Mdisk must have free extents. This error code is produced when at least one quorum disk is not accessible by all nodes in the cluster. A quorum disk might not be available because of a fibre-channel network failure or because of a fibre-channel switch zoning problem.

Recommended Action 1. Resolve any known fibre-channel network problems. 2. Ask the customer to confirm that Mdisks have been created and that those Mdisks have free extents. 3. List the manage disks. If at least one managed disk shows a mode of managed, mark the error you have just repaired as fixed. 4. If the customer is unable to make the appropriate changes, ask IBM Software Support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_NOT_AVAILABLE) Quorum Disk not available [chars]

Explanation One or more quorum disks were not discovered by the node.

Recommended Action 1. Resolve any known fibre-channel network problems. 2. Check managed disk status. If any managed disks are offline or excluded perform the disk controller problem determination and repair procedures for the managed disks. 3. Start a cluster discovery operation. 4. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ALL_SSH_KEYS_REMOVED) Attempt to delete SSH keys (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEPARTNERSHIP) Remote Copy partnership created [chars]

Explanation 'svc task mk partnership' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEPARTNERSHIP) Remote Copy partnership deleted [chars]

Explanation svc task mk partnership' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYPARTNERSHIP) Remote Copy partnership modified [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_ADDED) Attempt to add SSH key (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_REMOVED) Attempt to delete SSH key (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_CR_START) Cluster recovery required [chars]

Explanation The node has detected that cluster recovery is required and is waiting for human intervention to continue.

Recommended Action Contact IBM Product support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_CORRUPT) Node data corrupted - node rejected from cluster [chars]

Explanation Node data is readable but corrupted. The node has been rejected from the cluster.

Recommended Action 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_UNREADABLE) Node data unreadable - node rejected from cluster [chars]

Explanation Node data could not be read. The node has been rejected from the from cluster.

Recommended Action 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_HDW_CONFIG) Processor not valid [chars]

Explanation The node has detected unexpected differences in the processor vital data.

Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MEM_SIZE) Memory size error [chars]

Explanation The detected memory size does not match the expected memory size for the cluster.

Recommended Action A memory module on the Cisco MDS 9000 Caching Services Module is probably faulty. Reload the node. If the error persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MISSING_RES) Unable to form a cluster due to lack of cluster resources [chars]

Explanation The node is unable to locate sufficient other nodes in the cluster and/or the quorum disk controller needed in order to form a cluster.

Recommended Action Check the status of the quorum disk controller and the other nodes in the cluster. If the quorum disk has failed, perform the problem determination procedures for the disk controller. Otherwise perform problem determination on the missing nodes and network.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_NO_FABRIC) The node is unable to see the FC fabric [chars]

Explanation No active/functioning logical FC port was detected by the software.

Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_PWR_DMN_ERR) Power domain error [chars]

Explanation The two nodes in an IO group are on the same Caching Services Module.

Recommended Action Determine if both nodes on the Caching Services Module are in fact in the same IO group. If so, determine what the configuration should be. Remove one of the nodes and add a node to the IO group which is not on the same Caching Services Module. If not, ask IBM Product Support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_REPEATED_ASSERTS) Node repeatedly crashing due to a software fault [chars]

Explanation The number of software faults has exceeded the maximum allowed for the time period.

Recommended Action 1. Delete the node from the cluster. 2. Try to add the node back into the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance.

Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_RESET_AND_REJECT) Node data not found - node rejected from cluster [chars]

Explanation Node data was not found. The node has been rejected from the from cluster.

Recommended Action Examine error logs to determine if another recorded error caused the loss of the node data and, if so, follow the actions for that error. If no other error was recorded, the node may have lost power without saving data or been reset. Attempt to determine the cause of the power loss or reset. If no cause can be determined, then: 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.

Message SVC-3-SVC_SYSLOG_IF_INTERNAL_ERROR: Interface [chars] internal error: [chars]

Explanation SVC interface internal error

Recommended Action No action is required.

Message SVC-3-SVC_SYSLOG_LC_INTERNAL_ERROR: Unable to send MTS to linecard in slot [dec]: [chars]

Explanation Linecard MTS failure

Recommended Action No action is required.

Message SVC-3-SVC_SYSLOG_NPORT_INTERNAL_ERROR: [chars] N-port for Interface [chars], vsan [dec] internal error: [chars]

Explanation N-port internal error

Recommended Action No action is required.

SVC-4

Message SVC-4-NODE_WARNING_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_FIRST_DATA_PINNED) Customer data pinned [chars]

Explanation There is now pinned customer data. This warning is given when data is pinned and there was not already pinned data. Error log entries will exist for the under lying cause of the pinned data.'

Recommended Action Perform problem determination on the error log to determine the cause of the pinned data and correct.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_SYNCHRONOUS) Cache in write through mode due to pinned data [chars]

Explanation The cache must now operate in write through mode because of the amount of pinned data.

Recommended Action Perform problem determination on the error log to determine the cause of the pinned data and correct.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_BELOW_CAPACITY) Battery is below threshold capacity [chars]

Explanation Battery capacity is below threshold. The node will remain offline until the battery charge is sufficient to come up.

Recommended Action Wait for the battery to recharge. This may take many hours. If after several hours have passed and the node has not yet come up: 1. Reload the node. 2. If the error persists, re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 3. If the error persists, replace the Caching Services Module.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_CANNOT_OPEN_IO_PROCESS_Q) Internal error - IO process queue [chars]

Explanation The process was unable to open the needed message queue. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DEACTIVATE_CLUSTER_IP_FAILED) Deactivate cluster IP failed [chars]

Explanation Unable to deactivate the cluster IP for the config node. The cluster IP should be deactivated by other checks. If that is not the case it may not be possible to execute configuration commands.

Recommended Action If there is a problem executing configuration commands: 1. Shutting the interfaces of the node will force this node out of the cluster and should cause the switch to deactivate the IP address associated with this node which should restore the ability to execute configuration commands. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DUMP_METADATA_FAILED) Node assert dump failed [chars]

Explanation A failure occurred writing out a node assert dump. Other log entries may accompany this error.

Recommended Action An initial error will have caused the node assert dump. Examine the log for that error and follow the recommended actions for that error. In addition examine the log for errors related to the internal disk drive. If found, follow the recommended actions. If no entries explain the failure to write the dump: 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_EXECVE_FAILED) Internal error - program launch [chars]

Explanation The process was unable to launch the IO program. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_FORK_FAILED) Internal error - fork failed [chars]

Explanation The process was unable to launch the IO program. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_EXIT_LOGIC_ERR) Internal error - bad exit code [chars]

Explanation Node was warmstarted due to internal logic error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_UNKNOWN_EXEC_MODE) Internal error - run mode [chars]

Explanation Node was rebooted due to internal logic error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_EXITED_DUE_TO_SIGNAL) Internal error - signal caused exit [chars]

Explanation The IO process exited because of a signal which was not caught. Node was warmstarted due to this error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_STOPPED_DUE_TO_SIGNAL) Internal error - signal caused stop [chars]

Explanation The IO process stopped because of a signal received. Node was warmstarted due to this error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_IOP_TERMINATED_ABNORMALLY) Internal error - abnormal exit [chars]

Explanation The IO process exited abnormally. Node was warmstarted due to this error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_OPEN_MSG_QUEUE_FAILED) Internal error - message queue [chars]

Explanation The process was unable to open the needed message queue. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_PTHREAD_CREATE_FAILED) Internal error - threads [chars]

Explanation The process was unable to create the needed threads. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_UNKNOWN_MESSAGE_TYPE) Internal error - message type [chars]

Explanation Node was rebooted due to internal logic error.

Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_WAITPID_FAILED) Internal error - waitpid failed [chars]

Explanation The process was unable to launch the IO program properly. Node was warmstarted due to this error.

Recommended Action If this error is repeated continuously, 1. Reload the node. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_WARMSTART_MEMORY_FAILED) Internal error - warmstart memory device [chars]

Explanation The process was unable to warmstart the memory device. Node was rebooted due to this error.

Recommended Action If this error is repeated continuously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_MAPPING_STOPPED) FlashCopy has been stopped [chars]

Explanation A Flash Copy mapping task has been stopped because of an error. A stopped flash copy may affect the status of other VDisks in the same I/O group. Preparing the stopped flash copies as soon as possible is advised.

Recommended Action 1. Correct higher priority errors. Then, ask the customer to prepare and start the Flash Copy task again. 2. Mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_FAILED) FlashCopy prepare failed due to cache flush failure [chars]

Explanation A Flash Copy prepare task has failed because a cache flush has failed.

Recommended Action 1. Correct higher priority errors, then retry the prepare tasks. 2. Mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_STOP_COMPLETED) Flash Copy Stopped [chars]

Explanation The Flash Copy mapping or consistency group has entered the STOPPED state as a result of a user request to stop.

Recommended Action None

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_DIRECTORY_LIST_FAILED) Failed to obtain directory listing from remote node [chars]

Explanation An attempt to clean or retrieve files from /dumps directory has failed because of a failure to get listing of the directory from the remote node.

Recommended Action Determine if the remote node is still online. If not, perform problem determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support Center for assistance. Cisco CLI commands may be used to access the node directly as an alternative.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_FEATURISATION_VIOLATION) Featurisation violation [chars]

Explanation The user has allocated more visualized storage than licensed for or established a Flash Copy mapping or Remote Copy relationship when these have not been licensed.

Recommended Action Look in the featurisation log for log entries of type Error to determine the type of violation. The user then should the neither reduce visualized storage, remove the Flash Copy mapping or Remote Copy relationship, so as to be in compliance with their license; or update the license information if that is incorrect; or arrange with their IBM representative to purchase a license for the desired features.'

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_ER_TRANSFER_FILE_FAILED) Failed to transfer file from remote node [chars]

Explanation An attempt to retrieve a file from /dumps directory has failed.

Recommended Action Determine if the remote node is still online. If not, perform problem determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support Center for assistance. Cisco CLI commands may be used to access the node directly as an alternative.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_NONE_OK) Both nodes in the IO group are not available [chars]

Explanation Following node remove by the user, there are no nodes left in the IO group.

Recommended Action None

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_NODE_PENDED) Software upgrade process failed [chars]

Explanation A software upgrade has failed. This might be because of a hardware error or it might be because of a failure in the new version of the software. An automatic software downgrade is performed to restore the nodes to their previous software version. This will be indicated in the log by a Software down grade complete' entry. If the down grade operation fails to down grade a node, for example because it is offline, the down load operation will stop and wait for the offline SAN Volume Controller to be repaired or deleted from the cluster. While the down grade operation is in progress, configuration commands sent to the cluster will fail with a message indicating that a software upgrade operation is still in progress. The downgrade operation might take up to three hours.

Recommended Action 1. Display the status of the nodes on the cluster. 2. If any node is offline, delete the offline node from the cluster. If the delete fails with a message indicating that a software upgrade is in progress, this means that the downgrade process is still active. Wait for this operation to either complete or stop on the offline node and then retry the delete. If the downgrade operation had stopped, it will now continue. 3. Solve all logged hardware problems 4. Ask the user to retry the software install. 5. If the installation fails again, report the problem to your software support center. 6. Mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_PCK_DELIVERY_FAILED) Software install package cannot be delivered to all nodes [chars]

Explanation An error occurred while sending the software package to the nodes.

Recommended Action 1. Display the status of the nodes on the cluster. 2. If any node is offline, perform problem determination on the node and bring the node back online. Or, alternatively, delete the offline node from the cluster. 3. Retry the software retry the delete. If the downgrade operation had stopped, it will now continue. 3. Solve upgrade command. 4. If the installation fails again, report the problem to your software support center.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_PLIC_LINK) Connection to a configured remote cluster has been lost [chars]

Explanation This cluster is no longer able to communicate with the remote copy partner cluster.

Recommended Action Perform problem determination on the network and the other cluster.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_LSYNC) Remote Copy suffered loss of synchronization [chars]

Explanation In a remote-copy operation, the relationship has stopped and lost synchronization, for a reason other than a continuous I/O error.

Recommended Action 1. Correct higher priority errors, then restart the remote copy. 2. Mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_PERS) Remote Copy suffered persistent error [chars]

Explanation A Remote Copy relationship has been stopped because of a continuous I/O error.

Recommended Action 1. Correct the higher priority errors, then retry the Remote Copy task. 2. Mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_TIMEOUT) Remote Copy retry timeout [chars]

Explanation Remote Copy was unable to find a path to the device in the remote cluster within the timeout period.

Recommended Action Perform problem determination on the network and remote cluster: Ensure that all nodes in both clusters are configured in the inter-cluster SAN or VSAN. Ensure that all virtual disks in the remote cluster are online.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_COPIED_MEDIUM_ERROR) I/O media error copied [chars]

Explanation During a copy or a migrate process a media error was copied to the destination disk.

Recommended Action None

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_INSUFFICIENT_VIRTUAL_EXTENTS) Insufficient extents to create Virtual Disk [chars]

Explanation There are not enough extents contained within the managed disk group to create the required virtual disk. This error can be logged if a migration is started and then a virtual disk is created which uses the extents that were to be used for the migration.

Recommended Action Add additional managed disks to the managed disk group or reduce the size of virtual disk to be created.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_STOPPED) Migration stopped [chars]

Explanation The specific migration has been stopped due to errors occurring during migration, these errors have been logged.

Recommended Action Analyze the error log. Perform problem determination and correct any errors which have occurred. Migrate any specific extents which were not migrated due to the errors.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_SUSPENDED) Migration suspended [chars]

Explanation Migration suspended.

Recommended Action 1. Ensure that all error codes of a higher priority have already been fixed. 2. Ask the customer to ensure that all Mdisk groups that are the destination of suspended migrate operations have free extents available. 3. Mark this error as fixed. This will cause the migrate operation to be restarted. If the restart fails a new error will be logged.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_MEDIUM_ERROR) A media error has occurred during I/O to a Managed Disk [chars]

Explanation A disk I/O medium error has occurred.

Recommended Action 1. Ask the customer to rewrite the bad data to the block LBA reported in the host systems SCSI sense data. Note: If this error has occurred during a migration, the host system will notice the error until the target device is accessed. 2. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD_WARNING) Managed Disk error count warning threshold met [chars]

Explanation IOs to the managed disk have experienced sufficient errors to generate this warning. If the managed disk continues to experience IO errors, the managed disk may be excluded.

Recommended Action Perform problem determination on the affected managed disk.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LUN_DISCOVERY_FAILED) Discovery of LUN failed [chars]

Explanation The cluster has a connection to the device on the SAN through this node, but the device has not responded to the node in a manner consistent with a functional device LUN.

Recommended Action If there are device LUNs that should have been discovered by the node: 1) Perform a manual discovery. 2) Perform problem determination on the device.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_PORT_PREFERENCE_IGNORED) Preferred port is not being used for Managed Disk access [chars]

Explanation The preferred port designated by the back end controller is not being used for Managed Disk access. A port error or excluded port has prevented the use of the preferred port.

Recommended Action Perform problem determination on the controller and network to determine the cause of the port error or exclusion.

Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_NODERR_CR_FAILED) Cluster recovery failed [chars]

Explanation Cluster recovery has failed and a software dump has been created.

Recommended Action Contact IBM Product support for assistance.

Message SVC-4-SVC_SYSLOG_IF_INTERNAL_WARN: Interface [chars] internal warning: [chars]

Explanation SVC interface internal warning

Recommended Action No action is required.

Message SVC-4-SVC_SYSLOG_NPORT_INTERNAL_WARN: [chars] N-port for Interface [chars], vsan [dec] internal warning: [chars]

Explanation SVC interface internal warning

Recommended Action No action is required.

SVC-5

Message SVC-5-NODE_NOTICE_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

Message SVC-5-SVC_SYSLOG_IF_CONFIG_DELETED: Interface [chars] configuration was deleted[chars]

Explanation SVC interface configuration was deleted

Recommended Action No action is required.

Message SVC-5-SVC_SYSLOG_IF_DOWN: Interface [chars] is down

Explanation SVC interface is down

Recommended Action No action is required.

Message SVC-5-SVC_SYSLOG_IF_UP: Interface [chars] is up

Explanation SVC interface is up

Recommended Action No action is required.

SVC-6

Message SVC-6-NODE_INFO_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_ALL_DATA_UNPINNED) All data now unpinned [chars]

Explanation All the customer data in the IO group is now unpinned.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_ASYNCHRONOUS) Pinned data reduced; cache can operate normally [chars]

Explanation Enough customer data has been unpinned that the cache is no longer required to operate in write through mode because of the pinned data. (Note that the cache may still operate in write through mode for other reasons.)

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_OK) Battery recharged [chars]

Explanation Battery capacity has been restored to above threshold. The node will now come online.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_POWER_DOWN) Poweroff or power failure detected [chars]

Explanation The process has received a Poweroff or power failure indication. The node is shutting down.

Recommended Action Restore power. If power was not removed and this occurs: 1. Reload the node. 2. If the error persists, re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 3. If the error persists, replace the Caching Services Module.

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_PWR_BUTTON) Power withdrawn [chars]

Explanation Node software was notified that AC power was being shut off or the Caching Services Module was being reset.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_COPY_COMPLETED) Flash Copy Copied [chars]

Explanation The Flash Copy mapping or consistency group has entered the IDLE_COPIED state. The target disk now contains a complete copy and is no longer dependent on the source.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_COMPLETED) Flash Copy Prepared [chars]

Explanation The Flash Copy mapping or consistency group has entered the PREPARED state. It is now possible to Start or Stop the mapping/group.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_CLUSTER_RECOVERY_COMPLETE) Cluster recovery completed [chars]

Explanation Cluster recovery has completed successfully.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_ONE_OK) One node in the IO group is not available [chars]

Explanation Following node remove by the user, there is only one node left in the IO group.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_SECURE_DELETE_COMPLETE) Virtual Disk format completed [chars]

Explanation The formatting (writing all zeros) to new extents of the Virtual Disk has completed.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_COLDSTART) Node software started [chars]

Explanation The node software has been started (cold start).

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_COPY_COMP) Remote Copy complete [chars]

Explanation Background copy complete. The standalone relationship or consistency group has transitioned from Inconsistent Copying 'to' Consistent Synchronized'. This will only be logged on the cluster of the Primary Virtual Disk(s).'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_READY_TO_START) Remote Copy ready to start [chars]

Explanation The remote copy relationship or consistency group, which had been previously been stopped due to an error, is ready to be restarted. All resources are now online.

Recommended Action Restart the relationship or consistency group.

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VG_EV_MIGRATE_COMPLETE) Migration complete [chars]

Explanation Migration has completed.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_CLUSTER_FABRIC_VIEW_CHANGE) Cluster fabric view has been updated. [chars]

Explanation The node is in the process of discovering devices on the fabric.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_MAPPING) Virtual Disk to Host SCSI mapping created [chars]

Explanation svc task MKY disk host map or equivalent GUI/ Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_WWPN) Port added to a Host [chars]

Explanation svc task add host port or equivalent GUI/Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_CLUSTER_TIME) Attempt to change cluster time (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_TIMEZONE) Attempt to change time zone (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DISCOVERY) Manual Managed Disk discovery invoked [chars]

Explanation 'SVC task detect Mdisk' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DUMP_CONFIG) Cluster config dumped to file [chars]

Explanation 'svc task dump config' or equivalent GUI / Cisco CLI command has been invoked'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_MODIFY) Cluster attributes modified [chars]

Explanation 'svc task chcluster' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_SHUTDOWN) Node or Cluster shutdown [chars]

Explanation 'svc task stop cluster' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_FC_MAPPING) Flash Copy mapping created [chars]

Explanation 'svc task mk fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_HOST) Host created [chars]

Explanation 'svc task mk fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_FC_MAPPING) Flash Copy mapping deleted [chars]

Explanation 'svc task mk fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_HOST) Hosts deleted [chars]

Explanation 'svc task rm host' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_MAPPING) Virtual Disk to Host SCSI mapping deleted [chars]

Explanation 'svc task rm vdisk host map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_PORT_HOST_LIST) Ports deleted from a Host [chars]

Explanation 'svc task rm host port' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_WWPN) Port deleted from a Host [chars]

Explanation 'svc task rm host port' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DEVICE_SET_NAME) Controller attributes modified [chars]

Explanation 'svc task ch controller' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_ANALYSE) Error log analyzed [chars]

Explanation 'svc task find err' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_CLEARLOG) Error log cleared [chars]

Explanation 'svc task clear err log' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_DUMPLOG) Error log dumped [chars]

Explanation 'svc task dump err log' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_FIX) Error log entry marked fixed [chars]

Explanation 'svc task ch err state' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CONSIST_GRP_SET_NAME) Flash Copy consistency group name modified [chars]

Explanation 'svc task ch fc consist grp-name' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CREATE_CONSIST_GRP) Flash Copy consistency group created [chars]

Explanation 'svc task mk fc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_DELETE_CONSIST_GRP) Flash Copy consistency group deleted [chars]

Explanation 'svc task rm consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_SET_NAME) Flash Copy mapping name modified [chars]

Explanation 'svc task ch fc map-name' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FEATURISATION_CHANGED) Licensed settings modified [chars]

Explanation 'svc task ch license' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_PREPARE_CG) Flash Copy consistency group prepared [chars]

Explanation 'svc task per start fc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_START_CG) Flash Copy consistency group started [chars]

Explanation 'svc task start fc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_STOP_CG) Flash Copy consistency group stopped [chars]

Explanation 'svc task stop fc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_DELETE) Host deleted [chars]

Explanation 'svc task rm host' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_SET_NAME) Host attributes modified [chars]

Explanation 'svc task ch host' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HWS_SET_NAME) IO Group name modified [chars]

Explanation 'svc task ch iogrp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_IO_TRACE_FINISHED) IO Tracing stopped [chars]

Explanation 'svc task stop trace' or equivalent GUI / Cisco CLI command has been invoked, or the trigger occurred for a given Managed Disk, automatically stopping the trace.

Recommended Action Analyses the traces.

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_ADD_MDISK) Managed Disk added to Managed Disk group [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_CREATE) Managed Disk Group created [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE) Managed Disk Group deleted [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE_MDISK) Managed Disk deleted from Managed Disk group [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_SET_NAME) Managed Disk Group attributes modified [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_SET_NAME) Managed Disk attributes modified [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_UNSLANDER) Managed Disk online [chars]

Explanation The managed disk which was excluded is now online.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MIGRATE) Virtual Disk migration to new Managed Disk group started [chars]

Explanation svc task add Mdisk or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MODIFY_FC_MAPPING) Flash Copy mapping modified [chars]

Explanation 'svc task ch fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_ADD) Node added [chars]

Explanation 'svc task add node' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_CREATE_CLUSTER) Cluster created [chars]

Explanation 'cluster add' or equivalent GUI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_DELETE) Node deleted from cluster [chars]

Explanation 'svc task rm node' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_PEND) Node Pend [chars]

Explanation The node has gone into the pending state. It will shortly go into the online or offline state.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_REMOVE) Node leaving cluster (expected) [chars]

Explanation The node has gone offline as expected due to shutdown, upgrade or deletion.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SET_NAME) Node attributes modified [chars]

Explanation 'svc task ch node' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SHUTDOWN) Node shutdown [chars]

Explanation 'svc task stop cluster-node' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_UNPEND) Node Unpend [chars]

Explanation The node has gone online.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PLANAR_SN_CHANGE) Attempt to change the Planar Serial Number (no effect) [chars]

Explanation 'svc task rm all ssh keys' command has been invoked. This command has no effect in SAN Volume Controller for Cisco MDS9000, but is retained for compatibility.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PRETRIGGER_FC_MAPPING) Flash Copy mapping prepared [chars]

Explanation 'svc task pre start fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_QUORUM_CREATE) Quorum disk set [chars]

Explanation svc task set quorum' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATECONSTGRP) Remote Copy consistency group created [chars]

Explanation 'svc task mk rc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEREL) Remote Copy relationship created [chars]

Explanation 'svc task mk rc relationship' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETECONSTGRP) Remote Copy consistency group deleted [chars]

Explanation 'svc task rm consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEREL) Remote Copy relationship deleted [chars]

Explanation 'svc task rm rc relationship' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYCONSTGRP) Remote Copy consistency group modified [chars]

Explanation 'svc task ch rc consist grp' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYREL) Remote Copy relationship modified [chars]

Explanation 'svc task ch rc relationship' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START) Remote Copy relationship started [chars]

Explanation 'svc task start rc relationship' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START_CG) Remote Copy consistency group started [chars]

Explanation 'svc task start rc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP) Remote Copy relationship stopped [chars]

Explanation 'svc task stop rc relationship' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP_CG) Remote Copy consistency group stopped [chars]

Explanation 'svc task stop rc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH) Remote Copy relationship switched [chars]

Explanation 'svc task switch rc relationship' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH_CG) Remote Copy consistency group switched [chars]

Explanation 'svc task switch rc consist grp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SERVICE_APPLY_SOFTWARE) Software upgrade command accepted [chars]

Explanation cluster upgrade svc-system' or equivalent GUI command has been invoked. The command has been accepted. Additional log entries will track the progress of the upgrade.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_STOP_FC_MAPPING) Flash Copy mapping stopped [chars]

Explanation 'svc task stop fc map' or equivalent GUI / Cisco CLI command has been invoked.'

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_TRIGGER_FC_MAPPING) Flash Copy mapping started [chars]

Explanation 'svc task start fc map' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_BACKED_OFF) Software downgrade complete [chars]

Explanation The software upgrade process failed and all nodes have been restored to the previous level of code.

Recommended Action Perform problem determination on the cause of the upgrade failure and take corrective action before retrying the upgrade.

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_COMPLETED) Software upgrade complete [chars]

Explanation All nodes have successfully moved to the new code level, which will now be committed.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_STARTED) Software upgrade started [chars]

Explanation The software upgrade process has started (the first node is about to be upgraded).

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_CREATE) Virtual Disk created [chars]

Explanation 'svc task mk vdisk' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_DELETE) Virtual Disk deleted [chars]

Explanation 'svc task rm vdisk' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND) Virtual Disk expanded [chars]

Explanation 'svc task expand vdisk size' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND_SINGLE_EXT) Virtual Disk expanded by single extent [chars]

Explanation 'svc task add vdisk ext' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENT) Extent migration started [chars]

Explanation 'svc task migrate exts' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENTS) Extent migration started [chars]

Explanation 'svc task migrate exts' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MODIFY_GOVERN) Virtual Disk throttling rate modified [chars]

Explanation 'svc task ch vdisk-rate' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MOVE_HWS) Virtual Disk IO Group changed [chars]

Explanation 'svc task ch vdisk-iogrp' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SET_NAME) Virtual Disk name modified [chars]

Explanation 'svc task ch vdisk-name' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SHRINK) Virtual Disk shrunk [chars]

Explanation 'svc task shrink vdisk size' or equivalent GUI / Cisco CLI command has been invoked.

Recommended Action None

Message SVC-6-SVC_SYSLOG_CL_CONFIG: Node [chars] has become config node of cluster [chars]

Explanation SVC interface has because cluster config node

Recommended Action No action is required.

Message SVC-6-SVC_SYSLOG_CL_JOIN: Node [chars] has joined cluster [chars]

Explanation SVC interface has joined cluster

Recommended Action No action is required.

Message SVC-6-SVC_SYSLOG_CL_UNJOIN: Node [chars] has left cluster [chars]

Explanation SVC interface has left cluster

Recommended Action No action is required.

Message SVC-6-SVC_SYSLOG_LC_WWN_PURGE: All WWNs for module [dec] have been purged[chars]

Explanation SVC linecard has purged all WWNs

Recommended Action No action is required.

Message SVC-6-SVC_SYSLOG_VSAN_INACTIVE: Vsan [dec] suspended

Explanation Vsan was suspended; can cause warnings

Recommended Action No action is required.

SVC-7

Message SVC-7-NODE_DEBUG_MSG: [chars]

Explanation Syslog message from a SVC interface node

Recommended Action No action is required.

SWITCH Messages

This section contains the SWITCH messages.

SWITCH_ZONEMEMBER_FAN_OUT_RATIO_LIMIT

Message SCRIPT-INFO: ZONE-2-SWITCH_ZONE_MEMBER_RATIO: VSAN-[dec]: Zoneset [char] has [dec] devices that exceed the zone member ratio of 1:[dec].

Explanation Configured limit for the Zone member fan-out ratio exceeded : [chars].

Recommended Action Reconfigure the zoneset with smaller fan-out for the affected end devices so they avoid degraded performance.

SYSMGR Messages

This section contains the SYSMGR messages.

SYSMGR-2

Message SYSMGR-2-ACTIVE_LOWER_MEM_THAN_STANDBY: Active supervisor in slot [dec] is running with less memory than standby supervisor in slot [dec].

Explanation Supervisor memory mismatch

Recommended Action No action is required.

Message SYSMGR-2-BOOTSCOPE_HANDSHAKE: Service [chars] is in the boot scope, but tried a regular handshake. Discarding request.

Explanation A service is trying to take actions that belong to a different class of services.

Recommended Action 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.

Message SYSMGR-2-CFGERASE_ABORTED: Write erase aborted.

Explanation Write erase has failed.

Recommended Action Please verify the other syslog messages printed correct the problem, and try again.

Message SYSMGR-2-CFGSNAPSHOT_ABORTED_DIR: Unable to open the configuration directory. Aborting configuration snapshot.

Explanation The destination location for the snapshot-config could not be found.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGSNAPSHOT_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration snapshot.

Explanation An attempt to copy the startup-config to snapshot-config has failed because the old data could not be removed.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGSNAPSHOT_ABORTED: Configuration snapshot aborted.

Explanation An attempt to save a snapshot of the startup-config has failed.

Recommended Action Please verify the other syslog messages printed correct the problem, and try again.

Message SYSMGR-2-CFGSYNC_FAILURE: Syncing of the configuration to the standby failed.

Explanation Syncing of the configuration to the standby failed.

Recommended Action Please verify the other syslog messages printed correct the problem, and try again.

Message SYSMGR-2-CFGWRITE_ABORTED_DIR: Unable to open the configuration directory. Aborting configuration copy.

Explanation The destination location for the startup-config could not be found.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGWRITE_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration copy.

Explanation An attempt to copy the running-config to startup-config has failed because the old data could not be removed.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGWRITE_ABORTED_LABEL: Unable to label the new configuration (error-id [hex]). Aborting configuration copy.

Explanation An attempt to copy the running-config to startup-config has failed because the new startup-config could not be stamped.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGWRITE_ABORTED_LOCK: Unable to lock the configuration (error-id [hex]). Aborting configuration copy.

Explanation An attempt to copy the running-config to startup-config has failed because the system could not lock the required configuration items.

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.

Message SYSMGR-2-CFGWRITE_ABORTED_LOG: Unable to open a log file for the new configuration: [chars] (error-id [hex]). Aborting configuration copy.

Explanation An attempt to copy the running-config to startup-config has failed because a log file could not be created.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.

Explanation A configuration copy has failed.

Recommended Action Please verify the other syslog messages printed correct the problem, and try again.

Message SYSMGR-2-CFGWRITE_TIMEOUT_ABORT: Configuration copy aborted by timeout.

Explanation A service failed to store its configuration in the timeout period. The operation has been aborted.

Recommended Action No action is required.

Message SYSMGR-2-CFGWRITE_USER_ABORT: Configuration copy aborted by the user.

Explanation The user typed CTRL+C while the configuration was being saved, and the operation has been aborted.

Recommended Action No action is required.

Message SYSMGR-2-CONVERT_FUNC_FAILED: Conversion function failed for service “[chars]” (error-id [hex]).

Explanation This message indicates that the conversion function failed for this service.

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.

Message SYSMGR-2-CONVERT_FUNC_NOTFOUND: Conversion function not found for service “[chars]”.

Explanation This message indicates that the system could not find appropriate conversion function for this service.

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.

Message SYSMGR-2-CONVERT_LIB_NOTFOUND: Conversion library not found for service “[chars]”.

Explanation This message indicates that the system could not find conversion library for this service.

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.

Message SYSMGR-2-CONVERT_STARTUP_ABORTED: Conversion of startup-config failed.

Explanation This message indicates that the conversion of startup configuration was aborted.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-CONVERT_ZIPPING_FAILED: Failed to zip the converted startup configuration.

Explanation This message indicates that conversion of the startup configuration failed when system was trying to zip the converted configuration.

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.

Message SYSMGR-2-CORE_SAVE_FAILED: [chars]: PID [dec] with message [chars].

Explanation

Recommended Action No action is required.

Message SYSMGR-2-CREATE_DONEFILE_FAILED: Creating /var/run/sysmgr.initdone failed with return value: ([dec]).

Explanation The initialization of the system could not complete.

Recommended Action 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.

Message SYSMGR-2-DELETE_BINARY_STARTUP_FAILED: Deletion of binary startup config failed during boot (error-id [hex]).

Explanation This message indicates that the deletion of the binary startup configuration failed during boot.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-FEATURE_SET_NOT_DISABLED_SRVS: vdc [dec]: feature-set 0x%llx: Following services did not cleanup: [chars]

Explanation

Recommended Action No action is required.

Message SYSMGR-2-FEATURE_SET_SRVTIMEOUT: vdc [dec]: feature-set 0x%llx [chars]: Following services did not respond in time: [chars]

Explanation The services did not handshake with sysmgr in time

Recommended Action No action is required.

Message SYSMGR-2-FEATURE_SET_UNGRACEFUL_DISABLE_FAILED_SRVS: vdc [dec]: feature-set 0x%llx: Following services did not exit even after SIGKILL: [chars]

Explanation

Recommended Action No action is required.

Message SYSMGR-2-FORMAT_FAILURE_SUP_RESET: Failure to format a partition successfully causing sup to reset.

Explanation The partition used to store non-volatile pss files could not be formatted successfully. The supervisor will be reset.

Recommended Action If the problem persists, please contact customer support.

Message SYSMGR-2-GSYNC_ABORT: Global sync aborted by signal.

Explanation The initial synchronization of the services has been aborted. The synchronization will be attempted again later.

Recommended Action Use the command reload module <mod>

Message SYSMGR-2-GSYNC_GET_TIMEOUT: Request for global sync for UUID [hex] not completed in specified time.

Explanation Service failed to complete global sync in specified time. The standby will no longer act as a HA standby.

Recommended Action If the problem persists, please contact customer support.

Message SYSMGR-2-GSYNC_READY_SRVFAILED: Service “[chars]” on standby supervisor failed to restore its snapshot (error-id [hex]).

Explanation The initial synchronization of service [chars] has failed.

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.

Message SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service “[chars]” on active supervisor failed to store its snapshot (error-id [hex]).

Explanation The initial synchronization of service [chars] has failed.

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.

Message SYSMGR-2-HANDSHAKE_FAILED: Handshake with service “[chars]” in vdc [dec] failed since send failed: [chars] (error-id [hex]).

Explanation Handshake with a service failed since system manager could not send handshake response to it.

Recommended Action No action is required.

Message SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase).

Explanation A cold switchover has started (pre-start phase).

Recommended Action When the other supervisor is back online, use the command 'show system reset-reason' to know what caused the switch over.

Message SYSMGR-2-HASWITCHOVER_START: Supervisor [dec] is becoming active.

Explanation A cold switchover has started.

Recommended Action When the other supervisor is back online, use the command 'show system reset-reason' to know what caused the switch over.

Message SYSMGR-2-HEARTBEAT_FAILED: Sysmgr heartbeat failed at %lu. [chars]. [chars] ([dec])

Explanation System manager had failure while trying to heartbeat with KLM

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.

Message SYSMGR-2-INBAND_START_FAILED: Failure while bringing up inband after ISSU reboot, errno: [dec].

Explanation Sysmgr tried to bring up in band after ISSU reboot, but the call returned 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.

Message SYSMGR-2-INVALID_HANDSHAKE: Invalid secret ([dec]) received from service [chars]. Expected [dec].

Explanation A service cannot be started.

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.

Message SYSMGR-2-INVALID_SYSMGRCONF: [chars]: invalid configuration file “[chars]”: [chars] (error-id [hex]).

Explanation The system image contains an inconsistent list of services. The initialization of the system cannot proceed further.

Recommended Action 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.

Message SYSMGR-2-INVALID_VERSIONMSG: The remote System Manager ([chars]) declares itself in the same state as this System Manager ([chars]).

Explanation The redundancy state negotiation between the two supervisors failed.

Recommended Action 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.

Message SYSMGR-2-ISSU_FAILED: The ISSU has failed: [chars] (error-id [hex])

Explanation The ISSU has failed and the switch need to be rebooted.

Recommended Action No action is required.

Message SYSMGR-2-LAST_CORE_BASIC_TRACE: [chars]: PID [dec] with message [chars].

Explanation

Recommended Action No action is required.

Message SYSMGR-2-MSG_SEND_FAILURE_STANDBY_RESET: Failure in sending message to standby causing standby to reset.

Explanation We will be resetting the standby since mts on the active is unable to send a message to standby.

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.

Message SYSMGR-2-MTS_FLUSH_SYNC_QUEUE_FAILURE: flush mts sync queue failed with [chars] (errno [dec])

Explanation Calling mts_flush_sync_queue to guarantee no outstanding messages. the failure might affect HA

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.

Message SYSMGR-2-NON_VOLATILE_DB_FULL: System non-volatile storage usage is unexpectedly high at [dec]%.

Explanation System non-volatile storage space is almost full.

Recommended Action Please run the command clear processes log pid<pid>

Message SYSMGR-2-NON_VOLATILE_DB_INODE_FULL: System non-volatile inode storage usage is unexpectedly high at [dec]%.

Explanation System non-volatile inode storage space is almost full.

Recommended Action Please run the command clear processes log pid<pid

Message SYSMGR-2-ONBOARD_FAILURE_LOGGING_FULL: Onboard failure logging usage is unexpectedly high at [dec]%.

Explanation Onboard failure logging space is almost full.

Recommended Action Please run the command clear logging on board. If this message continues to persist, please contact TAC.

Message SYSMGR-2-PARSEERR_DEPENDCYCLE: Dependency cycle found among [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.'

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDCONFIG: [chars]: duplicated definition for service config. Previous definition in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDDEPEND: [chars]: duplicated dependency from [chars] for service [chars]. Previous use in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDNAME: [chars]: short name [chars] used by service [chars] is also used by service “[chars]” in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDOPTION: [chars]: duplicated definition for option [chars]-

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDSERVICE: [chars]: duplicated definition for service [chars]. Previous definition in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUPLICATEDVERDB: [chars]: duplicated definition for service version_db. Previous definition in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_DUP_UGRPENTRY: [chars]: service [chars] duplicated in the current upgrade group. Previous use in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_FT_SET_ID_PARSEERR: [chars]: client_id ([dec]) out of bound for “[chars]”.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INCONSISTENTOPT: [chars]: option “[chars]=[chars]” not consistent with “[chars]=[chars]” for service “[chars]”

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDCOMPCONDDEPEND: [chars] (in dependency list of compulsory conditional service [chars]): optional conditional service “[chars]” not allowed.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDCONDDEPEND: [chars] (in dependency list of ASAP service [chars]): conditional service “[chars]” not allowed.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDDEPEND: [chars] (in dependency list of service [chars]): service [chars] not defined for scope “[chars]”.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDEXEC: [chars]: invalid executable [chars] for service [chars]: [chars] ([dec]).

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDHANDSHAKEDEPEND: [chars] (in handshake dependency list of service [chars]): service “[chars]” is MTS unaware or not defined for scope “[chars]”.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDIDENT: [chars]: [chars] “[chars]” not found for service “[chars]”.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDOPTION: [chars]: option [chars]-

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDSTDBYDEPEND: [chars]: service [chars] cannot be dependent on service [chars] due to the standby mode wait for that service.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALIDVDCDEPEND: [chars] (in dependency list of service [chars]): service [chars] is a [chars] service.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.'

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.

Message SYSMGR-2-PARSEERR_INVALID_CLEANUP_ARGUMENTS: [chars]: cleanup_arguments = “[chars]”: only conditional services that are scripts can specify cleanup arguments

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_COND_SRV_MODE: [chars]: service [chars] not defined for scope “control” or not mts aware.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_DIR: [chars]: “[chars]” is not a valid [chars]: [chars] ([dec]).

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_GLOBAL_SYNC: [chars]: mts unaware service may not request for a global sync.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_HB: [chars]: “[dec]” is not a valid heartbeat timeout.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_MAX_INSTANCE: [chars]: [dec] is not a valid max_instance.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.'

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.

Message SYSMGR-2-PARSEERR_INVALID_SHELLTREE: [chars]: invalid shell parser tree [chars] for service [chars]: [chars] ([dec]).

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE_GLOBAL_SYNC: [chars]: service with standby mode wait cannot request for a global sync.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE: [chars]: standby_mode should be run.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_STARTUP_MODE_DEPENDENCY: [chars]: Invalid dependency. Service [chars] s startup mode ('[chars]') does not match dependent service “[chars]"'s startup mode ('[chars]').'

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

Recommended Action No action is required.

Message SYSMGR-2-PARSEERR_INVALID_TRANSL: [chars]: invalid translator [chars] for service [chars]: [chars] ([dec]).

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_INVALID_UGRPENTRY: [chars]: service "[chars]" is not defined.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_MISSINGOPTION: [chars]: option [chars]-

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND: [chars]: service [chars] is MTS unaware and cannot have handshake dependencies.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_NORESTART: [chars]: option [chars]-

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_NOTCONFIG: [chars]: [chars] implemented only for service config.

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_ADD_SRV: Service "[chars]" cannot be added

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_DELETE_SRV: Service "[chars]" cannot be removed

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_MODIFY_PARAM: Cannot modify parameter [chars] for the service "[chars]", old value = [chars], new value = [chars]

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_MODIFY_SRV: Configuration for service "[chars]" cannot be modified, param modified = [chars], old_value = [chars], new_value = [chars]

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_REP_UGRPENTRY: [chars]: service [chars] is used in more than one upgrade group. First use in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS_MULTIPLE_INST: [chars]: too many multiple instance dependencies ([dec]) for service "[chars]".

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS: [chars]: too many dependencies ([dec]) for service "[chars]".

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_UGRPDUPLICATEDNAME: [chars]: upgrade group name "[chars]" already used in [chars].

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARSEERR_UGRPNAMEREDEFINED: [chars]: the upgrade group is already called "[chars]".

Explanation The system image contains an inconsistent list of services. The initialization of the system can not proceed further.

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.

Message SYSMGR-2-PARTIAL_CFGWRITE_ABORTED: Partial configuration copy aborted.

Explanation A partial configuration copy has failed.

Recommended Action Please verify the other syslog messages printed correct the problem, and try again. If problem persists, please run the command copy running-config startup-config' and try again.'

Message SYSMGR-2-PLUGIN_BOOTUP_FAILURE: The bootup of the supervisor has failed due to plugin load: [chars] (error-id [hex])

Explanation The bootup of the supervisor has failed due to plugin load.

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.

Message SYSMGR-2-PSS2FILE_CONVERT_FAILED: Conversion of file [chars] failed.

Explanation Conversion of internal data format failed.

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.

Message SYSMGR-2-PSS2_VOLATILE_DB_FULL: Volatile database usage in kernel is unexpectedly high at [dec]%.

Explanation System volatile database in kernel space is almost full.

Recommended Action Please run the command ‘show system internal pss kernel mem stats'. If this message continues to persist, please contact TAC.'

Message SYSMGR-2-REDSTATE_GETFAILED: Failed to request redundancy state: [chars] (error-id [hex]).

Explanation The local supervisor is unable to get the redundancy state.

Recommended Action 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.

Message SYSMGR-2-REDSTATE_SETFAILED: Failed to set redundancy state: ret_val ([dec]).

Explanation The local supervisor is unable to get the redundancy state.

Recommended Action 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.

Message SYSMGR-2-REDUNDANCY_CHANNEL_FAILURE: Remote sup will be rebooted since its coming up as active when local sup is still active.

Explanation Remote sup is becoming active although local sup is still active. As a result, local sup will cause the remote sup to reset itself.

Recommended Action If the problem persists, please contact customer support.

Message SYSMGR-2-REDUNDANCY_HEARTBEAT_FAILURE: Heartbeat between active and standby on the redundancy channel not working for last [dec] minutes.

Explanation This supervisor is not receiving heartbeat on the redundancy channel from the other supervisor. This can result in problems during switchover and switchover may even fail.

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.

Message SYSMGR-2-RESTART_SYSTEM_LOG: We will be restarting system soon for vdc [dec].

Explanation We will be restarting system since we were trying to do a hot switchover before all the state could have been transferred to this supervisor. So we will be doing a cold switchover now.

Recommended Action No action is required.

Message SYSMGR-2-RESTORE_RUNTIME_DB_FAILED: Restoring of runtime database for fabric switch upgrade failed during boot (error-id [hex]).

Explanation This message indicates that the runtime database could not be restored during boot for the fabric switch upgrade.

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.

Message SYSMGR-2-SAVE_RUNTIME_DB_FAILED: Saving of runtime database for fabric switch upgrade failed (error-id [hex]).

Explanation This message indicates that the runtime database could not be saved for the fabric switch upgrade.

Recommended Action 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.

Message SYSMGR-2-SERVICE_CRASHED: Service "[chars]" (PID [dec]) hasntcaughtsignal[dec][chars]'

Explanation A service has terminated its execution abnormally. The service might be restarted, depending on the HA policies implemented for the service.

Recommended Action Please use the command 'show process' to verify that the service has been restarted.

Message SYSMGR-2-SHUTDOWN_FAILURE: Unable to set signal handler for graceful. shutdown: [chars] (error-id [hex]).

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-2-SHUTDOWN_REJECT: The System Manager is busy saving the configuration. Please try again later.

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-2-SHUTDOWN_SYSTEM_LOG: vdc [dec] will shut down soon.

Explanation We are shutting down system the vdc.

Recommended Action No action is required.

Message SYSMGR-2-SIGKILL_FAILURE: Service "[chars]" failure to respond to SIGKILL causing supervisor to reset. Last heartbeat %.2f secs ago.

Explanation We will be resetting the supervisor since service failed to respond to SIGKILL sent to it by System Manager.

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.

Message SYSMGR-2-SOCKET_ERROR: Failed to open socket connection, errno: [dec].

Explanation Call to open socket connection failed.

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.

Message SYSMGR-2-SRV_CLEAR_MEMORY_ALERT: service "[chars]" clear memory alert ([dec]%)

Explanation Clean Memory Alert Event received

Recommended Action No action is required.

Message SYSMGR-2-SRV_MAJOR_MEMORY_ALERT: service "[chars]" major memory alert ([dec]%)

Explanation Major Memory Alert Event received

Recommended Action No action is required.

Message SYSMGR-2-SRV_MINOR_MEMORY_ALERT: service "[chars]" minor memory alert ([dec]%)

Explanation Minor Memory Alert Event received

Recommended Action No action is required.

Message SYSMGR-2-SRV_SPAWN_FAILED: Spawning of service "[chars]" in vdc [dec] failed : [chars] (error-id [hex]).

Explanation Failed to spawn a service

Recommended Action No action is required.

Message SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up.

Explanation This message is printed if the standby supervisor does not complete its boot procedure (i.e.it doesn't reach the login prompt on the local console) 3 to 6 minutes after the loader has been loaded by the BIOS. This message is usually caused by boot variables not properly set for the stand by supervisor. This message can also be caused by a user intentionally interrupting the boot procedure at the loader prompt (by means of pressing ESC).

Recommended Action Connect to the local console of the standby supervisor. If the supervisor is at the loader prompt, try to use the boot' command to continue the boot procedure. Otherwise, issue a 'reload' command for the stand by supervisor from avsh session on the active supervisor, specifying the 'force-dnld' option. Once the stand by is online, fix the problem by setting the boot variables appropriately.

Message SYSMGR-2-STARTUP_CONVERSION_FAILED: Startup config conversion failed during boot (error-id [hex]).

Explanation This message indicates that the conversion of startup configuration failed during boot.

Recommended Action If the problem persists, please use the 'vshboot' command in system to initialize the configuration partition.

Message SYSMGR-2-START_SCRIPT_FAILED: Start script (/isan/etc/rc.sysmgr start) failed with return value: ([dec]).

Explanation The initialization of the system could not complete.

Recommended Action 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.

Message SYSMGR-2-SUBPROC_SPAWN_FAILED: Spawning of sub-process “[chars]" in vdc [dec] failed: [chars] (error-id [hex]).

Explanation Failed to spawn a sub-process

Recommended Action No action is required.

Message SYSMGR-2-SUP_POWERDOWN: Supervisor in slot [dec] is running with less memory than active supervisor in slot [dec]

Explanation Supervisor memory mismatch

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_OVER: Switchover completed.

Explanation The switchover is completed.

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_SRVCRASHED: Service "[chars]" (PID [dec]) crashed during switchover - hasn’t caught signal[dec].Core will not be collected.'

Explanation The switchover failed because a service crashed during switchover.

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_SRVFAILED: Service "[chars]" failed in performing its switchover actions (error-id [hex]).

Explanation The switchover failed because a service could not transition to the active state.

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_SRVTERMINATED: Service "[chars]" (PID [dec]) terminated during switchover with error code [dec].

Explanation The switchover failed because a service terminated during switchover.

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_THRESHOLD_EXCEEDED: Switchover threshold exceeded ([dec] switch overs happened within [dec] seconds). Powering down all linecards.

Explanation Switchover threshold exceeded

Recommended Action No action is required.

Message SYSMGR-2-SWITCHOVER_TIMEOUT: Service "[chars]" (vdc [dec]) did not respond to switchover message in [dec] seconds

Explanation The switchover timeout because a service failed to response

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.

Message SYSMGR-2-SYNC_FAILURE_MSG_PAYLOAD: vdc [dec]: [chars]

Explanation Dump out the msg to know what causes sync failure

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.

Message SYSMGR-2-SYNC_FAILURE_STANDBY_RESET: Failure in syncing messages to standby for vdc [dec] causing standby to reset.

Explanation We will be resetting the standby since mts on the active is unable to sync messages to standby.

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.

Message SYSMGR-2-SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG: This supervisor will temporarily remain online in order to collect show tech-support. This behavior is configurable via system [no] auto-collect tech-support'

Explanation Supervisor is automatically collecting logs

Recommended Action No action is required.

Message SYSMGR-2-TMP_DIR_FULL: System temporary directory usage is unexpectedly high at [dec]%.

Explanation System /tmp space is almost full.

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.

Message SYSMGR-2-VDC_CREATE_DELETE_SRVCRASHED: Global vdc-aware service "[chars]" (PID [dec]) crashed during vdc create/delete on standby - hasn’t caught signal [dec].'

Explanation The creation/deletion of vdc on standby failed because a global vdc-aware service crashed on standby.

Recommended Action No action is required.

Message SYSMGR-2-VDC_CREATE_DELETE_SRVTERMINATED: Global vdc-aware service [chars] (PID [dec]) terminated during vdc create/delete on standby with error code [dec].

Explanation The creation/deletion of vdc on standby failed because a global vdc-aware service terminated on standby.

Recommended Action No action is required.

Message SYSMGR-2-VDC_DELETE_FAILURE: The vdc delete has failed: [chars] (error-id [hex])

Explanation The vdc delete has failed

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.

Message SYSMGR-2-VDC_NOT_CLEANEDUP_SRVS: vdc [dec]: [chars]

Explanation

Recommended Action No action is required.

Message SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is unexpectedly high at [dec]%.

Explanation System volatile database space is almost full.

Recommended Action Please run the command system pss shrink'. If this message continue persistent, please contact TAC.'

Message SYSMGR-2-WARMSWITCHOVER_START: This supervisor is becoming active.

Explanation A cold switchover has started.

Recommended Action When the other supervisor is back online, use the command 'show system reset-reason' to know what caused the switchover.

Message SYSMGR-2-WDT_KGDB: System watchdog kgdb has been [chars] for slot [dec].

Explanation System watchdog kgdb has been [chars]. If the command has been enabled, the system will go into kgdb if there is a watchdog timeout.

Recommended Action No action is required.

SYSMGR-3

Message SYSMGR-3-BASIC_TRACE: [chars]: PID [dec] with message [chars].

Explanation

Recommended Action No action is required.

Message SYSMGR-3-CAPABILITY_REDUN_CHANGE: Redundancy mode changed to [chars] due to configuration change.

Explanation Some configuration changes have occurred causing administrative redundancy mode to change.

Recommended Action No action is required.

Message SYSMGR-3-CFGCTRL_ABORT: signal to abort cfgctrl as super changes to the unstable state

Explanation When super state changes to unstable, cfgctrl should be terminated

Recommended Action No action is required.

Message SYSMGR-3-CFGERASE_FAILED: Configuration erase failed (error-id [hex]).

Explanation The requested configuration erase has failed. [dec] is the error-ID representing the failure reason.

Recommended Action No action is required.

Message SYSMGR-3-CFGSNAPSHOT_FAILED: Configuration snapshot failed (error-id [hex]).

Explanation The requested configuration snapshot has failed. [dec] is the error-id representing the failure reason.

Recommended Action No action is required.

Message SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id [hex]).

Explanation The requested configuration copy has failed. [dec] is the error-id representing the failure reason.

Recommended Action No action is required.

Message SYSMGR-3-CFGWRITE_REJECT: Discarding request for configuration [chars]: configuration action already in progress.

Explanation Another instance of the command 'copy running-config startup-config' is in progress.

Recommended Action Please wait for the other instance to complete.

Message SYSMGR-3-CFGWRITE_SRVCRASHED: Service [chars] crashed with signal ([dec]) while configuration was being saved

Explanation A required service has crashed while configuration was being saved. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-CFGWRITE_SRVFAILED: Service "[chars]" failed to store its configuration (error-id [hex]).

Explanation A required service has failed to store its own configuration into the startup-config. The overall configuration copy is considered failed.

Recommended Action Use the 'show process' command to verify that the system is running properly and the service [chars] is behaving correctly. Then try again.

Message SYSMGR-3-CFGWRITE_SRVTERMINATED: Service [chars] terminated with error code ([dec]) while configuration was being saved

Explanation A required service has terminated while configuration was being saved. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-CFGWRITE_SRVTIMEOUT: Service [chars] failed to store its configuration in the timeout period

Explanation A required service has failed to send a response after receving a request to store its configuration into the startup-config. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-CFGWRITE_VDCSRVCRASHED: Service [chars] in vdc [dec] crashed with signal ([dec]) while configuration was being saved

Explanation A required service has crashed while configuration was being saved. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-CFGWRITE_VDCSRVFAILED: Service "[chars]" in vdc [dec] failed to store its configuration (error-id [hex]).

Explanation A required service has failed to store its own configuration into the startup-config. The overall configuration copy is considered failed.

Recommended Action Use the show process command to verify that the system is running properly and the service [chars] is behaving correctly. Then try again.

Message SYSMGR-3-CFGWRITE_VDCSRVTERMINATED: Service [chars] in vdc [dec] terminated with error code ([dec]) while configuration was being saved

Explanation A required service has terminated while configuration was being saved. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-CFGWRITE_VDCSRVTIMEOUT: Service [chars] in vdc [dec] failed to store its configuration in the timeout period

Explanation A required service has failed to send a response after receving a request to store its configuration into the startup-config. The overall configuration copy is considered failed.

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.

Message SYSMGR-3-COPY_CORES_FAILED: Copying cores failed ([dec]).

Explanation Copying cores to the destination failed because of an error specified in the log.

Recommended Action No action is required.

Message SYSMGR-3-COREDUMP_TIMEOUT: Failed to store the core in the specified time. Resetting....

Explanation Failed to store the core in the specified time. Resetting...

Recommended Action No action is required.

Message SYSMGR-3-CORE_CLIENT_INIT_FAILED: Core client will not be started due to some internal error.

Explanation Core client will not be started due to some internal error.

Recommended Action No action is required.

Message SYSMGR-3-CORE_OP_FAILED: Core operation failed: [chars]

Explanation Mainly use to display failure on core operation in general

Recommended Action No action is required.

Message SYSMGR-3-CORE_SERVER_INIT_FAILED: Core server will not be started due to some internal error.

Explanation Core server will not be started due to some internal error.

Recommended Action No action is required.

Message SYSMGR-3-DAEMONIZE_FAILED: Unable to daemonize service "[chars]": [chars] ([dec]).

Explanation A service could not be spawned.

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.

Message SYSMGR-3-FAILED_PFM_HANDSHAKE: PFM-handshake from service "[chars]" failed (error-id [hex]).

Explanation The Platform Manager handshake has failed. The system ca not proceed with the initialization.'

Recommended Action No action is required.

Message SYSMGR-3-GSYNC_TIMEOUT_FAILED: Failed to set timeout for global sync for an application ([dec]).

Explanation Failed to set timeout for global sync for an application. This can result in global sync to be stuck forever if application never complete global sync.

Recommended Action No action is required.

Message SYSMGR-3-HEARTBEAT_FAILURE: Service "[chars]" sent SIGABRT for not setting heartbeat for last [dec] periods. Last heartbeat %.2f secs ago.

Explanation A service is not setting proper heartbeats to System Manager So it will kill this service and if this service has restartability set to TRUE, the service will restart.

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.

Message SYSMGR-3-INVALID_BOOT_HANDSHAKE: Boot-scope-handshake received from service [chars], that is in scope [dec] (not the boot scope).

Explanation A service is trying to take actions that belong to a different class of services.

Recommended Action 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.

Message SYSMGR-3-INVALID_GSYNC_GET: Service "[chars]" vdc [dec] requesting gsync without setting proper flag in its conf file.

Explanation Service is requesting global sync without setting proper flag in its conf file.

Recommended Action No action is required.

Message SYSMGR-3-INVALID_PFM_HANDSHAKE: PFM-handshake received from service [chars], that is in scope [dec] (not the boot scope).

Explanation A service is trying to take actions that belong to the Platform Manager service.

Recommended Action 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.

Message SYSMGR-3-INVALID_TRANSITION: Transition from state [chars] to state [chars] is not allowed.

Explanation Unexpected transition in the System Manager state machine.

Recommended Action 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.

Message SYSMGR-3-INVALID_UUID: Service [chars] is configured with UUID [hex], but uses UUID [hex].

Explanation The identity of a service is inconsistent in the image file

Recommended Action 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.

Message SYSMGR-3-ISSU_BEGIN_FAILED: ISSU cannot proceed (error-id [hex]).

Explanation This message indicates that some service has blocked the ISSU.

Recommended Action No action is required.

Message SYSMGR-3-LC_IMAGE_UPGRADE_FAILURE: Linecard image upgrade request failed (error-id [hex]).

Explanation Linecard image upgrade request failed

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.

Message SYSMGR-3-LC_RESET: Resetting linecard

Explanation Linecard is being reset

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.

Message SYSMGR-3-LC_SAVE_STATES_FAILURE: Save states request for the linecard failed (error-id [hex]).

Explanation Save state request for the linecard failed

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.

Message SYSMGR-3-LC_STOP_ASYNC_FAILURE: Stop async notification request failed (error-id [hex]).

Explanation Stop async notification request for the linecard failed

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.

Message SYSMGR-3-LC_UPG_ERROR: LC ERROR: [chars]

Explanation Linecard upgrade Message

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.

Message SYSMGR-3-MISSING_OPTIONAL_CAPABILITY: Incomplete support for the current running-config on standby supervisor.

Explanation Loose config incompatibilities exist between active and standby sup. Operational redundancy mode is still set to HA.

Recommended Action No action is required.

Message SYSMGR-3-MODULE_LOCK_FAILED: Failed to lock the local module to avoid reset (error-id [hex]).

Explanation Locking the local module has failed. Reloading the local module can now result in switchover to fail.

Recommended Action No action is required.

Message SYSMGR-3-ND_UPGD_RECOVERY_SRVFAILED: Service "[chars]" in vdc [dec] failed in non-disruptive upgrade recovery (error-id [hex]).

Explanation The non-disruptive upgrade failed because a service could not recover its state.

Recommended Action No action is required.

Message SYSMGR-3-OPERATIONAL_MODE_WARM: Operational redundancy mode set to warm (error-id [hex]).

Explanation Operational redundancy mode will be set to warm. [dec] is the error-ID representing the reason.

Recommended Action No action is required.

Message SYSMGR-3-PARTIAL_CFGWRITE_FAILED: Partial configuration copy failed (error-id [hex]).

Explanation The requested configuration copy has failed. [dec] is the error-ID representing the failure reason.

Recommended Action No action is required.

Message SYSMGR-3-PARTIAL_CFGWRITE_VER_MISMATCH: Startup-config version not same as current software version.

Explanation Startup-config version not same as current software version.

Recommended Action Please do a copy running startup, and try again.

Message SYSMGR-3-RTDBCTRL_BUILD_UPG_TBL_FAILED: Failed to prepare upgrade version table during pre-upgrade

Explanation A required sequence in the pre-upgrade sequence has failed. The version table could not be built correctly

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.

Message SYSMGR-3-RTDBCTRL_SRVFAILURE: Service "[chars]" responded with a failure

Explanation A service responded with a failure to the request

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.

Message SYSMGR-3-RTDBCTRL_SRVTIMEOUT: Service [chars] failed to respond back to System Manager in the specified timeout period

Explanation A required service has failed to send a response after receiving a request for the fabric switch upgrade.

Recommended Action 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.

Message SYSMGR-3-RTDBCTRL_SRV_RECV_FAILED: Failed to receive response from Service "[chars]"

Explanation A required service has failed to send a response after receiving a request for the fabric switch upgrade.

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.

Message SYSMGR-3-RTDBCTRL_SRV_SEND_FAILED: Failed to send upgrade request to Service "[chars]"

Explanation Failed to send upgrade request to a required service

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.

Message SYSMGR-3-SERVICE_TERMINATED: Service [chars] (PID [dec]) has finished with error code [chars] ([dec]).

Explanation A service has terminated its execution normally. Depending on the value of [dec2] and the HA policies implemented for the service, the service might be restarted automatically.

Recommended Action No action is required.

Message SYSMGR-3-SHUTDOWN_OVER: The System Manager is shutting down now.

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-3-SHUTDOWN_START: The System Manager has started the shutdown procedure.

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-3-STANDBY_UNSTABLE_FTSET_OPERATION: Restarting standby since it is not in hot standby state while feature-set operation was in progress in vdc [dec].

Explanation Standby unstable during feature-set operation

Recommended Action No action is required.

Message SYSMGR-3-STANDBY_VDC_RESTART_FAILURE: vdc [dec] on standby failed to restart. error: [chars] ([hex])

Explanation

Recommended Action No action is required.

Message SYSMGR-3-SYSMGR_CRASHED: Sysmgr (PID [dec]) [chars]

Explanation Sysmgr has terminated abnormally.

Recommended Action Please use the command 'show process' to verify that sys mgr has been restarted.

Message SYSMGR-3-TFTP_CORES_FAILED: TFTPing cores failed ([chars]).

Explanation TFTPing cores to the destination failed because of an error specified in the log.

Recommended Action No action is required.

Message SYSMGR-3-UNACCEPTABLE_WAIT: Service [chars], no response from System Manager after [dec] seconds. Terminating.

Explanation A spawned service could not handshake with the System Manager and it's about to be terminated.

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.

Message SYSMGR-3-UNLINK_RELINK_CONF_FILES_FAILED: [chars] of conf files failed. plugin_id [dec]

Explanation Unlink and/or Relink of configuration files failed.

Recommended Action No action is required.

Message SYSMGR-3-URIFS_APPLY_FAILED: Applying URI filesystem database failed (error-id [hex]).

Explanation The application of URI filesystem database has failed. [dec] is the error-ID representing the failure reason.

Recommended Action No action is required.

SYSMGR-4

Message SYSMGR-4-BASIC_TRACE_WARNING: [chars]: PID [dec] with message [chars].

Explanation

Recommended Action No action is required.

Message SYSMGR-4-CFGWRITE_PARTIALFORCED: Some services are missing; partial configuration write forced.

Explanation The system is not fully operational, but a configuration copy has been forced. The services that are not running wont save their configuration, and then ext time they will restart with a default configuration.

Recommended Action Use the 'show process' command to find out which required services are not running.

Message SYSMGR-4-ON_DEMAND_STOP_UID_KNOWN: On-demand service "[chars]" stopped by uid ([dec]).

Explanation The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.

Recommended Action No action is required.

Message SYSMGR-4-ON_DEMAND_STOP: On-demand service "[chars]" stopped.

Explanation The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.

Recommended Action No action is required.

Message SYSMGR-4-PARSEWARN_INVALID_CFGFILE: [chars]: unable to find "[chars]": [chars] ([dec]).

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

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.

Message SYSMGR-4-PARSEWARN_RESTART_CNT_TOO_BIG: Service "[chars]": [chars] restart count of [dec] too big, needs to be set to [dec].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

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.

Message SYSMGR-4-PARSEWARN_VALUE_TOO_SMALL: [chars]: [chars] is too small, replaced with [dec].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

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.

Message SYSMGR-4-READCONF_REJECT: Discarding configuration update request: [chars].

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-4-READCONF_STARTED: Configuration update started (PID [dec]).

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-4-SRVSCOPE_DELAYED: Waiting for redundancy state; termination delayed for scope [chars].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-4-SYSMGR_CORE_TRUNCATED: Core seems to be truncated on generation. [dec] / [dec] KB. PID: [dec]

Explanation Core likely truncated

Recommended Action No action is required.

Message SYSMGR-4-SYSMGR_PLUGIN_FAILURE: Received failure response [hex] from Plugin Manager

Explanation Failure response from plugin mgr

Recommended Action No action is required.

Message SYSMGR-4-SYSMGR_VDC_CORE_DELETION: Cores in VDC [dec] will be deleted as part of VDC deletion

Explanation VDC cores deleted

Recommended Action No action is required.

Message SYSMGR-4-UGRP_ALL_COMPLETED: Upgrade completed for all the groups.

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-4-VAR_SYSMGR_FULL: System core file storage usage is unexpectedly high at [dec]%. This may cause corruption of core files

Explanation System core file storage space is almost full.

Recommended Action Please copy cores off the supervisor and run 'clear cores' to free some space

SYSMGR-5

Message SYSMGR-5-CFGERASE_DONE: Configuration erase successful.

Explanation The requested configuration erase has completed successfully.

Recommended Action No action is required.

Message SYSMGR-5-CFGERASE_STARTED: Configuration erase started (PID [dec]).

Explanation The requested configuration erase has started. [dec] is the Process-ID of the process servicing the request.

Recommended Action No action is required.

Message SYSMGR-5-CFGINIT_STARTED: Initialization of the startup configuration started (PID [dec]).

Explanation The requested initialization of the startup configuration has started. [dec] is the Process-ID of the process servicing the request.

Recommended Action No action is required.

Message SYSMGR-5-CFGSNAPSHOT_DONE: Configuration snapshot successful.

Explanation The requested configuration snapshot has completed successfully.

Recommended Action No action is required.

Message SYSMGR-5-CFGSNAPSHOT_STARTED: Configuration snapshot started (PID [dec]).

Explanation The requested configuration snapshot has started. [dec] is the Process-ID of the process servicing the request.

Recommended Action No action is required.

Message SYSMGR-5-CFGWRITE_DONE: Configuration copy successful.

Explanation The requested configuration copy has completed successfully.

Recommended Action No action is required.

Message SYSMGR-5-CFGWRITE_STARTED: Configuration copy started (PID [dec]).

Explanation On the active supervisor, this message indicates that the system has started to service a 'copy running-config startup-config' requested by the user. On the standby supervisor, this message indicates that the system is synchronizing the startup-config from the active supervisor.[dec] is the Process-ID of the process servicing the request.'

Recommended Action No action is required.

Message SYSMGR-5-CONVERT_STARTUP_STARTED: Configuration conversion started (PID [dec]).

Explanation This message indicates that the system has started conversion of startup configuration. This happens either on system boot or during the course of an upgrade.

Recommended Action No action is required.

Message SYSMGR-5-DELETE_BINARY_STARTUP_STARTED: Deletion of binary startup configuration started (PID [dec]).

Explanation This message indicates that the system will be deleting the binary startup configuration, due to an error in the conversion of the startup conversion.

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.

Message SYSMGR-5-FSM_STATE_TRANS: System Manager NESTED state transition from [chars] to [chars].

Explanation

Recommended Action No action is required.

Message SYSMGR-5-IMPROPER_CLEANUP: Service "[chars]" exited without replying to switchover request.

Explanation A conditional service exited without replying to switchover request. This message is for logging purposes only and does not affect the functionality of the system

Recommended Action No action is required.

Message SYSMGR-5-ISSU_ABORT: Notifying services of aborted ISSU (PID [dec]).

Explanation This message indicates that the ISSU has been aborted and the services have been asked to rollback any changes.

Recommended Action No action is required.

Message SYSMGR-5-ISSU_BEGIN_STARTED: Notifying services of ISSU (PID [dec]).

Explanation This message indicates that the system has started notifying services for the ISSU. Services can block the upgrade at this point.

Recommended Action No action is required.

Message SYSMGR-5-LC_UPGRADE_REBOOT: Rebooting linecard as a part of upgrade

Explanation Linecard is being rebooted as a part of upgrade

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.

Message SYSMGR-5-LC_UPGRADE_START: Starting linecard upgrade

Explanation Linecard upgrade is starting

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.

Message SYSMGR-5-MODULE_ONLINE: System Manager has received notification of local module becoming online.

Explanation System Manager has received notification of local module becoming online.

Recommended Action No action is required.

Message SYSMGR-5-PARTIAL_CFGWRITE_ASCII_CONFIG: Startup-config version not present.

Explanation Startup-config version not present.

Recommended Action Startup-config version is not present. Ascii configuration will be applied.

Message SYSMGR-5-PARTIAL_CFGWRITE_DONE: Partial configuration copy successful.

Explanation The requested configuration copy has completed successfully.

Recommended Action No action is required.

Message SYSMGR-5-PARTIAL_CFGWRITE_STARTED: Partial configuration copy started by UUID [hex] (PID [dec]).

Explanation This message is printed only on active supervisor, and indicates that service with mentioned UUID has requested a partial write mem. [dec] is the Process-ID of the process servicing the request.

Recommended Action No action is required.

Message SYSMGR-5-RECOVERY_FAILED: Stateful recovery failed, system manager will now start stateless.

Explanation Stateful recovery failed, system manager will now restart system and start stateless.

Recommended Action No action is required.

Message SYSMGR-5-RUNTIME_DB_RESTORE_STARTED: Runtime database controller started (PID [dec]).

Explanation This message indicates that the system has started the restoration of the runtime database. This happens during the non-disruptive fabric switch upgrade.

Recommended Action No action is required.

Message SYSMGR-5-RUNTIME_DB_RESTORE_SUCCESS: Runtime database successfully restored.

Explanation This message indicates that the runtime database has been successfully restored for the non-disruptive fabric switch upgrade.

Recommended Action No action is required.

Message SYSMGR-5-RUNTIME_DB_SAVE_STARTED: Runtime database save has started (PID [dec]).

Explanation This message indicates that the system has started the saving of the runtime database. This happens during the non-disruptive fabric switch upgrade.

Recommended Action No action is required.

Message SYSMGR-5-SERVICE_DELETED: Service [chars] has been removed from the System Manager database.

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

Message SYSMGR-5-STATEFUL_STATE: System Manager is in state [chars] after stateful restart.

Explanation System Manager has been restarted stateful after an error that resulted in System Manager exiting.

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.

Message SYSMGR-5-SUBPROC_KILLED: "[chars]" (PID [dec]) hasn’t caught signal[dec][chars]

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-5-SUBPROC_TERMINATED: "[chars]" (PID [dec]) has finished with error code [chars] ([dec]).

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-5-UGRP_COMPLETED: Upgrade completed for group [dec].

Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).

Recommended Action No action is required.

SYSMGR-6

Message SYSMGR-6-ALL_SCOPES_STARTED: System services have completely started at this time.

Explanation System services have completely started at this time.

Recommended Action No action is required.

Message SYSMGR-6-HANDSHAKE_DONE: Handshake with service "[chars]" successfully performed.

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-6-HANDSHAKE_VERIFYING_DONE: Handshake verification done from service "[chars]".

Explanation

Recommended Action No action is required.

Message SYSMGR-6-LC_UPG_DEBUG: LC DEBUG: [chars]

Explanation Linecard upgrade debug message

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.

Message SYSMGR-6-RLIMIT_INFO: rlimit of service "[chars]"([dec]) = %llu

Explanation

Recommended Action No action is required.

Message SYSMGR-6-SERVICE_STARTED: Service "[chars]" in vdc [dec] started with PID([dec]).

Explanation The System Manager is starting a service. This message is for debugging purposes only.

Recommended Action No action is required.

Message SYSMGR-6-SERVICE_SUCCESS_EXIT: Service [chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]).

Explanation A service has successfully exited its execution.

Recommended Action No action is required.

Message SYSMGR-6-SRVSCOPE_COMPLETED: Completed execution for scope [chars].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-6-SRVSCOPE_STARTED: Started execution for scope [chars].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-6-SRVSTATE_CHANGED: State for service "[chars]" changed from [chars] to [chars] in vdc [dec].

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-6-SRV_ENQUEUED_FOR_START: Conditional service "[chars]" started by sap "[dec]" has been enqueued for start.

Explanation

Recommended Action No action is required.

Message SYSMGR-6-STATE_CHANGED: System Manager state changed from [chars] to [chars] for vdc [dec].

Explanation

Recommended Action No action is required.

Message SYSMGR-6-SUBPROC_SUCCESS_EXIT: [chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]).

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-6-SUPERSTATE_CHANGED: System Manager super state changed from [chars] to [chars] for vdc [dec].

Explanation

Recommended Action No action is required.

Message SYSMGR-6-UNEXPECTED_GSYNC_RESTART_STANDBY: Sending a message to restart system on standby on vdc [dec].

Explanation Activity occurred on active supervisor that is incompatible with state of standby. System will be restarted on standby.

Recommended Action No action is required.

SYSMGR-7

Message SYSMGR-7-CFGWRITE_UNEXPECTEDRSP: Discarding unexpected response from service "[chars]".

Explanation

Recommended Action No action is required.

Message SYSMGR-7-DUPLICATED_PFM_HANDSHAKE: PFM-handshake received from service [chars], but information already available.

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-7-LIBCDB_FAILURE: Conversion for service "[chars]" failed in libcdb.

Explanation This message indicates that either the system could not find conversion tarball or there is no conversion library needed for this service.

Recommended Action No action is required.

Message SYSMGR-7-LIBVDB_FAILURE: Conversion for service "[chars]" failed in libvdb.

Explanation This message indicates that the system could not find package information for this service in the version database.

Recommended Action No action is required.

Message SYSMGR-7-ND_UPGD_RECOVERY_SRVSUCCEEDED: Service "[chars]" recovered its state during non-disruptive upgrade.

Explanation

Recommended Action No action is required.

Message SYSMGR-7-NO_STARTUP_CONFIG: No startup-config to convert.

Explanation This message indicates that the system tried to convert startup configuration but it found no configuration to convert.

Recommended Action No action is required.

Message SYSMGR-7-SWITCHOVER_SRVSUCCEDED: Service "[chars]" completed its switchover actions.

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-7-UNEXPECTEDMSG: Opcode [dec] not expected at this time from service "[chars]" ([chars]).

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-7-UNKNOWNADDR: Opcode [dec] received from unknown source [chars]. Discarding.

Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.

Recommended Action No action is required.

Message SYSMGR-7-UNKNOWNMSG: Unknown opcode [dec] received from [chars].

Explanation The System Manager has received an unrecognized message with the specified opcode. [chars] is the source of the message. This message is for debugging purposes only.

Recommended Action No action is required.

Message SYSMGR-7-UNKNOWNPID: Opcode [dec] received from [chars] with unknown PID [dec]. Discarding.

Explanation The System Manager has received a message from an unknown process. [chars] is the source of the message. This message is for debugging purposes only.

Recommended Action No action is required.

Message SYSMGR-7-UNKNOWNUUID: Opcode [dec] received from [chars] with unknown UUID [dec]. Discarding.

Explanation The System Manager has received an unrecognized message from the specified UUID. [chars] is the source of the message. This message is for debugging purposes only.

Recommended Action No action is required.

SYSTEM HEALTH LC Messages

This section contains the SYSTEM HEALTH LC messages.

SYSTEM HEALTH LC-2

Message SYSTEM HEALTH LC-2-OHMS_FIPS_FAILURE: FIPS compliance error during random number generation.

Explanation FIPS compliance error.

Recommended Action No action is required.

Message SYSTEM HEALTH LC-2-OHMS_LC_CF_CRC_FAILED: Compact Flash firmware CRC checksum on module [dec] is corrupted.

Explanation Compact flash firmware has been corrupted.

Recommended Action Replace the compact flash on this module.

Message SYSTEM HEALTH LC-2-OHMS_LC_CF_INIT_ERRORS: Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec], reason:([chars]).

Explanation Compact flash CRC checksum initializations failed.

Recommended Action Check the compact flash on the board and any relevant system (mis) configurations.

Message SYSTEM HEALTH LC-2-OHMS_LC_CF_REFLASH_FAILED: Compact Flash firmware refresh procedure failed, replace the compact flash on module [dec]. Reason [dec]

Explanation Compact flash firmware has been corrupted is corrupted.

Recommended Action Replace the compact flash on this module.

Message SYSTEM HEALTH LC-2-OHMS_LC_TCAM_PARITY_OFLOW: Too many TCAM Parity errors detected on module [dec]

Explanation More parity errors than that can be corrected were detected on the affected module

Recommended Action Please schedule a downtime and reload the module. If these errors continue to happen even after module reload, please replace the module.

SYSTEM HEALTH LC-4

Message SYSTEM HEALTH LC-4-OHMS_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module [dec] Reason:([chars]).

Explanation Compact flash test errors.

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_EXIT: Online System Health exiting due to internal errors. Reason [dec]

Explanation Online System Health exiting due to internal errors.

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_LC_BATTERY_ERRORS: Battery test on module [dec] has stopped due to internal errors.

Explanation Battery test internal errors

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_LC_BOOTFLASH_TEST_ERR: Bootflash test cannot proceed due to internal errors on module [dec].

Explanation Compact flash test has had too many internal errors.

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_LC_CACHE_DISK_ERRORS: Cache disk test on module [dec] dpp [dec] has stopped due to internal errors.

Explanation Cache disk test internal errors

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_LC_CF_CRC_PASSED: Compact Flash firmware on module [dec] is healthy at this time.

Explanation The Compact Flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

SYSTEM HEALTH LC-4-OHMS_LC_CF_CRC_PROCESS_ERR:

Message SYSTEM HEALTH LC-4-OHMS_LC_CF_CRC_PROCESS_ERR: Compact flash firmware CRC checksum procedure failed on module [dec]. Reason [dec]

Explanation Compact flash firmware CRC checksum procedure failed.

Recommended Action Try restarting the cf-crc-check using system health clear-errors module cf-crc-check. If the condition still persist, schedule a downtime and replace the compact flash on the affected module.

Message SYSTEM HEALTH LC-4-OHMS_LC_CF_RECALLED: Compact Flash on module [dec] was recalled.

Explanation The Compact flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEM HEALTH LC-4-OHMS_LC_CF_REFLASH_PASSED: Compact Flash firmware was successfully refreshed on module [dec].

Explanation The Compact Flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEM HEALTH LC-4-OHMS_LC_CF_UNRESPONSIVE: Recalled Compact Flash on module [dec] is unresponsive.

Explanation The Compact flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEM HEALTH LC-4-OHMS_LC_EOBC_ERRORS: EOBC test on module [dec] has stopped due to internal errors.

Explanation EOBC test internal errors

Recommended Action No action is required.

Message SYSTEM HEALTH LC-4-OHMS_LC_EOBC_HALTED: EOBC Test Halted for module [dec]. Module needs EPLD Upgrade

Explanation Module does not have the minimum required EPLD version to run EOBC test.

Recommended Action Please upgrade the module with the latest EPLDs.'

Message SYSTEM HEALTH LC-4-OHMS_LC_TCAM_PARITY_ACL_FIB_TIMEOUT: TCAM test timeout waiting for ACL/FIB to update TCAM on module [dec]

Explanation System health TCAM test timeout occurred while waiting for response from ACL/FIB

Recommended Action If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module

Message 7 SYSTEM HEALTH LC-4-OHMS_LC_TCAM_PARITY_ACL_FIB_UPDATE_FAILING: Tcam test failed as ACL/FIB failed to update TCAM on module [dec]

Explanation ACL/FIB failed to update TCAM after soft parity errors were encountered.

Recommended Action If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module

SYSTEM HEALTH LC-6

Message SYSTEM HEALTH LC-6-OHMS_LC_STARTED: Online System Health started on LC.

Explanation Online System Health started on a line card.

Recommended Action No action is required.

SYSTEMHEALTH Messages

This section contains the SYSTEMHEALTH messages.

SYSTEMHEALTH-2

Message SYSTEMHEALTH-2-OHMS_BATTERY_FAILED: Battery [dec] failed for module [dec]. Reason: [chars].

Explanation Battery failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_DAY: Bootflash hard resets for module [dec] has reached threshold limit in 24 hours.

Explanation Bootflash hard resets reached threshold limit in 24 hours.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_LIFE: Bootflash hard resets for module [dec] has reached the maximum threshold limit.

Explanation Bootflash hard resets reached maximum threshold limit.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED: Bootflash test maximum failures reached for module [dec] Reason: ([chars]).

Explanation Bootflash failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_CACHE_DISK_FAILED: Cache disk [dec] failed for module [dec].

Explanation Cache disk failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_EMGMT_FAILED: Management port failed for module [dec].

Explanation Ethernet management port failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_EOBC_FAILED: EOBC test failed for module [dec].

Explanation EOBC test failed for module.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_FIPS_FAILURE: FIPS compliance error during random number generation.

Explanation FIPS compliance error.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_FREE_DISK_FAILED: Free Disk Space on partition [chars] is below [chars] threshold for module [dec].

Explanation System Health Free Disk Space below threshold.

Recommended Action Force a switch over if a standby supervisor is available, or reboot the switch to recover

Message SYSTEMHEALTH-2-OHMS_FREE_DISK_RUNNING: Free Disk Space on partition [chars] have increased and is above [chars] threshold for module [dec].

Explanation System Health Free Disk Space above threshold.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_INBAND_FAILED: Inband test maximum failures reached for module [dec].

Explanation Inband failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module [dec] Port [dec] has failed loop back tests.

Explanation Port loop-back test failure.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_MOD_RELOAD_REQ: Module [dec] reload being requested due to errors found by [chars] test.

Explanation System Health Module Reload Request.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_MOD_SNAKE_TEST_FAILED: Module [dec] has failed snake loopback tests.

Explanation Snake test failure.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_NVRAM_FAILED: Nvram test maximum failures reached for module [dec] for blocks 0x%llx.

Explanation Nvram failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_FAILED: Compact Flash firmware CRC checksum on module [dec] is corrupted.

Explanation Compact flash firmware has been corrupted.

Recommended Action Replace the compact flash on this module.

Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_INIT_ERRORS: Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec], reason:([chars]).

Explanation Compact flash CRC checksum initializations failed.

Recommended Action Check the compact flash on the board and any relevant system (mis) configurations.

Message SYSTEMHEALTH-2-OHMS_SUP_CF_REFLASH_FAILED: Compact Flash firmware refresh procedure failed, replace the compact flash on module [dec]. Reason [dec]

Explanation Compact flash firmware has been corrupted is corrupted.

Recommended Action Replace the compact flash on this module.

Message SYSTEMHEALTH-2-OHMS_SWITCHOVER_REQ: Supervisor switch over being requested due to errors found [chars] test.

Explanation System Health Switch Over Request.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_SWITCH_RELOAD_REQ: Switch reload request due to errors found [chars] test.

Explanation System Health Switch Reload Request.

Recommended Action No action is required.

Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_FAILED: TCAM test failed for module [dec].

Explanation TCAM test failed for module as uncorrectable parity errors were detected.

Recommended Action Please schedule a downtime and replace the module.

Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_OFLOW: Too many TCAM Parity errors detected on module [dec]

Explanation More parity errors than that can be corrected were detected on the affected module.

Recommended Action Please schedule a downtime and reload the module. If these errors continue to happen even after module reload, please replace the module.

SYSTEMHEALTH-4

Message SYSTEMHEALTH-4-OHMS_BATTERY_ERRORS: Battery test on module [dec] has been suspended due to internal errors.

Explanation Battery test internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_BOOTFLASH_TEST_ERRORS: Bootflash test cannot proceed due to internal errors on module [dec].

Explanation Compact flash test internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_CACHE_DISK_ERRORS: Cache disk test on module [dec] dpp [dec] has been suspended due to internal errors.

Explanation Cache disk test internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_CF_CRC_PASSED: Compact Flash firmware on module [dec] is healthy at this time.

Explanation The Compact Flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEMHEALTH-4-OHMS_CF_REFLASH_PASSED: Compact Flash firmware was successfully refreshed on module [dec].

Explanation The Compact Flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEMHEALTH-4-OHMS_EMGMT_ERRORS: Management port test cannot proceed due to internal errors on module [dec].

Explanation Ethernet management port internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_EOBC_ERRORS: EOBC test on module [dec] has been suspended due to internal errors.

Explanation EOBC test internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_EOBC_HALTED: EOBC Test Halted for module [dec]. Module needs EPLD Upgrade

Explanation Module does not have the minimum required EPLD version to run EOBC test.

Recommended Action Please upgrade the module with the latest EPLDs.

Message SYSTEMHEALTH-4-OHMS_EXIT: Online System Health exiting due to internal errors. Reason [dec].

Explanation Online System Health exiting due to internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_FAIL_ACTION_NOTICE: Failure action not taken, failure action is disabled.

Explanation System Health SERDES test failure.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_FREE_DISK_ERRORS: Too many errors on module [dec] while running the Free Disk Space test for partition [chars].

Explanation System Health Free Disk Space test has too many errors while running.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_FREE_DISK_FAILING: Free Disk Space on partition [chars] is starting to go below threshold for module [dec]

Explanation System Health Free Disk Space going below threshold.

Recommended Action Force a switch over if a standby supervisor is available, or reboot the switch to recover.

Message SYSTEMHEALTH-4-OHMS_INBAND_FAILING1: Inband test failed [dec] times for module [dec].

Explanation Inband Failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_INBAND_TEST_ERRORS: Too many errors while running the inband test.

Explanation Inband test has had too many errors while running.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_EXITED: System Health process running on module [dec] exited due to internal errors. Will attempt to restart.

Explanation System Heath line card daemon exited.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_FAILED: System Health process running on module [dec] failed due to fatal errors.

Explanation System Heath line card daemon failed.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_RESTARTED: System Health process running on module [dec] restarted.

Explanation System Heath line card daemon restarted.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_PATH_FAILURE: Snake Loopback data path failure on module [dec].

Explanation Snake data path only error.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_TEST_ERRORS: Snake Loopback test cannot proceed due to internal errors for module [dec].

Explanation Snake test internal errors.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_NVRAM_ERRORS: Too many errors on module [dec] while running the Nvram test.

Explanation Nvram test has had too many errors while running.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_SERDES_FAILED: SERDES loopback test on interface fc[dec]/[dec] failed.

Explanation System Health SERDES Test Failure.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module [dec] Reason:([chars]).

Explanation Compact flash test errors on supervisor.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_INTERN_ERRORS: Compact flash firmware CRC checksum procedure cannot proceed due to internal errors on module [dec].

Explanation Compact flash firmware CRC checksum procedure ended up in errors.

Recommended Action Try restarting the cf-crc-check using system health clear-errors module <x

Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_PROCESS_ERRORS: Compact flash firmware CRC checksum procedure failed on module [dec]. Reason [dec]

Explanation Compact flash firmware CRC checksum procedure failed.

Recommended Action Try restarting the cf-crc-check using system health clear-errors module <x

Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_TEST_FAILING: Compact flash firmware CRC checksum validation starting to fail on module [dec].

Explanation Compact flash firmware CRC checksum might be bad on this module.

Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades.

Message SYSTEMHEALTH-4-OHMS_SUP_CF_RECALLED: Compact Flash on module [dec] was recalled.

Explanation The Compact flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_INTERN_ERRORS: Compact Flash firmware re-flash procedure cannot proceed due to internal errors on module [dec].

Explanation Compact flash firmware re-flash procedure ended up in errors.

Recommended Action Try restarting the test using system health clear-errors module <x

Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_TEST_FAILING: Compact flash firmware refresh procedure starting to fail on module [dec].

Explanation Compact flash might be dead on this module.

Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades.

Message SYSTEMHEALTH-4-OHMS_SUP_CF_UNRESPONSIVE: Recalled Compact Flash on module [dec] is unresponsive.

Explanation The Compact flash model has data retention issues and need to be replaced.

Recommended Action Please schedule a downtime and replace the compact flash on this module.

Message SYSTEMHEALTH-4-OHMS_SVC_DAEMON_FAILED: System Health process running on module [dec] SVC node [dec] exited due to errors.

Explanation OHMS SVC daemon exited.

Recommended Action No action is required.

Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_TIMEOUT: TCAM test timeout waiting for ACL/FIB to update TCAM on module [dec]

Explanation System health TCAM test timeout occurred while waiting for response from ACL/FIB

Recommended Action If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module

Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_UPDATE_FAILING: Tcam test failed as ACL/FIB failed to update TCAM on module [dec]

Explanation ACL/FIB failed to update TCAM after soft parity errors were encountered.

Recommended Action If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module

Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ERRORS: TCAM test on module [dec] has been suspended due to internal errors.

Explanation TCAM test internal errors.

Recommended Action No action is required.

SYSTEMHEALTH-5

Message SYSTEMHEALTH-5-OHMS_BATTERY_FAILING: Battery [dec] starting to fail on module [dec]. Reason: [chars].

Explanation System Health battery failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_BOOTFLASH_FAILING: Bootflash starting to fail on module [dec].

Explanation System Health bootflash failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_CDISK_FAILING: Cache disk [dec] starting to fail on module [dec].

Explanation System Health cache disk failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_EMGMT_FAILING: Management port on module [dec] starting to show signs of failures.

Explanation System Health emgmt failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_EOBC_FAILING: EOBC starting to fail on module [dec].

Explanation System Health eobc failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_INBAND_FAILING: Inband starting to fail on module [dec].

Explanation System Health inband failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_NVRAM_FAILING: Nvram starting to fail on module [dec].

Explanation System Health Nvram failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_SUP_CF_ERRORS_CLEARED: Compact flash failing conditions on module [dec] has been cleared.

Explanation Compact flash might be dead on this module.

Recommended Action Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades.

Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_CLEARED: Failing conditions for TCAM on module [dec] have been cleared.

Explanation System Health TCAM failures cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_FAILING: TCAM starting to fail on module [dec].

Explanation System Health Tcam failing.

Recommended Action No action is required.

Message SYSTEMHEALTH-5-OHMS_TEST_FAILING: [chars] test starting to fail on module [dec].

Explanation System Health test failing.

Recommended Action No action is required.

SYSTEMHEALTH-6

Message SYSTEMHEALTH-6-OHMS_ASIC_FAILURE_INFO: Module [dec] Asic [chars] instance [dec] probable cause of failure.

Explanation HW failure analysis findings.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_BATTERY_CLEARED: Failing conditions for battery [dec] on module [dec] have been cleared.

Explanation System Health battery failure cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_BOOTFLASH_CLEARED: Failing conditions for bootflash on module [dec] have been cleared.

Explanation System Health bootflash failures cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_CDISK_CLEARED: Failing conditions for cache disk [dec] on module [dec] have been cleared.

Explanation System Health cache disk failure cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_EMGMT_CLEARED: Failing conditions for management port on module [dec] have been cleared.

Explanation System Health emgmt failure cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_EOBC_CLEARED: Failing conditions for EOBC on module [dec] have been cleared.

Explanation System Health eobc failures cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_FAILURE_CLEARED: Failing conditions for test [chars] have been cleared on module [dec].

Explanation System Health failure cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_INBAND_CLEARED: Failing conditions for inband on module [dec] have been cleared.

Explanation System Health inband failures cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_INBAND_DROP: Inband Dropping frames from module [dec] due to unknown reasons.

Explanation System Health Inband non-timeout drop.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_INBAND_TO_ERR: Inband Dropping frames from module [dec] due to timeout errors.

Explanation System Health Inband timeout drop.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_INBAND_TX_CONGESTION: Inband Unable to transmit due to TX path congestion on module [dec].

Explanation System Health Inband TX congestion.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_NVRAM_CLEARED: Failing conditions for Nvram on module [dec] have been cleared.

Explanation System Health Nvram failures cleared.

Recommended Action No action is required.

Message SYSTEMHEALTH-6-OHMS_STARTED: Online System Health started.

Explanation Online System Health started.

Recommended Action No action is required.

TACACS Messages

This section contains the TACACS messages.

TACACS-2

Message TACACS-2-TACACS_PROGRAM_EXIT: TACACS+ daemon exiting: [chars]

Explanation TACACS+ daemon is exiting.

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.

TACACS-3

Message TACACS-3-TACACS_ERROR_MESSAGE: [chars]

Explanation TACACS+ Message

Recommended Action No action is required.

TACACS-4

Message TACACS-4-TACACS_WARNING: [chars]

Explanation TACACS+ warning

Recommended Action No action is required.

TACACS-5

Message TACACS-5-TACACS_MONITOR_STATUS: [chars] [chars]

Explanation Notifying TACACS+ server monitor status change

Recommended Action No action is required.

Message TACACS-5-TACACS_NOTIFICATION: [chars]

Explanation TACACS+ notification

Recommended Action No action is required.

Message TACACS-5-TACACS_SERVER_STATUS: [chars] server [chars] with auth-port [dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was in previous-state for [chars], and total dead time of the server is [chars]

Explanation Notifying Tacacs+ server status change

Recommended Action No action is required.

TACACS-6

Message TACACS-6-TACACS_ACCOUNTING_MESSAGE: [chars]

Explanation Accounting Message

Recommended Action No action is required.

Message TACACS-6-TACACS_MESSAGE: [chars]

Explanation TACACS+ Message

Recommended Action No action is required.

TBIRD_CMN_USD Messages

This section contains the TBIRD_CMN_USD messages.

TBIRD_CMN_USD-6

Message TBIRD_CMN_USD-6-TBIRD_CMN_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

TBIRD_FWD_USD Messages

This section contains the TBIRD_FWD_USD messages.

TBIRD_FWD_USD-6

Message TBIRD_FWD_USD-6-TBIRD_FWD_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

TBIRD_MAC_USD Messages

This section contains the TBIRD_MAC_USD messages.

TBIRD_MAC_USD-3

Message TBIRD_MAC_USD-3-FCMAC_ERR_MSG: [chars]

Explanation Error log message

Recommended Action No action is required.

TBIRD_MAC_USD-6

Message TBIRD_MAC_USD-6-FCMAC_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

TBIRD_QUE_USD Messages

This section contains the TBIRD_QUE_USD messages.

TBIRD_QUE_USD-6

Message TBIRD_QUE_USD-6-TBIRD_QUE_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

TBIRD_XBAR_USD Messages

This section contains the TBIRD_XBAR_USD messages.

TBIRD_XBAR_USD-6

Message TBIRD_XBAR_USD-6-TBIRD_XBAR_DEBUG_MSG: [chars]

Explanation Debug log message

Recommended Action No action is required.

TCAP Messages

This section contains the TCAP messages.

TCAP-2

Message TCAP-2-MEM_FULL: Memory allocation failed.

Explanation TCAP process has failed to allocate memory.

Recommended Action Please perform a 'show tcap event-history' to collect more information.

Message TCAP-2-PROC_DN: Process is shutting down: [chars]

Explanation TCAP process is exiting.

Recommended Action Please perform a 'show tcap event-history' to collect more information.

Message TCAP-2-PROC_INITFAIL: Process initialization failed due to [chars].

Explanation TCAP process has failed initialization.

Recommended Action Please perform a 'show tcap event-history' to collect more information.'

TIM Messages

This section contains the TIM messages.

TIM-2

Message TIM-2-IF_CRITICAL_FAILURE: (Debug syslog) Critical failure: [chars], [chars]

Explanation There was a critical failure in the component.

Recommended Action Please follow instructions on the syslog.

Message TIM-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled. Reason:[chars])

Explanation The interface encountered an error while configuring it

Recommended Action Collect more information about failed interface using command 'show port internal all interface [char]'. In most cases, you can recover using a 'shutdown' followed a 'noshutdown' on the interface or removing and re-inserting the fibre optic-cable.

Message TIM-2-IF_DOWN_LINK_FAILURE_CRIT: 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

Message TIM-2-SEQ_TIMEOUT: Component [chars] timed out on response to opcode [chars] ([chars])

Explanation Some component did not respond to a request in stipulated time.

Recommended Action None

Message TIM-2-SYSLOG_TIM_CRITICAL: Critical failure: [chars]

Explanation There was a critical failure in the component.

Recommended Action Please collect system tech-support

TIM Messages

TIM-3

Message TIM-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface [chars] is down (Channel error disabled)

Explanation This interface belongs to a Port Channel and the Port Channel is error disabled

Recommended Action Perform 'shut' and 'no shutdown' on the Port Channel interface that it belongs to'

Message TIM-3-IF_ERROR_VLANS_REMOVED: VLANs [chars] on Interface [chars] are removed from suspended state.

Explanation The VLANs on an interface are being removed from the suspended state

Recommended Action No action is required.

Message TIM-3-IF_ERROR_VLANS_SUSPENDED: VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])

Explanation The VLANs on an interface are being suspended due to some protocol action

Recommended Action No action is required.

Message TIM-3-IF_SFP_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message TIM-3-IF_SFP_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message TIM-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported

Explanation The transceiver for the interface specified in the Message is not a Cisco supported module

Recommended Action Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced

Message TIM-3-IF_XCVR_ALARM: Interface [chars], [chars]

Explanation There was an alarm on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message TIM-3-IF_XCVR_ERROR: Interface [chars], [chars]

Explanation There was an error on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

TIM Messages

TIM-4

Message TIM-4-IF_NON_QUALIFIED_TRANSCEIVER: Non-qualified transceiver on interface [chars] was detected

Explanation The transceiver for the interface specified has not been qualified on this platform for this software release

Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details

Message TIM-4-IF_SFP_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

Message TIM-4-IF_XCVR_WARNING: Interface [chars], [chars]

Explanation There was an warning on the transceiver module

Recommended Action Please do show interface transceiver details to obtain more information

TIM Messages

TIM-5

Message TIM-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]

Explanation Interface is admin up

Recommended Action No action is required.

Message TIM-5-IF_BANDWIDTH_CHANGE: Interface [chars], bandwidth changed to [chars] Kbit

Explanation Bandwidth of the interface (port channel) has changed and this change is updated

Recommended Action No action is required.

Message TIM-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down)

Explanation Interface has been configured to be administratively down

Recommended Action Perform noshutdown''

Message TIM-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change)

Explanation FCIP interface temporarily down due to reconfiguration

Recommended Action No action is required.

Message TIM-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 Perform 'shut' and 'noshutdown' on the PortChannel interface that it belongs to.

Message TIM-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 Retry the configuration again

Message TIM-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.

Message TIM-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.

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

Explanation Isolated due to domain manager being disabled

Recommended Action No action is required.

Message TIM-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 not responding.

Recommended Action No action is required.

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

Explanation Isolating this interface due to the remote end being isolated.

Recommended Action No action is required.

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

Explanation Isolated due to domain overlap.

Recommended Action No action is required.

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

Explanation ELP failed on the interface.

Recommended Action Check the output of 'show port internal info' in the ELP failure reason 'field'

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

Explanation Trunk protocol failed

Recommended Action 'show port internal event-history msgs' will indicate the trunk protocol exchanges to determine why it failed.

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

Explanation ESC failed on the interface

Recommended Action Check the output of show port internal event-history msgs' will indicate the trunk protocol exchanges to determine why it failed.

Message TIM-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, the interface is administratively enabled.

Message TIM-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

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

Explanation The FCOT has been removed

Recommended Action Insert an FCOT

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

Explanation Fcot inserted is not a supported one

Recommended Action Please contact customer support for a list of authorized transceiver vendors

Message TIM-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)

Explanation The modules hardware has failed

Recommended Action Collect more information about failed module using command 'show module internal all module'

Message TIM-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

Message TIM-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 Perform a 'show port internal info' to determine the list of modes supported on this interface

Message TIM-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 Get the allowed receive B2B credit size from 'show port internal info'

Message TIM-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'

Message TIM-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 Perform a 'show port internal info' to determine the range of speed supported on this interface

Message TIM-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, check the output of 'show port internal event-history' to determine what it is waiting for.

Message TIM-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)

Explanation Interface removed

Recommended Action No action is required.

Message TIM-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

Message TIM-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure)

Explanation Diag failed on the interface

Recommended Action Collect more information about failed interface using command 'attach module' to connect to module

Message TIM-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

Message TIM-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.

Message TIM-5-IF_DOWN_NONE: Interface [chars] is down ([chars])

Explanation Interface is down with a possible reason.

Recommended Action Collect more information about port using command 'show port internal info/event-history' to determine why it went down

Message TIM-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating)

Explanation The loop port has been put into non participating mode

Recommended Action No action is required.

Message TIM-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.

Message TIM-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down)

Explanation Parent interface is down

Recommended Action No action is required.

Message TIM-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 This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection

Message TIM-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 The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection

Message TIM-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

Message TIM-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 perform a 'shutdown' and a 'noshutdown'

Message TIM-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.

Message TIM-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.

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

Explanation Module that has the tunnel source port of this FCIP interface is not fully online

Recommended Action The module that has the tunnel src port is coming online. Please use “show mod” to find module status

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

Explanation Tunnel port source interface unbound

Recommended Action No action is required.

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

Explanation Tunnel source port of this FCIP interface has been removed

Recommended Action The src interface with ip address that matches the ip address of the bound entity is removed. This happens normally due to the module on which the src interface exists is removed

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

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

Explanation This interface belongs to a PortChannel and 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 Port Channel

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

Explanation This interface belongs to a Port Channel and 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 Port Channel

Message TIM-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended)

Explanation This interface belongs to a Port Channel and has been suspended due to an error while bringing it up

Recommended Action Perform a 'shutdown' and a 'no shutdown'. If this happens again obtain output of 'show port internal info/event-history' on the interface

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

Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Interface is down due to maximum retransmission failure

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr trace route ip addr

Message TIM-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 TCP persist timer expired

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

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

Explanation Upgrade of the linecard software is in progress

Recommended Action No action is required.

Message TIM-5-IF_DOWN_VRF_UNUSABLE: Interface [chars] is down (Vrf down)

Explanation The VRF for which this interface is a member is removed

Recommended Action No action is required.

Message TIM-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 with the VSANs configured on the remote end

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

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

Explanation Isolated due to a failure during zone merge

Recommended Action No action is required.

Message TIM-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.

Message TIM-5-IF_DUPLEX: Interface [chars], operational duplex mode changed to [chars]

Explanation Operational duplex mode has changed when link came up

Recommended Action No action is required.

Message TIM-5-IF_ERRDIS_RECOVERY: Interface [chars] is being recovered from error disabled state (Last Reason:[chars])

Explanation Interface is being recovered from error disabled state

Recommended Action No action is required.

Message TIM-5-IF_HARDWARE: Interface [chars], hardware type changed to [chars]

Explanation There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed

Recommended Action No action is required.

Message TIM-5-IF_L2MP_MODE: Interface [chars], l2mp-mode changed to [chars]

Explanation The l2mp-mode on the port has changed

Recommended Action No action is required.

Message TIM-5-IF_RX_FLOW_CONTROL: Interface [chars], operational Receive Flow Control state changed to [chars]

Explanation Operational receive flow control has changed when link came up

Recommended Action No action is required.

Message TIM-5-IF_TRUNK_DOWN: Interface [chars], vlan [chars] down

Explanation Interface [chars] is trunking, VLANs [chars] are down

Recommended Action The following commands will help determine why this VSAN is down on this interface: show interface, show port internal info interface VSAN, show port internal event-history interface vsan

Message TIM-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up

Explanation Interface [chars] is trunking, VLANs [chars] are up

Recommended Action No action is required.

Message TIM-5-IF_TX_FLOW_CONTROL: Interface [chars], operational Transmit Flow Control state changed to [chars]

Explanation Operational transmit flow control has changed when link came up

Recommended Action No action is required.

Message TIM-5-IF_UP: Interface [chars] is up [chars]

Explanation Interface is up in mode specified, if applicable

Recommended Action No action is required.

Message TIM-5-SPEED: Interface [chars], operational speed changed to [chars]

Explanation Operational speed has changed when link came up

Recommended Action No action is required.

Message TIM-5-STORM_CONTROL_ABOVE_THRESHOLD: Traffic in port [chars] exceeds the configured threshold [chars]

Explanation Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped

Recommended Action Identify source of traffic storm

Message TIM-5-STORM_CONTROL_BELOW_THRESHOLD: Traffic in port [chars] has fallen below the configured threshold [chars]

Explanation Traffic on specified port has returned to within configured storm-control threshold

Recommended Action No action is required.

 

TLPORT Messages

This section contains the TLPORT messages.

TLPORT-2

Message TLPORT-2-INITFAIL: TL Port Manager Initialization failed: [chars]

Explanation TL Port Manager initialization failed. [chars] explains the reason for the failure.

Recommended Action No action is required.

TLPORT-3

Message TLPORT-3-ALLOCFAIL: Heap Memory allocation failed: [chars]

Explanation TL Port Manager is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Message TLPORT-3-FC2ERROR: [chars]

Explanation TL Port Manager encountered an FC2 error. [chars] specifies the context where the error occurred.

Recommended Action No action is required.

Message TLPORT-3-GENERROR: [chars]

Explanation TL Port Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.

Recommended Action No action is required.

Message TLPORT-3-MTSERROR: [chars]

Explanation TL Port Manager encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action No action is required.

Message TLPORT-3-PSSERROR: [chars]

Explanation TL Port Manager encountered a PSS error. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

TLPORT-4

Message TLPORT-4-TLPM_ALPA_CACHE_FULL: Translation Port ALPA cache is full. Some new entries may not be cached

Explanation TL Port cache is currently fully populated with active entries. Hence, there is no available cache space to be assigned any newly created alpa entry on a TL Port. This is an informational message.

Recommended Action No action is required.

TLPORT-6

Message TLPORT-6-MGRCREATED: Translation Port Manager created.

Explanation TL Port Manager was created successfully and is up and running. This is an informational message.

Recommended Action No action is required.

Message TLPORT-6-MGREXIT: Translation Port Manager shutting down gracefully.

Explanation TL Port Manager is shutting down gracefully. This is an informational message.

Recommended Action No action is required.

Message TLPORT-6-PORTDOWN: Translation Port [chars] DOWN.

Explanation A port configured as TL Port is DOWN and out of operation. [chars] is the interface-id string that identifies the TL Port. This is an informational message.

Recommended Action No action is required.

Message TLPORT-6-PORTUP: Translation Port [chars] UP.

Explanation A port configured as TL Port is UP and operational. [chars] is the interface-id string that identifies the TL Port. This is an informational message.

Recommended Action No action is required.

TPC Messages

This section contains the TPC messages.

TPC-SLOT#-5

Message TPC-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN:[dec] VT pWWN:[chars] DPP died

Explanation The DPP associated with the Virtual Target has crashed

Recommended Action No action is required.

Message TPC-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars] VT Activate failed

Explanation The activate step for a Virtual Target has failed

Recommended Action No action is required.

Message TPC-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN:[dec] VT pWWN :[chars] VT and NPort creation FAILED !!!

Explanation The Virtual Target and nport creation failed

Recommended Action No action is required.

Message TPC-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target : [chars] Deleted

Explanation The Virtual Target in the associated VSAN is being destroyed

Recommended Action No action is required.

Message TPC-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars] VSAN down

Explanation The VSAN where the Virtual Target is configured is down

Recommended Action No action is required.

TTYD Messages

This section contains the TTYD messages.

TTYD-2

Message TTYD-2-TTYD_ERROR: TTYD Error [chars]

Explanation Critical TTY daemon error.

Recommended Action No action is required.

Message TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars]

Explanation TTY daemon message error.

Recommended Action No action is required.

Message TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars]

Explanation TTY daemon Debug Facility failed.

Recommended Action No action is required.

TTYD-3

Message TTYD-3-TTYD_MISC_ERROR: Error [chars] with error [chars]([hex])

Explanation TTY daemon errors.

Recommended Action No action is required.

TTYD-6

Message TTYD-6-TTYD_MISC: TTYD [chars]

Explanation The tty daemon miscellaneous message.

Recommended Action No action is required.

Message TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars]

Explanation Failed to store configuration for TTY service.

Recommended Action No action is required.

TUNNEL Messages

This section contains the TUNNEL messages.

TUNNEL-2

Message TUNNEL-2-FEATURE_ENABLE_FAILED: failed to enable feature tunnel, reason [chars] ([hex])

Explanation Failed to enable feature tunnel, reason [char] ([int])

Recommended Action Check the failure reason and take appropriate action to fix the failure. if unable to fix, please capture “show tech-support tunnel”

Message TUNNEL-2-TM_F2_ONLY_VDC: Tunnel feature is not supported in F2 only VDC

Explanation Tunnel feature is not supported in F2 only VDC

Recommended Action Disable the Tunnel feature by the CLI “no feature tunnel”

TUNNEL-3

Message TUNNEL-3-HW_PROGRAMMING_FAILED: for [chars], reason [chars]

Explanation Hardware programming failed for tunnel [num] interface

Recommended Action Try 'shutdown' and a 'noshutdown' under tunnel interface submode after sometime. If still tunnel interface doesn't come up capture 'show tech-support tunnel to identify the issue

TUNNEL-4

Message TUNNEL-4-TM_DF_PROGRAMMING_FAILED: [chars] DF(dont fragment) programming failed! status [hex]

Explanation [chars] DF programming failed! status [int]

Recommended Action Capture “show tech-support tunnel” to identify why DF flag programing failed

Message TUNNEL-4-TM_DF_PROGRAMMING: Programming [chars] DF (dont fragment) df.sel [dec] df.val [dec]

Explanation Programming [chars] DF df.sel [int] df.val [int]

Recommended Action No action is required.

Message TUNNEL-4-TM_MTU_PROGRAMMING_FAILED: [chars] mtu [dec] programming failed! status [hex]

Explanation [chars] MTU [int] programming failed! status [int]

Recommended Action Capture show "tech-support tunnel" to identify why MTU programming as failed. Tunnel interface will used default MTU value.

Message TUNNEL-4-TM_MTU_PROGRAMMING: Programming [chars] mtu [dec]...

Explanation Programming [chars] mtu [int]

Recommended Action No action is required.

TUNNEL-5

Message TUNNEL-5-IF_CLEAR_COUNTER: Interface [chars] counters is cleared

Explanation Interface [char] counters is cleared

Recommended Action No action is required.

Message TUNNEL-5-IF_CREATED: Interface [chars] is created

Explanation Interface [char] is created

Recommended Action No action is required.

Message TUNNEL-5-IF_CREATE_FAILED: Interface [chars] creation failed due to [[hex]] [chars]

Explanation Interface [char] is creation failed due to [int] [char]

Recommended Action No action is required.

Message TUNNEL-5-IF_DELETED: Interface [chars] is deleted

Explanation Interface [char] is deleted

Recommended Action No action is required.

Message TUNNEL-5-IF_STATE_UPDATE: Interface [chars] is [chars] reason [chars]

Explanation Interface [char] is [char] reason [char]

Recommended Action No action is required.

Message TUNNEL-5-PPF_SESSION_FAILED: session id %llx type [chars] for [chars] failed error [hex] [chars]

Explanation Session id [int] type [char] for [char] failed error [int] [char]

Recommended Action No action is required.

Message TUNNEL-5-TM_DISABLED: Tunnel Disabled

Explanation Tunnel Service Disabled

Recommended Action No action is required.

Message TUNNEL-5-TM_ENABLED: Tunnel Enabled

Explanation Tunnel Service Enabled

Recommended Action No action is required.

TUNNEL-7

Message TUNNEL-7-TM_INFO: [chars]

Explanation Tunnel Service info

Recommended Action No action is required.

TUSCANY_APP Messages

This section contains the TUSCANY_APP messages.

TUSCANY_APP-SLOT#-2

Message TUSCANY_APP-SLOT#-2-TUSCANY_APP_EXITED: Tuscany driver application exited (syserr = [dec], errno = [dec])

Explanation Tuscany driver application exited

Recommended Action No action is required.