This chapter lists the system messages by facility. Within each facility, the messages are listed by severity levels 0 to 7: 0 is the highest severity level, and 7 is the lowest severity level. Each message is followed by an explanation and a recommended action.
This section contains the AAA messages.
Error Message AAA-1-AAA_SESSION_LIMIT_REJECT: aaa request rejected as maximum aaa sessions are in progress
Explanation Aaa request rejected as the limit for maximum concurrent aaa sessions is reached
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.
Error Message AAA-2-AAA_NVRAM_UPGRADE_FAILURE: upgrading of accounting log failed. [chars]
Explanation Upgrading of accounting log 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.
Error Message AAA-2-AAA_PROGRAM_EXIT: aaa daemon exiting: [chars]
Explanation Aaa 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.
Error Message AAA-3-AAA_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.
Error Message AAA-6-AAA_ACCOUNTING_MESSAGE: [chars]
Explanation Accounting Message
Recommended Action No action is required.
This section contains the AAM messages.
Error Message AAM-2-ELS_FC2_GL_SINDEX_LOOKUP_FAILED: Failed to lookup global port index for interface [[chars]]
Explanation Failed to lookup global port index for interface [chars]
Recommended Action No action is required.
Error Message AAM-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec] size [dec]
Explanation AAM 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.
Error Message AAM-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
Explanation AAM Process assertion failed in File:[chars], at line:[dec]
Recommended Action No action is required.
This section contains the ACLLOG messages.
Error Message ACLLOG-4-ACLLOG_MAXFLOW_REACHED: [chars]
Explanation Max flow reached in current interval: [chars]
Recommended Action No action is required.
Error Message ACLLOG-4-ACLLOG_THRESHOLD: [chars]
Explanation Threshold Reached for Flow: [chars]
Recommended Action No action is required.
Error Message ACLLOG-6-ACLLOG_FLOW_INTERVAL: [chars]
Explanation Flow info in current alert interval: [chars]
Recommended Action No action is required.
Error Message ACLLOG-6-ACLLOG_NEW_FLOW: [chars]
Explanation New Acllog Flow: [chars]
Recommended Action No action is required.
This section contains the ACLMGR messages.
Error Message ACLMGR-2-ACLMGR_L2_REDIRECTED_PORTS: Redirected port(s) are supported on L2 interface type.
Explanation Redirected port(s) are supported on L2 interface type.
Recommended Action No action is required.
Error Message ACLMGR-2-ACLMGR_NO_ERRDISABLED: [chars] event on interface [chars] ([hex]) allowed to succeed in spite of access-list failure
Explanation Although an access-list operation failed during a port event, the port event still finished successfully because errdisable is disallowed
Recommended Action No action is required.
Error Message ACLMGR-2-EXITING: Exit reason: [chars]
Explanation The ACLMGR service process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message ACLMGR-2-INITFAIL: ACLMGR Service Init failed: [chars]
Explanation ACLMGR Service initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message ACLMGR-2-MALLOC_ERROR: Size [dec] bytes
Explanation The ACLMGR service could not allocate memory.
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.
Error Message ACLMGR-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The ACLMGR service encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_ACL_OWNER_MISMATCH: The ACL [chars] deleted was in use by [chars]. Please check show running-config for more information.
Explanation ACL that was in use by another feature was deleted
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_COMMIT_FAIL: Commit failed: [chars]
Explanation The PPF commit failed
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_DB_LOCK_MSG: ACL database message, reason: [chars], session 0x%llx, type: [chars]
Explanation ACL PPF database lock acquire/release related message.
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_GSYNC_ERROR: Error occured during global sync of ACL runtime database to standby, reason: [chars] , [chars]
Explanation ACL snapshot to send the copy of runtime database to standby failed
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_PPF_ERROR: PPF error: [chars]
Explanation The PPF generated error
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The ACLMGR service has detected corruption in one of its persistent information database. The database would be recreated.
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_STAT_CONSOLIDATION_FAILURE: ACL statistic parsing or consolidation failed
Explanation A statistic update failed during the parsing or consolidation step; statistics may have been lost
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_VACL_REDIRECTION_DISABLED_REMOVAL: VACL redirection to interface [chars] ([hex]) disabled: the port has been removed
Explanation A VACL redirection to the port has been deactivated because the port has been removed
Recommended Action No action is required.
Error Message ACLMGR-3-ACLMGR_VERIFY_FAIL: Verify failed: [chars]
Explanation The PPF Verify failed
Recommended Action No action is required.
Error Message ACLMGR-3-MTSERROR: [chars]
Explanation ACLMGR Service encountered an MTS error. [chars] specifies the context where the error occured.
Recommended Action No action is required.
Error Message ACLMGR-4-ACLMGR_PPF_WARNING: PPF warning: [chars]
Explanation The PPF generated warning
Recommended Action No action is required.
Error Message ACLMGR-4-ACLMGR_VACL_REDIRECTION_DISABLED_PCM: VACL redirection to interface [chars] ([hex]) disabled: the port became a portchannel member
Explanation A VACL redirection to the port has been temporarily deactivated because it is now a member in a port channel
Recommended Action No action is required.
Error Message ACLMGR-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the ACLMGR service and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error Message ACLMGR-6-ACLMGR_PPF_NOTIF: PPF notification: [chars]
Explanation The PPF generated notification
Recommended Action No action is required.
Error Message ACLMGR-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The ACLMGR service on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Error Message ACLMGR-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The ACLMGR service became standby from active mode.
Recommended Action No action is required.
Error Message ACLMGR-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]
Explanation The ACLMGR service was unable to send heartbeat to the system manger
Recommended Action No action is required.
Error Message ACLMGR-6-SERVICE_UP: Initialized [chars]
Explanation The ACLMGR service is up and ready The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message ACLMGR-6-SRVEXIT: ACLMGR Service shutting down gracefully
Explanation ACLMGR Service is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message ACLMGR-6-SWITCHOVER: Switching Over to other Sup.
Explanation The ACLMGR service has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
This section contains the ACLQOS messages.
Error Message ACLQOS-SLOT#-0-ACLQOS_SPAN_EGRESS_RATE_LIMIT_MAX: Configuring span-egress rate limit failed. [chars]
Explanation Failed to configure span-egress rate limit. No free entry available in ERACL TCAM region.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_BUFFER_DRAIN_FAILURE: Failed to drain buffers while modifying network qos policy on unit:[dec] slice: [dec]!
Explanation Failed to drain buffers while modifying network qos policy.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_BURST_DETECT_FPGA_INCOMPATIBLE: Current FPGA image doesn't support microburst detection feature. Please upgrade IOFPGA epld image to version [dec].
Explanation Current FPGA image doesn't support microburst detection feature.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_BURST_DETECT_OVER_THRESHOLD: Interface [chars] queue [dec] queue-depth is over the configured burst threshold. Please check 'show queuing burst-detect detail' for more information.
Explanation Queue depth went above configured burst threshold.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_FAILED: ACLQOS failure: [chars]
Explanation ACLQOS operation failed in the aclqos client
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_INBAND_INTERFACE_FAILURE: Inband interface lif lookup failed ([chars])
Explanation Inband interface lif lookup failed
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_MALLOC_FAILED: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_OOTR: Tcam resource exhausted: [chars]
Explanation Tcam resources to program acls exhausted
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_QUEUE_LIMIT_IGNORED_ON_FEX: Queue-limit configuration is being allowed but will not be configured on any connected FEXes.
Explanation Queue-limit configuration is not supported on FEX.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_QUEUE_LIMIT_MAX: Queue limit is restricted to max available buffers([dec] bytes) on unit [dec].
Explanation Queue limit is restricted to the max available buffers on the unit.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_TCAM_CARVING_FAILURE: [chars] TCAM region carving crossed the allowed max limits. Please re-adjust the limits using "hardware access-list tcam region .." command and reload the linecard
Explanation [chars] Tcam is excessively provisioned
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_TCAM_REGION_CREATION_FAILURE: TCAM region creation failed for instance: [dec], Group ID: [dec], reason: [chars]
Explanation [chars] Tcam region is not properly configured
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_TCAM_TEMPLATE_FAILURE: TCAM template application has failed with reason: [chars]. Failing the module bring up
Explanation [chars] Tcam template is not properly applied
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-PPF_FAILED: Database failure: [chars]
Explanation Database operation failed in the aclqos client
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-3-ACLQOS_CC_INVALID: Invalid Congestion Control parameters: [chars]
Explanation Invalid Congestion Control parameters
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-3-ACLQOS_MCM_ERROR: MCM Message Inconsistent. Please collect MCM and ACLMgr Tech Support for all VDCs
Explanation MCM Message Inconsistent
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-3-ACLQOS_PAUSE_INVALID: Invalid Pause parameters: [chars]
Explanation Invalid Pause parameters
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-3-ACLQOS_QUEUING_ERROR: ACL/QoS queuing error: [chars]
Explanation Internal error in ACL/QoS queuing config
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_ANALYTICS_L4OP_UNSUPPORTED: Analytics TCAM doesnt support port-expansion or LOU allocation. Please modify ACL policy and re-apply
Explanation Analytics TCAM doesnt support port-expansion or LOU allocation. Please modify ACL policy and re-apply
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_ATOMIC_ERR: [chars]
Explanation Tcam will be overused, please turn off atomic update
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_BC_OVER_THRESHOLD: Bank Chaining enabled: Inst [dec]'s usage has reached its threshold
Explanation Tcam is almost full
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_FC_WARNING: Found stale FCoE entry in instance [dec]. VSAN: [dec], SID: [hex], DID: [hex], SI:[dec], SI_MASK:[dec], RW_VSAN: [dec], RW_VSAN_FLAG: [dec], RW_SID: [hex], RW_SID_FLAG: [dec], RW_DID: [hex]. RW_DID_FLAG: [dec] Cleaning it up.
Explanation Found stale FCoE entry in instance [dec]. VSAN: [dec], SID: 0x[hex], DID: 0x[hex], SI:[dec], SI_MASK:[dec], RW_VSAN:[dec], RW_VSAN_FLAG: [dec], RW_SID: 0x[hex], RW_SID_FLAG:[dec], RW_DID: 0x[hex]. RW_DID_FLAG: [dec] Cleaning it up.
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_MATCH_ALL_MERGE_UPDATE: Warning (match_all merging): [chars]
Explanation Warning (match_all merging)
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_OPENFLOW_DFLT_MISS_UNSUPP: Openflow default-miss action needs [chars] TCAM region to be configured in double-wide mode
Explanation Openflow default-miss action specified without configuring TCAM in double-wide mode
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_OVER_THRESHOLD: Inst [dec] Tcam [dec] Bank [dec]'s ([chars]) usage has reached its threshold
Explanation Tcam is almost full
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_QUEUING_COS2Q_INVALID: ACL/QoS invalid queuing policy because of cos map change: [chars] queue [chars], interface [chars]
Explanation Attemped to configure an invalid queuing policy
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_QUEUING_INVALID: ACL/QoS invalid queuing policy: [chars]
Explanation Attemped to configure an invalid queuing policy
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_TAP_AGG_REDIR_INVALID: Redirect action invalid without Tap aggregation enable, interface [chars]
Explanation Redirect action specified without Tap aggregation enable
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_UNDER_THRESHOLD: Tcam [dec] Bank [dec]'s usage is below the threshold now
Explanation Tcam's usage is below the threshold
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-4-ACLQOS_WARNING: ACLQOS Warning: [chars]
Explanation ACLQOS Warnings
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-5-ACLQOS_DISRUPTIVE_IPv6_UPDATE: Disruptive update of IPv6 compression entries
Explanation Disruptive IPv6 compression entries update
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-5-ACLQOS_MAC_SA_DA_OVERLAP_LOG: MAC [chars] overlap for address(mask) [hex][hex]([hex][hex]) with [hex][hex]([hex][hex]) for hardware instance [dec]
Explanation MAC SA/DA overlaps with already configured value. Overlapping MAC SA/DA matching is not supported on this platform
Recommended Action No action is required.
Error Message ACLQOS-SLOT#-5-ACLQOS_NON_ATOMIC: Non atomic ACL/QoS policy update done for [chars]
Explanation Non atomic ACL/QoS policy update was done
Recommended Action No DDTS.
This section contains the ACLTCAM messages.
Error Message ACLTCAM-2-ACL_TCAM_ADJ_EXHAUSTED: ACLTCAM failed to program route for VSAN: [dec], SID: [chars] DID: [chars], error: [chars].
Explanation ACLTCAM process experienced a failure while programming route for VSAN [dec] SID [chars] DID [chars] due to resource exhaustion. [chars] is the error code.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_ALMOST_FULL: TCAM close to FULL. [chars] TCAM Usage ([dec]/[dec]) exceeded [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_READ_FROM_DRIVER_FAILED: [chars] [dec], Error: [hex].
Explanation Unable to read configuration from forwarding engine ASIC driver. [chars] [dec], Error: 0x[hex].
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_WRITE_TO_DRIVER_FAILED: [chars] [dec], Error: [hex].
Explanation Unable to write configuration to forwarding engine ASIC driver. [chars] [dec], Error: 0x[hex].
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_FLOW_STATS_READ_FAILED: Hardware flow stats read failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).
Explanation Hardware flow stats read failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_DATABASE: Database found inconsistent.
Explanation Database found inconsistent.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_TCAM_CONTENTS: TCAM contents found inconsistent.
Explanation TCAM contents are found inconsistent.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_INIT_FAILED: Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM.
Explanation Initialization failed for forwarding engine ASIC [dec], in [chars] TCAM.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_INIT_REGIONS_FAILED: Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM, [chars] Region.
Explanation Initialization of regions failed for forwarding engine ASIC [dec], in [chars] TCAM, for [chars] Region.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_MALLOC_FAILURE: Memory allocation failed for size [dec].
Explanation Memory allocation is failed for size [dec] bytes.
Recommended Action Restart the process.
Error Message ACLTCAM-2-ACL_TCAM_MTS_FAILURE: MTS operation failed: [chars].
Explanation MTS operation failed. [chars] is the reason.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_MTS_Q_FULL: MTS queue for SAP [dec] is full
Explanation MTS queue for SAP [dec] is full
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_MTS_REGISTRATION_FAILED: MTS registration failed for opCode: [dec].
Explanation MTS registration failed for opCode: [dec].
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_NO_ROUTE: ACLTCAM failed to get route for VSAN: [dec], Rewrite: [chars] DID: [chars] DID MASK: [chars], error: [hex].
Explanation ACLTCAM process experienced a failure while getting route for VSAN [dec] Rewrite [chars] DID [chars] DID Mask [chars]. [hex] is the error code.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_NO_TCAM_LEFT: ACLTCAM resource exhausted for interface : [chars]
Explanation ACLTCAM hardware resource is completely used.
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_READ_FAILED: [chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).
Explanation [chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_READ_INVALID: Invalid([chars], value: [dec]) TCAM entry read from hardware TCAM (FWD-Engine: [dec], [chars] TCAM, Address: [dec]), Ignoring this entry.
Explanation Invalid([chars], value: [dec]) TCAM entry from hardware TCAM(FWD-Engine: [dec], [chars] TCAM, Address: [dec]) Ignoring this entry
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: [chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).
Explanation [chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).
Recommended Action No action is required.
Error Message ACLTCAM-2-ACL_TCAM_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].
Explanation Failed to do PSS operation [chars]. [hex] is the reason.
Recommended Action No action is required.
Error Message ACLTCAM-2-PSS_OPEN_FAILED: PSS open failed - [hex].
Explanation Persistent database handle could not obtained for ACLTCAM. [hex] is the error.
Recommended Action No action is required.
Error Message ACLTCAM-2-RECONS_FAILED: Reconstruction of TCAM contents failed during upgrade - [hex].
Explanation During non-disruptive upgrade, the ACLTCAM contents are not properly reconstructed. [hex] is the error.
Recommended Action No action is required.
Error Message ACLTCAM-3-ACL_TCAM_MTS_Q_LEAK: Possible MTS buffer leak for SAP [dec]
Explanation Possible MTS buffer leak for SAP [dec]
Recommended Action No action is required.
Error Message ACLTCAM-3-REGISTER_FAILED: Could not register to MTS opcode [chars] - error [hex].
Explanation ACLTCAM process could not register to the notifications mentioned by [chars]. [hex] is the error.
Recommended Action No action is required.
Error Message ACLTCAM-4-ACL_TCAM_BELOW_THRESHOLD: [chars] TCAM usage ([dec]/[dec]) fell below [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] fell below [dec] percent on fwd-engine [dec], [chars]
Recommended Action No action is required.
Error Message ACLTCAM-4-ACL_TCAM_BEYOND_THRESHOLD: [chars] TCAM usage ([dec]/[dec]) exceeded [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]
Recommended Action No action is required.
Error Message ACLTCAM-4-ACL_TCAM_FLOW_COUNTER_INVALIDATED: Flow counter for flow: vsan: [dec], sid: [hex], did: [hex] with statistics: frames = %llu & bytes = %llu was invalidated due to: [chars]
Explanation ACLTCAM process invalidated the flow counter for flow VSAN [dec] SID [hex] DID [hex] with collected stats of [dec] frames and [dev] bytes was invalidated because of reason [[chars]].
Recommended Action No action is required.
Error Message ACLTCAM-4-ACL_TCAM_FLOW_COUNTER_VALIDATED: Flow counter for flow: vsan: [dec], sid: [hex], did: [hex] is now valid
Explanation ACLTCAM process validated the flow counter for flow VSAN [dec] SID [hex] DID [hex].
Recommended Action No action is required.
Error Message ACLTCAM-4-ACL_TCAM_MTS_Q_HIGH: MTS queue for SAP [dec] is close to full
Explanation MTS queue for SAP [dec] is close to full
Recommended Action No action is required.
Error Message ACLTCAM-6-ACL_TCAM_STATUS: Status: [chars].
Explanation ACLTCAM status is reported as: [chars].
Recommended Action No action is required.
This section contains the ACL messages.
Error Message ACL-2-ACL_HA_FAILURE: Failed to do high availability operation: [chars].
Explanation Failed to do high availability operation. [chars] is the reason.
Recommended Action No action is required.
Error Message ACL-2-ACL_INIT_FAILED: Initialization failed for ACL: [chars], reason: [hex].
Explanation Initialization failed for ACL due to [chars], reason: [hex].
Recommended Action No action is required.
Error Message ACL-2-ACL_LINECARD_STATUS: Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].
Explanation Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].
Recommended Action No action is required.
Error Message ACL-2-ACL_MTS_FAILURE: Failed to do MTS operation: [chars].
Explanation Failed to do MTS operation. [chars] is the reason.
Recommended Action No action is required.
Error Message ACL-2-ACL_MTS_Q_FULL: MTS queue for SAP [dec] is full
Explanation MTS queue for SAP [dec] is full
Recommended Action No action is required.
Error Message ACL-2-ACL_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec].
Explanation MTS options setting to [hex] failed for opCode: [dec].
Recommended Action No action is required.
Error Message ACL-2-ACL_PENDING_MSG_ARR_FULL: ACL Upgrade Pending Messages Array is Full with [dec] messages. Failing the MTS message with Opc: [dec], RR_TOKEN: [hex]
Explanation ACL Upgrade Pending Messages Array is Full with [dec] messages. Failing the MTS message with Opc: [dec], RR_TOKEN: [hex]
Recommended Action No action is required.
Error Message ACL-2-ACL_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].
Explanation Failed to do PSS operation [chars]. [hex] is the reason.
Recommended Action No action is required.
Error Message ACL-2-ACL_PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.
Recommended Action No action is required.
Error Message ACL-2-ACL_RUNTIME_FAILURE: [chars] [dec], Error: [hex]
Explanation ACL runtime failure is reported as [chars] [dec], reason: [hex].
Recommended Action No action is required.
Error Message ACL-2-ACL_TCAM_FAILURE: Failed to do TCAM operation: [chars].
Explanation Failed to do TCAM operation. [chars] is the reason.
Recommended Action No action is required.
Error Message ACL-3-ACL_MTS_Q_LEAK: Possible MTS buffer leak for SAP [dec]
Explanation Possible MTS buffer leak for SAP [dec]
Recommended Action No action is required.
Error Message ACL-4-ACL_MTS_Q_HIGH: MTS queue for SAP [dec] is close to full
Explanation MTS queue for SAP [dec] is close to full
Recommended Action No action is required.
Error Message ACL-4-ACL_WARNING: [chars] [dec]
Explanation ACL warning messages is reported as [chars] [dec].
Recommended Action No action is required.
Error Message ACL-5-ACL_ADJ_SHARING_STATUS: Successfully completed "[chars]" on Generation 2 linecards.
Explanation Successfully completed the command \[chars]\ on Generation 2 linecards.
Recommended Action No action is required.
Error Message ACL-6-ACL_DIAG_EVENT_STATUS: [chars] [hex].
Explanation ACL system health management event status is reported as [chars] [hex].
Recommended Action No action is required.
Error Message ACL-6-ACL_E_PORT_EVENT_STATUS: [chars] [chars].
Explanation ACL xEport event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_FCC_EVENT_STATUS: [chars] [chars].
Explanation ACL FCC event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_LINECARD_EVENT_STATUS: [chars] [hex].
Explanation ACL linecard event status is reported as [chars] [dec].
Recommended Action No action is required.
Error Message ACL-6-ACL_MCAST_EVENT_STATUS: [chars] [chars].
Explanation ACL multicast event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_NX_PORT_EVENT_STATUS: [chars] [chars].
Explanation ACL Nx Port event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_PORT_MODE_EVENT_STATUS: [chars] [chars].
Explanation ACL portmode event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_RUNTIME_STATUS: [chars] [dec]
Explanation ACL runtime status is reported as [chars] [dec].
Recommended Action No action is required.
Error Message ACL-6-ACL_SPAN_DEST_CONFIG_STATUS: [chars] [chars].
Explanation ACL SPAN destination config event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_SPAN_SRC_CONFIG_STATUS: [chars] [chars].
Explanation ACL SPAN source config event status is reported as [chars] [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_STATUS: ACL Status: [chars].
Explanation ACL status is reported as [chars].
Recommended Action No action is required.
Error Message ACL-6-ACL_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].
Explanation ACL update SSRAM for QoS event status is reported as [chars] [chars].
Recommended Action No action is required.
This section contains the AMM messages.
Error Message AMM-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation AMM failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message AMM-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation AMM failed to initialize timer library. This is a fatal error.
Recommended Action No action is required.
Error Message AMM-SLOT#-2-AMM_MEM_ALLOC: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No action is required.
Error Message AMM-SLOT#-2-AMM_RECOVERY_ERROR: Error in Recovery: [chars]
Explanation AMM failed to recover after a re-start. This is a fatal error.
Recommended Action No action is required.
Error Message AMM-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation AMM has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
This section contains the ASCII-CFG messages.
Error Message ASCII-CFG-2-ACFG_CONFIGURATION_APPLY_ERROR: Error encountered while Ascii configuration was being applied. Please use "show startup-config log" to view details
Explanation At least one command failed while Ascii configuration was being applied
Recommended Action No action is required.
Error Message ASCII-CFG-2-ACFG_LIB_INVOKE_ERR: Ascii config library invocation error: [chars]
Explanation Error encountered while library function was being invoked to display Ascii configuration
Recommended Action No action is required.
Error Message ASCII-CFG-2-ACFG_OPER_FAIL: Operation failed because of [chars]
Explanation Operation failed
Recommended Action No action is required.
Error Message ASCII-CFG-2-ACFG_ROLLBACK_FAILED: Rollback to checkpoint [chars] Failed, Going to undo the changes (atomic option)
Explanation Rollback operation failed for atomic option
Recommended Action No action is required.
Error Message ASCII-CFG-2-ACFG_ROLLBACK_UNDO_FAILED: Undo failed for atomic Rollback, Please correct the error manually and retry rollback
Explanation Undoing the rollback changes (for atomic behavior) Failed
Recommended Action No action is required.
Error Message ASCII-CFG-2-ACFG_SYSLOG_INIT_FAILED: Ascii config Syslog Init Error
Explanation Error encountered while Initializing Syslog for Ascii Config
Recommended Action No action is required.
Error Message ASCII-CFG-2-CONFIG_REPLAY_STATUS: [chars] Replay [chars].
Explanation Bootstrap or Ascii Configuration Replay Status info.
Recommended Action No action is required.
Error Message ASCII-CFG-2-CONF_CONTROL: [chars]
Explanation Configuration restore control info.
Recommended Action No action is required.
Error Message ASCII-CFG-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version
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.
Error Message ASCII-CFG-2-SYSERR_ACFG_NO_STARTUP_CFG_FILE: [chars]
Explanation Startup configuration file is empty
Recommended Action No action is required.
Error Message ASCII-CFG-3-ACFG_MTSERROR: [chars]
Explanation Ascii-cfg-server (rollback process) encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CLEAR_DATABASE: cleared all the configuration checkpoints
Explanation Cleared all the configuration checkpoints
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CREATED: Created configuration checkpoint [chars]
Explanation Created configuration checkpoint
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_DELETED: Deleted configuration checkpoint [chars]
Explanation Deleted configuration checkpoint
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_MAX_CHECKPOINTS: Maximum no of checpoints reached, Removing the oldest checkpoint
Explanation Maximum no.of checkpoints reached, removing the oldest checkpoint
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_ROLLBACK_ATOMIC: Performing configuration rollback to checkpoint [chars] (with atomic option)
Explanation Performing configuration rollback with atomic option
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_ROLLBACK_BEST: Performing configuration rollback to checkpoint [chars] (with best-effort option)
Explanation Performing configuration rollback with best-effort option
Recommended Action No action is required.
Error Message ASCII-CFG-6-ACFG_ROLLBACK_FIRST_ERR: Performing configuration rollback to checkpoint [chars] (with stop-at-first failure option)
Explanation Performing configuration rollback with stop-at-first-failure option
Recommended Action No action is required.
Error Message ASCII-CFG-6-INFORMATION: [chars]
Explanation An event happend that affects Acfg-Rollback. [chars] indicates the event
Recommended Action No action is required.
Error Message ASCII-CFG-6-PSS_ERR: [chars]
Explanation An error occurred during an Acfg PSS operation. [chars] indicates the PSS operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
This section contains the ASSOC_MGR messages.
Error Message ASSOC_MGR-0-EMERGENCY_MSG: [chars]
Explanation Association Manager Emergency Message
Recommended Action Please file the bug for Association Manager Component thro' CDETS
Error Message ASSOC_MGR-1-ALERT_MSG: [chars]
Explanation Association Manager Alert Message
Recommended Action Association Manager Internal Operation Alert
Error Message ASSOC_MGR-2-CRITICAL_MSG: [chars]
Explanation Association Manager Critical Message
Recommended Action No action is required.
Error Message ASSOC_MGR-3-ERROR_MSG: [chars]
Explanation Association Manager Error Message
Recommended Action No action is required.
Error Message ASSOC_MGR-4-WARN_MSG: [chars]
Explanation Association Manager Warning Message
Recommended Action No action is required.
Error Message ASSOC_MGR-5-NOTIF_MSG: [chars]
Explanation Association Manager Notification Message
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_ACTIVATED: Association Activated for vlan id:[dec] <--> vsan id:[dec]
Explanation Association Activated
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_CREATED: Association Created for vlan id:[dec] <--> vsan id:[dec]
Explanation Association Created
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_DEACTIVATED: Association Deactivated for vlan id: [dec] <--> vsan id: [dec]
Explanation Association Deactivated
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_DELETED: Association Deleted for vlan id: [dec] <--> vsan id: [dec]
Explanation Association Deleted
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_MGR_STATEFULL_RESTART: Association Manager Statefull Restart
Explanation Association Manager Stateful Restart
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_MGR_STATELESS_RESTART: Association Manager Stateless Restart
Explanation Association Manager Stateless Restart
Recommended Action No action is required.
Error Message ASSOC_MGR-6-ASSOC_OPER_STATUS_CHG: Association status for vlan id: [dec] <--> vsan id: [dec] changed from [chars] to [chars]
Explanation Association Operational State Change
Recommended Action No action is required.
Error Message ASSOC_MGR-6-INFO_MSG: [chars]
Explanation ASSOC Manager Informational Message
Recommended Action No action is required.
Error Message ASSOC_MGR-7-DEBUG_MSG: [chars]
Explanation Association Manager Debug Message
Recommended Action No action is required.
This section contains the BFDC messages.
Error Message BFDC-SLOT#-2-BFDC_GENERAL_FAILURE: General failure. [chars]
Explanation General failure. This is a critical failure
Recommended Action No DDTS.
Error Message BFDC-SLOT#-2-BFDC_MALLOC_FAILED: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No DDTS.
Error Message BFDC-SLOT#-2-BFDC_MTS_FAILURE: MTS failure. [chars]
Explanation MTS related failure. This is a critical failure
Recommended Action No DDTS.
This section contains the BFD messages.
Error Message BFD-3-REACHED_CAPACITY_LIMIT: BFD session [chars] creation on interface [chars] failed due to capacity limit [dec]
Explanation BFD session [chars] creation on interface [chars] failed due to current capacity limit [dec]
Recommended Action Please remove current bfd sessions to make room for new ones
Error Message BFD-3-SESSION_ACL_INSTALL_GAVE_UP: BFD session [chars] installation failed due to ACL installation failure interface [chars]
Explanation BFD session [chars] installation failed due to ACL installation failure interface [chars
Recommended Action Maximum acl install retries exceeded. Please to free up acl resources
Error Message BFD-3-SESSION_ACL_REMOVE_GAVE_UP: BFD session [chars] removal failed due to ACL removal failure interface [chars]
Explanation BFD session [chars] removal failed due to ACL removal failure interface [chars
Recommended Action Maximum acl removal retries exceeded. Please manually remove bfd sessions
Error Message BFD-3-SESSION_CREATE_FAIL: Failed to create BFD session to neighbor [chars] over intertface [chars]. Reason [chars]
Explanation Failed to create BFD session to neighbor [chars] over intertface [chars] Reason [chars]
Recommended Action SYSLOGDPC_NO_ACTION
Error Message BFD-4-INVALID_NBR: Attempt to BFD session failed for application [chars].
Explanation Attempt to BFD session failed for application [chars].
Recommended Action No action is required.
Error Message BFD-4-SESSION_DELETE_FAIL: Attempt to delete BFD session for neighbor [chars] failed: Reason [chars] ([hex]).
Explanation Attempt to delete BFD session for neighbor [chars] failed: Reason [chars] (0x[hex]).
Recommended Action No action is required.
Error Message BFD-5-BFD_DISABLED: BFD Disabled
Explanation BFD Service Disabled
Recommended Action No action is required.
Error Message BFD-5-BFD_ENABLED: BFD Enabled
Explanation BFD Service enabled
Recommended Action No action is required.
Error Message BFD-5-SESSION_CREATED: BFD session to neighbor [chars] on interface [chars] has been created
Explanation BFD session to neighbor [chars] on interface [chars]
Recommended Action No action is required.
Error Message BFD-5-SESSION_LOCAL_PARAMS_CHANGE: Local parameter of BFD session [hex] has changed [chars]
Explanation Local parameter of BFD session 0x[hex] has changed [chars]
Recommended Action No action is required.
Error Message BFD-5-SESSION_MOVED: BFD session [hex]: [chars]
Explanation BFD session 0x[hex]: [chars]
Recommended Action No action is required.
Error Message BFD-5-SESSION_NO_RESOURCES: No resource for session to neighbor [chars] on interface [chars]
Explanation The BFD session can not be created or modified due to lack of resources. No resources for session to neighbor [chars]
Recommended Action Remove other BFD sessions to free resources for this session
Error Message BFD-5-SESSION_REMOVED: BFD session to neighbor [chars] on interface [chars] has been removed
Explanation BFD session to neighbor [chars] on interface [chars]
Recommended Action No action is required.
Error Message BFD-5-SESSION_STATE_DOWN: BFD session [chars] to neighbor [chars] on interface [chars] has gone down. Reason: [chars].
Explanation BFD session [chars] to neighbor [chars] on interface [chars] has gone down. Reason: [chars]. This may be as a result of the forwarding path being down.
Recommended Action No action is required.
Error Message BFD-5-SESSION_STATE_UP: BFD session [chars] to neighbor [chars] on interface [chars] is up.
Explanation BFD session [chars] to neighbor [chars] on interface [chars] is up.
Recommended Action No action is required.
Error Message BFD-6-SESSION_ACL_INSTALL_FAILED: BFD session [chars] failed due to missing ACL resources for interface [chars]
Explanation BFD session [chars] failed due to missing ACL resources for interface [chars]
Recommended Action No action is required.
Error Message BFD-6-SESSION_ACL_REMOVE_FAILED: BFD session [chars] removal failed due to missing ACL resources for interface [chars]
Explanation BFD session [chars] removal failed due to missing ACL resources for interface [chars]
Recommended Action No action is required.
Error Message BFD-6-SESSION_ACTIVE_PARAMS_CHANGE: Local parameter of BFD session [hex] has changed [chars]
Explanation Local parameter of BFD session 0x[hex] has changed [chars]
Recommended Action No action is required.
This section contains the BIOS_DAEMON messages.
Error Message BIOS_DAEMON-2-BIOS_DAEMON_FLASH_WARNING: Flash chip not supported by running image. Skipping bios upgrade.
Explanation BIOS CHIP NOT SUPPORTED
Recommended Action No action is required.
Error Message BIOS_DAEMON-2-BIOS_DAEMON_PRI_BOOT_FAIL: System booted from Alternate BIOS Flash
Explanation Boot from Alternate
Recommended Action SYSLOGDOC_NOACTION
Error Message BIOS_DAEMON-2-BIOS_DAEMON_SUP_ERROR: BIOS Sector ([dec]) is write protected
Explanation BIOS WRITE PROTECTED
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.
Error Message BIOS_DAEMON-5-BIOS_DAEMON_PRI_BOOT: System booted from Primary BIOS Flash
Explanation Boot from Primary
Recommended Action SYSLOGDOC_NOACTION
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_ERROR: BIOS Sector ([dec]) is write protected
Explanation BIOS WRITE PROTECTED
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.
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_PRI_BOOT_FAIL: System booted from Alternate BIOS Flash
Explanation Boot from Alternate
Recommended Action SYSLOGDOC_NOACTION
Error Message BIOS_DAEMON-SLOT#-5-BIOS_DAEMON_LC_PRI_BOOT: System booted from Primary BIOS Flash
Explanation Boot from Primary
Recommended Action SYSLOGDOC_NOACTION
This section contains the BLOGGERD messages.
Error Message BLOGGERD-2-BLOGGERD_SYSLOG_TRANSFER_ERROR_DISABLED: [chars]
Explanation Blogger Log Transfer has been error disabled
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_INVALID_VDC: At [chars]([dec]) Invalid VDC [dec]
Explanation Invalid VDC ID
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_LOG_DUMP_THROTTLED: VDC [dec] Comp: [chars] Buf_uuid: [dec] Buf_inst: [dec] sap: [chars]. Please collect 'show system internal sdwrap buffers sap [dec] detailed' from module [dec] Wiki: https://and-sw-web.cisco.com/twiki/bin/view/Sw/LogDumpThrottle
Explanation Log Dump Throttled
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_MOVE_LOGS_SCRIPT_NOT_FOUND: At [chars]([dec]) Move Logs Script Not Found at [chars]
Explanation Move Log Script Not Found
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_PATH_NOT_FOUND: At [chars]([dec]) Path [chars] NOT found
Explanation Required Path Not Found
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_CONFIG_PULL_FAILED: At [chars]([dec]) Config Pull Failed. Returned [hex]([chars])
Explanation Blogger Config Pull Failed
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_MTS_BIND_FAILED: MTS Bind Failed
Explanation MTS Bind Failed
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_MTS_UNDROP: MTS is not dropped by Node [hex] SAP [dec]
Explanation MTS not dropped
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_PSS_FAILURE: At [chars]([dec]) Internal PSS Error. Returned: [hex]([chars])
Explanation PSS Operation Failed
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_SDWRAP_INIT_FAILED: At [chars]([dec]) sdwrap initialization failed. Returned: [hex]([chars])
Explanation SDWrap Debug Init failed
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-3-BLOGGERD_SYSLOG_THREAD_CREATE_FAILED: At [chars]([dec]) Thread Creation Failed [hex] errno: [dec]([chars])
Explanation Thread Creation Failed
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-4-BLOGGERD_FLOW_CONTROL_ENABLED: Temporarily suspending BloggerD Log Transfer from Modules due to lack of space (available: %ld MB) on Active SUP
Explanation Flow Control Enabled. Transfer from Modules temporarily suspended
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-4-BLOGGERD_FLOW_CONTROL_RESET: Revoking temporary Log Transfer Suspension from Modules. Space available now: %ld MB
Explanation Flow Control Reset. Transfer from Modules re-enabled
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
Error Message BLOGGERD-6-BLOGGERD_INFO: [chars]
Explanation Info
Recommended Action Please collect BloggerD tech support using 'show tech bloggerd-all'
This section contains the BOOTUP_TEST messages.
Error Message BOOTUP_TEST-2-EOBC_FAIL: Module [dec] has failed test [chars] on EOBC due to error [chars]
Explanation Online diagnostics EOBC test has failed
Recommended Action No action is required.
Error Message BOOTUP_TEST-2-EOBC_SKIP: Module [dec] has failed test [chars] on EOBC due to error [chars]
Explanation Online diagnostics ManagementPort test has failed
Recommended Action No action is required.
Error Message BOOTUP_TEST-2-MGMT_PORT_FAIL: Module [dec] has failed test [chars] on Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test has failed
Recommended Action No action is required.
Error Message BOOTUP_TEST-2-MGMT_PORT_SKIP: Module [dec] has skipped test [chars] on Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test is skipped
Recommended Action No action is required.
This section contains the BOOTVAR messages.
Error Message BOOTVAR-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate memory.
Recommended Action Check if the system is low on memory, if so reset the switch.
Error Message BOOTVAR-2-AUTOCOPY_FAILED: Autocopy of file [chars] to standby failed. [chars] (Error-id: [hex])
Explanation The image deemed to be copied to standby via the auto-copy feature failed.
Recommended Action Check error id for specified reason.
Error Message BOOTVAR-2-AUTOSYNC_FAILED: Image autosync failed. Reason: [chars] ([hex])
Explanation Image synchronization failed.
Recommended Action Check that there is enough space on the flash, as well as system high availability status.
Error Message BOOTVAR-2-CONFIG_ERROR: Failed to update boot configuration
Explanation An error has occurred during the update of the boot configuration files
Recommended Action Check that there is enough space on the flash, show boot to check the configured image names, show loader internal configuration to compare them with the current bootloader configuration, if they are not coherent do write erase and retry to save the configuration.
Error Message BOOTVAR-2-IMAGE_NOT_COMPATIBLE: Warning: image [chars] is not compatible with the current platform in SUP [dec]
Explanation The input image name is not compatible with the current platform.
Recommended Action Make sure a right image is specified before reboot.
Error Message BOOTVAR-3-AUTOCOPY_FAILED_STANDBY_FULL: Autocopy of file [chars] to standby failed due to not enough disk space on standby
Explanation There is not enough disk space on the standby for the file to be copied.
Recommended Action Clear space on the standby disk.
Error Message BOOTVAR-3-INIT_FAILED: Initialization failed: Component [chars]
Explanation The service failed to start The failure occurs during initialization of the component [chars].
Recommended Action Show processes to check the status of the other processes, pay attention to the specified component.
Error Message BOOTVAR-3-LOAD_VERIFY_LIB_FAILED: Fetching library [chars] failed, reason=[chars]
Explanation Failed to load bootvar specified verification library.
Recommended Action No action is required.
Error Message BOOTVAR-3-MODULE_LOCK_FAIL: Unable to get module lock, please don't reload
Explanation Unable to acquire modlock to prevent user to reload during auto-sync.
Recommended Action No action is required.
Error Message BOOTVAR-3-NEIGHBOR_REJECT_AUTOCOPY: auto-copy failed - not supported by neighbor supervisor.
Explanation Standby supervisor does not support auto-copy, thus failed.
Recommended Action No action is required.
Error Message BOOTVAR-3-VERIFY_FAILED: Image [chars] for bootvar [chars] verification failed, reason=[chars]
Explanation The image set for this bootvar has failed the verification process, this is just a warning.
Recommended Action Check reason to determine actions.
Error Message BOOTVAR-5-AUTOCOPY_SUCCEED: auto-copy of file [chars] to standby supervisor succeed
Explanation Auto copy of the file succeed, image integrity verified by standby.
Recommended Action No action is required.
Error Message BOOTVAR-5-AUTOCOPY_VERIFY_SEND_FAILED: Unable to ask standby to verify file [chars], error = [hex]
Explanation Upon copied the image to standby, failed to send message to ask standby to verify integrity.
Recommended Action Turn auto-copy off and back on.
Error Message BOOTVAR-5-AUTOSYNC_DONE: Image autosync done
Explanation The image synchronization done successfully.
Recommended Action No action is required.
Error Message BOOTVAR-5-AUTOSYNC_REBOOT: Rebooting standby after successful autosync
Explanation Image autosync has been successful, resetting the standby supervisor to load the new image.
Recommended Action Check that the standby sup reloads correctly.
Error Message BOOTVAR-5-AUTOSYNC_START: Starting image autosync. Please wait until completion...
Explanation The standby-sup has requested the sync of the current image.
Recommended Action No action is required.
Error Message BOOTVAR-5-IMAGE_NOTEXISTS_ACTIVE: Warning: image [chars] doesn't exist on active sup
Explanation The input image name doesn't exist on the active supervisor.
Recommended Action Check whether the input image name you entered exists and make sure that you have the image on the flash before reboot.
Error Message BOOTVAR-5-IMAGE_NOTEXISTS: Warning: image [chars] doesn't exist on sup[dec]
Explanation The input image name doesn't exist on the specified supervisor.
Recommended Action Check whether the input image name you entered exists and make sure that you have the image on the flash before reboot.
Error Message BOOTVAR-5-INVALID_NXOS_IMAGE: Warning: This is not a valid NXOS image
Explanation This is not a valid NXOS image
Recommended Action Check whether the input image name you entered is valid NXOS image
Error Message BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor supervisor, starting...
Explanation Info log reporting standby's support of auto-copy. Auto-copy is being started.
Recommended Action No action is required.
Error Message BOOTVAR-6-ALREADY_IN_SYNC: Image already in sync
Explanation No need to update the image on the standby-sup.
Recommended Action No action is required.
Error Message BOOTVAR-6-AUTOCOPY_DID_NOT_START: Autocopy of file [chars] to standby did not start. [chars] (Error-id: [hex])
Explanation Autocopy of the file did not start as the remote copy location does not exist
Recommended Action No action is required.
Error Message BOOTVAR-6-CONFIG_UPDATED: Boot configuration updated
Explanation The boot-loader configuration files have been successfully updated.
Recommended Action No action is required.
Error Message BOOTVAR-6-STARTING: Boot configuration initialized
Explanation The service has successfully started.
Recommended Action No action is required.
This section contains the CALLHOME messages.
Error Message CALLHOME-2-EVENT: [chars]
Explanation Callhome event [chars] occurred.
Recommended Action If you have configured your email address to receive callhome notifications, please check your email for more details about this callhome event. If callhome was not enabled, please execute CLI commands relevant to the callhome event to get more information about the error
Error Message CALLHOME-2-PROGRAM_EXIT: callhome process ending: [chars]
Explanation Callhome process is exiting with reason [chars].
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.
Error Message CALLHOME-3-CALLHOME_CFS_MERGE_OPERATION_FAILED: [chars]
Explanation [chars1]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message CALLHOME-3-CALLHOME_CFS_OPERATION_FAILED: [chars] : [chars]
Explanation [chars1] [chars2]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message CALLHOME-3-CALLHOME_MAX_ALERT_MSG: [chars]
Explanation [chars]
Recommended Action Please check the reason for the generation of the callhome messages and rectify the problem
Error Message CALLHOME-3-EVENT_PROCESS_ERROR: error in processing callhome event [chars] reason:[chars]
Explanation Error in processing callhome event [chars] reason:[chars]
Recommended Action Please check your callhome configuration for proper configuration. Please check SMTP server address, email addresses for destination profiles and enable status of callhome. Use "show callhome" commands for displaying configuration.
Error Message CALLHOME-3-MESSAGE_SIZE_EXCEED: message size for callhome alert:[chars] exceeds maximum limit for destination profile:[chars]
Explanation Message size for callhome alert:[chars] exceeds maximum limit for destination profile:[chars]
Recommended Action Please check the maximum message size for the destination profile under question. Increase it if possible to match the maximum limit allowed by your email destinations.
Error Message CALLHOME-6-NONCRIT_EVENT: [chars]
Explanation Non-critical Callhome event [chars] occurred.
Recommended Action If you have configured your email address to receive callhome notifications, please check your email for more details about this callhome event. If callhome was not enabled, please execute CLI commands relevant to the callhome event to get more information about the error
This section contains the CARDCLIENT messages.
Error Message CARDCLIENT-2-CARDCL_CRIT: [chars]
Explanation CardClient 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.
Error Message CARDCLIENT-2-FPGA_BOOT_GOLDEN: [chars] booted from Golden
Explanation CardClient fpga boot status
Recommended Action No action is required.
Error Message CARDCLIENT-2-FPGA_BOOT_PRIMARY: [chars] booted from Primary
Explanation CardClient fpga boot status
Recommended Action No action is required.
Error Message CARDCLIENT-2-FPGA_BOOT_STATUS: Unable to retrieve [chars] boot status
Explanation CardClient fpga boot status
Recommended Action No action is required.
Error Message CARDCLIENT-2-ONL: [chars]
Explanation Online 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.
Error Message CARDCLIENT-2-REG: [chars]
Explanation CardClient Console 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.
Error Message CARDCLIENT-2-SSE: [chars]
Explanation CardClient Console 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.
Error Message CARDCLIENT-3-CARDCL_ERR: [chars]
Explanation CardClient 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.
Error Message CARDCLIENT-3-CARDCL_INFO: [chars]
Explanation CardClient 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.
Error Message CARDCLIENT-SLOT#-2-ERR: [chars]
Explanation CardClient Remote Syslog msg
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.
Error Message CARDCLIENT-SLOT#-2-IMG_ERR: [chars]
Explanation CardClient Remote Syslog msg
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.
This section contains the CATENA messages.
Error Message CATENA-2-CATENA_LICENSE_EXPIRED: CATENA License: license grace-period expired. Please install NETWORK_SERVICES_PKG.
Explanation License or grace-period has expired..
Recommended Action Take steps to renew license. Feature will be disabled.
Error Message CATENA-2-CATENA_LICENSE_MISSING: Feature Catena license missing: NETWORK_SERVICES_PKG
Explanation License does not exist when attempting to enable Catena feature.
Recommended Action Acquire license or grace-period permission.
Error Message CATENA-2-LICENSE_EXPIRED: Catena License: license grace-period expired. Please install NETWORK_SERVICES_PKG.
Explanation License or grace-period has expired.
Recommended Action Take steps to renew license. Feature will be disabled.
Error Message CATENA-4-ISSU_PRE_UPGRADE_TIMEOUT: Catena ISSU: pre-upgrade timed out, reason: [chars].
Explanation See the reason.
Recommended Action Try again with the upgrade.
This section contains the CDP messages.
Error Message CDP-2-INITFAIL: CDP Daemon Initialization failed: [chars]
Explanation CDP Daemon Initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message CDP-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation CDP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message CDP-3-GENERROR: [chars]
Explanation CDP Daemon 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.
Error Message CDP-3-MCASTBINDFAIL: Failed to bind for CDP multicast address on interface [hex] - [chars]
Explanation An attempt to register for packets destined to the CDP multicast address failed. [dec] identifies the interface [char] identifies the reason.
Recommended Action No action is required.
Error Message CDP-3-MTSERROR: [chars]
Explanation CDP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action No action is required.
Error Message CDP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Explanation Failed to receive packet. [char] identifies the reason.
Recommended Action No action is required.
Error Message CDP-3-PKTSENDFAIL: Failed to send packet, interface [hex] - [chars]
Explanation Failed to send packet. [dec] identifies the interface [char] identifies the reason.
Recommended Action No action is required.
Error Message CDP-3-PSSERROR: [chars]
Explanation CDP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message CDP-3-SOCKBINDFAIL: Failed to bind to raw socket, interface [hex] - [chars]
Explanation Failed to bind to raw socket. [dec] identifies the interface [char] identifies the reason.
Recommended Action No action is required.
Error Message CDP-3-SOCKOPENFAIL: Failed to open socket for receiving raw 802_2 packets - [chars]
Explanation An attempt to open a socket for receiving raw 802_2 packets failed. [char] identifies the reason.
Recommended Action No action is required.
Error Message CDP-4-CDP_PDU_PAYLOAD_TOO_BIG: CDP PDU payload len is too big over [dec], if_index:[hex], payload_len:[dec](ext_hdr:[dec])
Explanation CDP PDU payload len is too big This is a warning message.
Recommended Action No action is required.
Error Message CDP-4-DUPLEX_MISMATCH: Duplex mismatch discovered on [chars], with [chars]
Explanation Duplex mismatch discovered from the received cdp packet This is a warning message.
Recommended Action No action is required.
Error Message CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on [chars]([dec]), with [chars]([dec])
Explanation Native VLAN mismatch discovered This is a warning message.
Recommended Action No action is required.
Error Message CDP-5-DISABLED: CDP is disabled
Explanation CDP is disabled on the device.
Recommended Action No action is required.
Error Message CDP-5-ENABLED: CDP is enabled
Explanation CDP is enabled on the device.
Recommended Action No action is required.
Error Message CDP-5-NEIGHBOR_ADDED: Device [chars] discovered of type [chars] with port [chars] on incoming port [chars] with ip addr [chars] and mgmt ip [chars]
Explanation Discovered a neighbor device. This is an informational message.
Recommended Action No action is required.
Error Message CDP-5-NEIGHBOR_REMOVED: CDP Neighbor [chars] on port [chars] has been removed
Explanation Deleted a neighbor device. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-CDPDUP: CDP Daemon Up.
Explanation CDP Daemon was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-CDPEXIT: CDP Daemon shutting down gracefully.
Explanation CDP Daemon is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-PORTDISABLE: CDP disabled on port [chars]
Explanation CDP was disabled on a given port. [chars] is the interface-ID string that identifies the port. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-PORTDOWN: A CDP enabled port [chars] went down.
Explanation A CDP enabled port became un-operational. [chars] is the interface-ID string that identifies the port. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-PORTENABLE: CDP enabled on port [chars]
Explanation CDP was enabled on a given port. [chars] is the interface-ID string that identifies the port. This is an informational message.
Recommended Action No action is required.
Error Message CDP-6-PORTUP: A CDP enabled port [chars] came up.
Explanation A CDP enabled port became operational. [chars] is the interface-ID string that identifies the port. This is an informational message.
Recommended Action No action is required.
This section contains the CERT_ENROLL messages.
Error Message CERT_ENROLL-2-CERT_EN_PROGRAM_EXIT: cert_enroll daemon exiting: [chars]
Explanation Cert_enroll 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.
Error Message CERT_ENROLL-3-CERT_EN_ERROR_MESSAGE: [chars]
Explanation CERT_ENROLL Error Message
Recommended Action No action is required.
Error Message CERT_ENROLL-3-CERT_EN_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode : [chars]
Explanation FIPS mode initialization error
Recommended Action No action is required.
Error Message CERT_ENROLL-6-CERT_EN_MESSAGE: [chars]
Explanation CERT_ENROLL Message
Recommended Action No action is required.
This section contains the CFS messages.
Error Message CFS-2-CFS_REJECT: CFS reject: [chars]: Switch WWN [chars], ip [chars], reason [chars]
Explanation CFS reject: [chars] Switch WWN [chars], ip [chars], reason [chars]
Recommended Action No action is required.
Error Message CFS-2-EXITING: Exit reason: [chars]
Explanation The CFS service process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message CFS-2-GENERAL_ERROR: [chars]
Explanation The CFS service has encountered an critical error. The description of error is [str.]
Recommended Action No action is required.
Error Message CFS-2-INITFAIL: CFS Service Init failed: [chars]
Explanation CFS Service initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message CFS-2-LOCK_FAILED: lock failed for sap [dec] due to internal error.
Explanation Lock failed due to Unrestricted uncoordinated count is out of sync for sap [dec]
Recommended Action To recover from this state run command 'cfs internal decrement-unrestricted
Error Message CFS-2-MALLOC_ERROR: Size [dec] bytes
Explanation The CFS service could not allocate memory.
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.
Error Message CFS-2-MTS_REJECT: Verification failed reject MTS message SAP [dec]:RR-token [hex]
Explanation This MTS message could have been posted by the previous active running pre 3.x; MTS structure has changed since then hence ignore the MTS message, Source SAP [dec]; RR-token [hex]
Recommended Action No action is required.
Error Message CFS-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The CFS service encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Error Message CFS-2-VDC_MGR_FAIL: Failed to get a valid switch mac from VDC Manager: [chars]
Explanation VDC manager did not respond with a proper MAC address. It could have been because of a timeout in MTS received
Recommended Action No action is required.
Error Message CFS-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation CFS Service is out of dynamic memory. [chars] specifies the context where the failure occured
Recommended Action No action is required.
Error Message CFS-3-APP_MERGE_FAILED: Merge failed for app [chars], local switch wwn [chars], remote switch wwn [chars].Please check 'show cfs merge status name [chars]' for more information
Explanation The CFS service has detected a merge failure.
Recommended Action No action is required.
Error Message CFS-3-CFS_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The CFS service has detected corruption in one of its persistent information database. The database would be recreated.
Recommended Action No action is required.
Error Message CFS-3-DBERROR: [chars]
Explanation CFS Service encountered a database error. [chars] specifies the context where the failure occured.
Recommended Action No action is required.
Error Message CFS-3-FAILURE_RESPONSE: [chars] [hex]
Explanation CFS Service failed to get response [chars][hex] specify the context where the failure occured.
Recommended Action No action is required.
Error Message CFS-3-FIPS_TEST_FAILED: FIPS compliance test failed
Explanation FIPS compliance test failed
Recommended Action No action is required.
Error Message CFS-3-GENERROR: [chars]
Explanation CFS Service 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.
Error Message CFS-3-LICERR: [chars]
Explanation CFS Service failed to get license.
Recommended Action No action is required.
Error Message CFS-3-MERGE_FAILED: Merge failed for app [chars], local switch wwn [chars],ip [chars], remote switch wwn [chars], ip [chars]
Explanation The CFS service has detected a merge failure.
Recommended Action No action is required.
Error Message CFS-3-MTSERROR: [chars]
Explanation CFS Service encountered an MTS error. [chars] specifies the context where the error occured.
Recommended Action No action is required.
Error Message CFS-3-PSSERROR: [chars]
Explanation CFS Service encountered a PSS error. [chars] specifies the context where the failure occured.
Recommended Action No action is required.
Error Message CFS-3-TIMEOUT_ERROR: [chars] [hex]
Explanation CFS Service encountered a timeout [chars][hex] specify the context where the failure occured.
Recommended Action No action is required.
Error Message CFS-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]
Explanation The CFS service has received an unknown message from [dec]].[dec]. This information is for debugging only.
Recommended Action No action is required.
Error Message CFS-4-LICEXP: [chars]
Explanation CFS Service license is going to expire. [chars] gives the expected time of expiry
Recommended Action No action is required.
Error Message CFS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the CFS service and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error Message CFS-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The CFS service on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Error Message CFS-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The CFS service became standby from active mode.
Recommended Action No action is required.
Error Message CFS-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.]
Recommended Action No action is required.
Error Message CFS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]
Explanation The CFS service was unable to send heartbeat to the system manger
Recommended Action No action is required.
Error Message CFS-6-GENERAL_EVENT: [chars]
Explanation The CFS service has generated an important event. The description of the event is [str.]
Recommended Action No action is required.
Error Message CFS-6-INVALID_CHECKSUM: Received packet from peer on if-index([hex]) with corrupted checksum
Explanation This could be because of errors in the link
Recommended Action No action is required.
Error Message CFS-6-INVALID_IF_INDEX: Received packet on if-index([hex]) which is not recognized by CFS
Explanation The if-index does not match with the if-index used in discovery or we might have already recieved an adjacency cleanup message for this if-index. Check if the if-index is that of the port-channel or a physical if-index
Recommended Action No action is required.
Error Message CFS-6-LOGICAL_DISTRIBUTION_INFO: vsan [dec], source wwn [chars], ip [chars] app-id [dec], session-id [dec], user [chars], [chars]
Explanation Vsan [dec], source wwn [chars], ip [chars], app-id [dec], user [chars], event [chars]
Recommended Action No action is required.
Error Message CFS-6-PHY_DISTRIBUTION_INFO: source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], [chars]
Explanation Source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], event [chars]
Recommended Action No action is required.
Error Message CFS-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of CFS service has been recreated
Recommended Action No action is required.
Error Message CFS-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases of CFS Service has been intentionally destroyed and would be recreated.
Recommended Action No action is required.
Error Message CFS-6-REGION_CTX_REMOVED: Region info is deleted for [chars]
Explanation [chars] is in logical scope. Regions are supported only physical scope applications
Recommended Action No action is required.
Error Message CFS-6-SERVICE_UP: Initialized [chars]
Explanation The CFS service is up and ready to accept client requests The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message CFS-6-SRVCREATED: CFS Service created
Explanation CFS Service was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Error Message CFS-6-SRVEXIT: CFS Service shutting down gracefully
Explanation CFS Service is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message CFS-6-SWITCHOVER: Switching Over to other Sup.
Explanation The CFS service has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
This section contains the CLIS messages.
Error Message CLIS-5-CLIS_SYSLOG_CMD_REMOVED: Command deleted from the NVDB: [chars]
Explanation Command removal due to configuration change
Recommended Action No action is required.
This section contains the CLK_MGR messages.
Error Message CLK_MGR-2-CLK_MGR_FC2_CRIT: CLK_MGR critical error: [chars]
Explanation CLK_MGR fc2 clock synchronization critical error
Recommended Action No action is required.
Error Message CLK_MGR-5-CLK_MGR_CLI_CONFIG: CLK_MGR clock is synchronized by [chars] from VDC [dec]
Explanation CLK_MGR clock is synchronized by [chars] from VDC
Recommended Action No action is required.
Error Message CLK_MGR-6-CLK_MGR_TSTAMP_CHKS_DISABLED: CLK_MGR timestamp checks disabled: [chars]
Explanation CLK_MGR timestamp checks disabled
Recommended Action No action is required.
Error Message CLK_MGR-6-CLK_MGR_TSTAMP_CHKS_ENABLED: CLK_MGR timestamp checks enabled
Explanation CLK_MGR timestamp checks enabled
Recommended Action No action is required.
This section contains the CLOUD messages.
Error Message CLOUD-2-PROGRAM_EXIT: cloud-discovery process ending: [chars]
Explanation Cloud-discovery process is exiting with reason [chars].
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.
Error Message CLOUD-3-CLOUD_CFS_MERGE_OPERATION_FAILED: [chars]
Explanation [chars1]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message CLOUD-3-CLOUD_CFS_OPERATION_FAILED: [chars] : [chars]
Explanation [chars1] [chars2]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message CLOUD-3-CLOUD_FEATURE_MANAGER_ERROR: [chars] : [chars]
Explanation [chars1] [chars2]
Recommended Action Please check the reason for error using feature manager and rectify the problem
Error Message CLOUD-3-CLOUD_PSS_OPERATION_FAILED: [chars] : [chars]
Explanation [chars1] [chars2]
Recommended Action Please check the reason for the failure of the pss operation and rectify the problem
Error Message CLOUD-6-CLOUD_DISCOVERY_DONE: discovery over
Explanation Cloud-discovery started
Recommended Action Check cloud membership
Error Message CLOUD-6-CLOUD_DISCOVERY_STARTED: [chars] discovery started
Explanation Cloud-discovery started
Recommended Action Check cloud-discovery status after sometime
This section contains the CLUSTER messages.
Error Message CLUSTER-2-CLUSTER_ADD_FAIL: Cluster 0x%llx creation failed
Explanation Cluster Creation Failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_CAP_ADD_FAIL: Failed to add cluster capability [dec]
Explanation Cluster capability addition failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_CAP_DEL_FAIL: Failed to delete cluster capability [dec]
Explanation Cluster capability deletion failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_CONF_MGR_FAIL: Configuration manager failed to handle "[chars]" ([dec]) status=[hex]
Explanation Cluster Config Manager failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_DB_SYNC_FAIL_CLIENT: Client on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason="[chars]" from application
Explanation Cluster database synchronization failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_DB_SYNC_FAIL_MANAGER: Manager on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason="[chars]" from server on node 0x%llx
Explanation Cluster database synchronization failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_DB_SYNC_FAIL_SERVER: Server on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason="[chars]" from client on node 0x%llx
Explanation Cluster database synchronization failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_DB_SYNC_FAIL: Cluster 0x%llx application [dec] dataset [dec] database synchronization failed, reason="[chars]"
Explanation Cluster database synchronization failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_LEADER_ANNOUNCE: Node 0x%llx is the new Master of cluster 0x%llx of [dec] nodes
Explanation Leader announcement of cluster
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_LEAVE_REQ_FAIL: Node failed to send LEAVE request to Cluster 0x%llx
Explanation Failed to send Leave Request
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_LEAVE_RESP_FAIL: Bad response to LEAVE request for Cluster 0x%llx
Explanation Received Bad Leave response
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_LOCAL_NODE_EXIT: Local Node 0x%llx has left the Cluster 0x%llx Reason:[chars]
Explanation Node is not part of cluster
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x%llx now has quorum with [dec] nodes
Explanation Cluster has quorum
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_QUORUM_LOSS: Cluster 0x%llx has lost quorum; number of nodes=[dec]
Explanation Cluster has lost quorum
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_RGC_TRANSACTION_FAIL: Cluster 0x%llx RGC transaction application=[dec] dataset=[dec] failed reason="[chars]"
Explanation Cluster RGC transaction failed
Recommended Action No action is required.
Error Message CLUSTER-2-CLUSTER_TRANSPORT_FAIL: Cluster 0x%llx transport failed to send message from node 0x%llx to 0x%llx error=[dec]
Explanation Cluster transport failed to send message
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_ADD: Cluster 0x%llx added
Explanation Cluster Added
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_DISABLED: CLUSTER Disabled
Explanation CLUSTER Service Disabled
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_ENABLED: CLUSTER Enabled
Explanation CLUSTER Service Enabled
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_NODE_ADD: Node 0x%llx added to cluster 0x%llx
Explanation Node added to cluster
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_NODE_JOIN: Node 0x%llx joined cluster 0x%llx
Explanation Node joined cluster
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_NODE_LEAVE_EXPLICIT: Remote Node 0x%llx has left the Cluster 0x%llx voluntarily
Explanation Remote Node Left voluntarily
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_NODE_LEAVE: Node 0x%llx not in cluster 0x%llx
Explanation Node not in cluster
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_NODE_REMOVE: Node 0x%llx removed from cluster 0x%llx
Explanation Node removed from cluster
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_REMOVE: Cluster 0x%llx removed
Explanation Cluster removed
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_RX_JOIN_REQ: Node 0x%llx received JOIN request from node=0x%llx
Explanation Cluster received JOIN request
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_RX_JOIN_RESP: Node 0x%llx received JOIN response from node=0x%llx result="[chars]"
Explanation Cluster received JOIN response
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_RX_PROBE: Node 0x%llx received PROBE from node=0x%llx
Explanation Cluster received PROBE message
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_STARTED: CLUSTER 0x%llx Started
Explanation CLUSTER Started
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_STOPPED: CLUSTER 0x%llx Stopped
Explanation CLUSTER Stopped
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_TRANSPORT_DOWN: Cluster 0x%llx transport down for node=0x%llx
Explanation Cluster Transport Connection DOWN
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_TRANSPORT_UP: Cluster 0x%llx transport up for node=0x%llx
Explanation Cluster Transport Connection UP
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_TX_JOIN_REQ: Node 0x%llx sending JOIN request to node=0x%llx
Explanation Cluster sending JOIN request
Recommended Action No action is required.
Error Message CLUSTER-5-CLUSTER_TX_JOIN_RESP: Node 0x%llx sending JOIN response to node=0x%llx result="[chars]"
Explanation Cluster sending JOIN request
Recommended Action No action is required.
This section contains the CMOND messages.
Error Message CMOND-2-CMOND_ALERT_MSG: [chars]
Explanation Alert message
Recommended Action No action is required.
Error Message CMOND-2-CMOND_ERROR_MSG: [chars]
Explanation Error message
Recommended Action No action is required.
This section contains the COPP messages.
Error Message COPP-1-COPP_DROPS1: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-2-COPP_DROPS2: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-2-COPP_INIT_FAIL: CoPP Initialization failed: [chars]
Explanation CoPP Initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message COPP-2-COPP_MTS_FAIL: Failed to do MTS operation: [chars]
Explanation Failed to do MTS operation. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message COPP-2-COPP_NO_POLICY: Control-plane is unprotected.
Explanation There isn't any policy configured to protect control-plane.
Recommended Action No action is required.
Error Message COPP-2-COPP_POLICY: Control-Plane is protected with policy [chars].
Explanation There is a policy attached to the control-plane.
Recommended Action No action is required.
Error Message COPP-2-COPP_PROFILE_DIFF: CoPP Default Profile may have changed, please check the diffs using show copp diff profile
Explanation CoPP Default Profile may have changed, please check the diffs using show copp diff profile
Recommended Action No action is required.
Error Message COPP-2-COPP_RATELIMIT_DISABLED: CoPP rate-limit is disabled for all classes. Hence CPU is vulnerable to traffic attacks. Please do "no copp rate-limit disable" as soon as possible
Explanation CoPP rate-limit is disabled for all classes
Recommended Action No action is required.
Error Message COPP-3-COPP_ALLOC_FAIL: Memory allocation failure: [chars]
Explanation Failed to alloc required memory. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message COPP-3-COPP_DROPS3: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-3-COPP_PPF_FAIL: Error during PPF operation: [chars]
Explanation Failed to do PPF operation. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message COPP-3-COPP_PSS_FAIL: Error during PSS operation: [chars]
Explanation Failed to do PSS operation. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message COPP-4-COPP_DROPS4: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-5-COPP_DISABLED: COPP Disabled
Explanation COPP Service Disabled
Recommended Action No action is required.
Error Message COPP-5-COPP_DROPS5: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-5-COPP_ENABLED: COPP Enabled
Explanation COPP Service nabled
Recommended Action No action is required.
Error Message COPP-5-COPP_INIT: COPP initialized
Explanation COPP Service Initialized
Recommended Action No action is required.
Error Message COPP-6-COPP_DROPS6: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
Error Message COPP-6-COPP_POLICY_ATTACHED: CoPP policy has been attached to control plane interface.
Explanation CoPP policy has been attached to control plane interface.
Recommended Action No action is required.
Error Message COPP-6-COPP_POLICY_DETACHED: CoPP policy has been detached from control plane interface.
Explanation CoPP policy has been detached from control plane interface.
Recommended Action No action is required.
Error Message COPP-7-COPP_DROPS7: CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
Recommended Action No action is required.
This section contains the CORE-DMON messages.
Error Message CORE-DMON-2-MODULE_COREDUMP_DONE: kernel coredump completed on module:[dec]
Explanation Kernel coredump finishing on a module
Recommended Action No action is required.
Error Message CORE-DMON-2-MODULE_COREDUMP_STARTED: kernel coredump started on module:[dec]
Explanation Kernel coredump starting on a module
Recommended Action No action is required.
Error Message CORE-DMON-3-NO_SPACE: Failed to save core file [chars]. Try removing existing core files.
Explanation Not enough space to save new core files
Recommended Action No action is required.
This section contains the CRDCFG messages.
Error Message CRDCFG-2-CRDCFG_SRV_CRIT: [chars]
Explanation CardConfig CRITICAL 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.
Error Message CRDCFG-3-CRDCFG_ERR: [chars]
Explanation CardConfig error mesage
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.
Error Message CRDCFG-3-CRDCFG_MSG: [chars]
Explanation CardConfig log mesage
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.
Error Message CRDCFG-3-CRDCFG_SRV_ERR: [chars]
Explanation CardConfigServer error mesage
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.
Error Message CRDCFG-3-CRDCFG_SRV_MSG: [chars]
Explanation CardConfigServer log mesage
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.
Error Message CRDCFG-SLOT#-2-CONFIG_ERR: [chars]
Explanation CardConfig Failed to find matching cardid, pnum in database
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.
This section contains the DCEFIB messages.
Error Message DCEFIB-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation L2mp unicast fib failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation L2mp unicast fib failed to initialize timer library. This is a fatal error.
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-2-DCEFIB_MEM_ALLOC: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-2-DCEFIB_RECOVERY_ERROR: Error in Recovery: [chars]
Explanation L2mp unicast fib failed to recover after a re-start. This is a fatal error.
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-2-U2FIB_ERR: [chars]
Explanation L2mp unicast fib encountered an error:
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation L2mp unicast fib has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-6-U2FIB_INFO: [chars]
Explanation L2mp unicast fib notice:
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-6-VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in l2mp unicsat fib was successful.
Recommended Action No action is required.
Error Message DCEFIB-SLOT#-6-VDC_REMOVED: VDC [dec] Removed
Explanation L2mp unicast fib has successfully removed VDC [dec] from its databases.
Recommended Action No action is required.
This section contains the DEVICE-ALIAS messages.
Error Message DEVICE-ALIAS-2-ALLOC_FAILED: Memory allocation failed for size:[dec] type:[dec]
Explanation Memory allocation failed for size [dec] type [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.
Error Message DEVICE-ALIAS-2-INIT_FAILED: [chars]
Explanation An error occurred during initialization. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-CFS_OPER_FAILED: [chars]
Explanation An error occurred while performing a CFS operation. [chars] indicates the CFS operation and the reason for 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.
Error Message DEVICE-ALIAS-3-CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the session. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-COMMIT_FAILED: [chars]
Explanation An error occurred while committing the database. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-COMMIT_REJECTED: [chars]
Explanation Commit request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the lock. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-LOCK_REJECTED: [chars]
Explanation Lock request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_FAILED: [chars]
Explanation An error occurred while activating the merged database. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_REJECTED: [chars]
Explanation Merge activation request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_FAILED: [chars]
Explanation An error occurred during merge operation. [chars] indicates the reason for failure.
Recommended Action Compare device-alias configuration with the other switches in the fabric, resolve the conflicts if any and commit the changes.
Error Message DEVICE-ALIAS-3-MERGE_MREQ_REJECTED: [chars]
Explanation MREQ received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_MRESP_REJECTED: [chars]
Explanation MRESP received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_VALIDATION_FAILED: [chars]
Explanation An error occurred while validating the merged database. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MERGE_VALIDATION_REJECTED: [chars]
Explanation Merge validation request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-MTS_OPER_FAILED: [chars]
Explanation An error occurred during MTS operation. [chars] indicates the MTS operation and the reason for 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.
Error Message DEVICE-ALIAS-3-PSS_OPER_FAILED: [chars]
Explanation An error occurred during PSS operation. [chars] indicates the PSS operation and the reason for 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.
Error Message DEVICE-ALIAS-3-UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the lock. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-UNLOCK_REJECTED: [chars]
Explanation Unlock request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-VALIDATION_FAILED: [chars]
Explanation An error occurred while validating the database. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-3-VALIDATION_REJECTED: [chars]
Explanation Validation request received from remote switch is rejected. [chars] indicates the reason for 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.
Error Message DEVICE-ALIAS-6-CLEAR_FAILED_INFO: [chars]
Explanation An error occurred while clearing the session. [chars] indicates the additional information regarding 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.
Error Message DEVICE-ALIAS-6-COMMIT_FAILED_INFO: [chars]
Explanation An error occurred while committing the database. [chars] indicates the additional information regarding 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.
Error Message DEVICE-ALIAS-6-IMPORT_DEFINITION_CONFLICT: Fcalias [chars] could not be imported due to definition conflict
Explanation Fcalias [chars] could not be imported due to definition conflict. Either there is already a device-alias configuration present with the same definition OR another VSAN specified in the import VSAN range has an fcalias with the same definition.
Recommended Action Resolve the conflict and issue the import command again.
Error Message DEVICE-ALIAS-6-IMPORT_MEMBER_TYPE_CONFLICT: Fcalias [chars] could not be imported due to having unsupported member type
Explanation Fcalias [chars] could not be imported due to having unsupported member types. Fcalias can be imported only if it has Port WWN based members..
Recommended Action Make sure that the fcalias has Port WWN based members and issue the import command again.
Error Message DEVICE-ALIAS-6-IMPORT_NAME_CONFLICT: Fcalias [chars] could not be imported due to name conflict
Explanation Fcalias [chars] could not be imported due to name conflict. Either there is already a device-alias configuration present with the same name OR another VSAN specified in the import VSAN range has an fcalias with the same name.
Recommended Action Resolve the conflict and issue the import command again.
Error Message DEVICE-ALIAS-6-IMPORT_NUM_MEMBERS_CONFLICT: Fcalias [chars] could not be imported due to having unsupported number of members
Explanation Fcalias [chars] could not be imported due to having unsupported number of members. Fcalias can be imported only if it has exactly one member..
Recommended Action Make sure that the fcalias has exactly one member and issue the import command again.
Error Message DEVICE-ALIAS-6-LOCK_FAILED_INFO: [chars]
Explanation An error occurred while acquiring the lock. [chars] indicates the additional information regarding 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.
Error Message DEVICE-ALIAS-6-MERGE_ACTIVATION_FAILED_INFO: [chars]
Explanation An error occurred while activating the merged database. [chars] indicates the additional information regarding 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.
Error Message DEVICE-ALIAS-6-MERGE_VALIDATION_FAILED_BUSY: [chars]
Explanation Merged database could not be validated as some of the applications returned busy. [chars] indicates information about the application returned busy. There is no user intervention necessary. The validation would be automatically retried after some time.
Recommended Action No DDTS.
Error Message DEVICE-ALIAS-6-MERGE_VALIDATION_REJECTED_BUSY: [chars]
Explanation Merged database received from the remote switch could not be validated as some of the applications returned busy. [chars] indicates information about the application returned busy. There is no user intervention necessary. The validation would be automatically retried after some time.
Recommended Action No DDTS.
Error Message DEVICE-ALIAS-6-UNLOCK_FAILED_INFO: [chars]
Explanation An error occurred while releasing the lock. [chars] indicates the additional information regarding 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.
Error Message DEVICE-ALIAS-6-VALIDATION_ABORTED: [chars]
Explanation Local validation is aborted. [chars] indicates the reason why validation is aborted.
Recommended Action No DDTS.
This section contains the DEVICE_TEST messages.
Error Message DEVICE_TEST-2-ASIC_REG_CHECK_FAIL: Module [dec] has failed test [chars] [dec] times on device [chars] [chars] [dec] [chars] due to error [chars]
Explanation Online diagnostics ASICRegisterCheck test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-COMPACT_FLASH_FAIL: Module [dec] has failed test [chars] [dec] times on device BootFlash due to error [chars]
Explanation Online diagnostics BootFlash test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-CRYPTO_DEVICE_FAIL: Module [dec] has failed test [chars] [dec] times on Crypto device due to error [chars]
Explanation Online diagnostics CryptoDevice test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-EOBC_FAIL: Module [dec] has failed test [chars] on EOBC due to error [chars]
Explanation Online diagnostics EOBC test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-FAN_MOD_FAIL: Module [dec] has failed test [chars] [dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to error [chars] error number [hex]
Explanation Online diagnostics SystemMgmtBus test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-MALLOC_FAILURE: Memory allocation failed
Explanation Device Test process could not allocate memory
Recommended Action No action is required.
Error Message DEVICE_TEST-2-MGMT_PORT_SKIP: Module [dec] has skipped test [chars] on Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test is skipped
Recommended Action No action is required.
Error Message DEVICE_TEST-2-NVRAM_FAIL: Module [dec] has failed test [chars] [dec] times on device NVRAM due to error [chars]
Explanation Online diagnostics NVRAM test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-OBFL_FAIL: Module [dec] has failed test [chars] [dec] times on device OBFL due to error [chars]
Explanation Online diagnostics OBFL test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-POWER_SUPPLY_FAIL: Module [dec] has failed test [chars] [dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to error [chars] error number [hex]
Explanation Online diagnostics SystemMgmtBus test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-PWR_MGMT_BUS_FAIL: Module [dec] has failed test [chars] [dec] times on device Power Mgmt Bus on slot [dec] due to error [chars] error number [hex]
Explanation Online diagnostics PwrMgmtBus test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-RTC_FAIL: Module [dec] has failed test [chars] [dec] times on device RealTimeClock due to error [chars]
Explanation Online diagnostics RealTimeClock test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-SPINE_CONTROL_BUS_FAIL: Module [dec] has failed test [chars] [dec] times on device Spine Control Bus on slot [dec] due to error [chars] error number [hex]
Explanation Online diagnostics SpineControlBus test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-STANDBY_LOOPBACK_TEST_FAIL: Module [dec] has failed test [chars] [dec] times on [chars] [dec] due to error [chars]
Explanation Online diagnostics StandbyFabricLoopback test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-TWOWIRE_STW_FAIL: Module [dec] has failed test [chars] [dec] times on Status Bus on slot [dec] due to error [chars]
Explanation Online diagnostics Status bus test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-2-USB_FAIL: Module [dec] has failed test [chars] [dec] times on device USB due to error [chars]
Explanation Online diagnostics USB test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-3-MCE_1HR_FAIL: Module [dec] has exceeded MCE 1 hour correctable threshold of [dec] with [dec] correctable errors for address 0x%llx within 1 an hour.
Explanation These memory errors are correctable and no functional impact to system behavior. However, excessive correctable memory errors can be an indication of possible hardware fault. Please collect \show tech gold\ and open a Support case for further investigation.
Recommended Action No action is required.
Error Message DEVICE_TEST-3-MCE_24HR_FAIL: Module [dec] has exceeded MCE 24 hour correctable threshold of [dec] with [dec] correctable errors within 24 hours.
Explanation These memory errors are correctable and no functional impact to system behavior. However, excessive correctable memory errors can be an indication of possible hardware fault. Please collect \show tech gold\ and open a Support case for further investigation.
Recommended Action No action is required.
Error Message DEVICE_TEST-3-STANDBY_TEST_GET_DIAG_VQI_FAIL: Standby test get diag vqi failed due to error [hex]
Explanation Device Test StandbyLoopback Test failed get vqi
Recommended Action No action is required.
Error Message DEVICE_TEST-3-STANDBY_TEST_GET_SPINE_FAIL: Standby test get spines failed due to error [hex]
Explanation Device Test StandbyFabricLoopback Test get spine failed
Recommended Action No action is required.
Error Message DEVICE_TEST-3-STANDBY_TEST_INIT_FAIL: Init for standby test failed due to error [hex]
Explanation Device Test StandbyFabricLoopback Test failed init process
Recommended Action No action is required.
Error Message DEVICE_TEST-3-STANDBY_TEST_MTS_FAIL: Mts Init for standby test failed due to error [hex]
Explanation Device Test StandbyFabricLoopback Test failed mts init
Recommended Action No action is required.
Error Message DEVICE_TEST-3-STANDBY_TEST_SOCKET_FAIL: Standby test socket error [chars]: [hex]
Explanation Device Test StandbyFabricLoopback Test Socket error
Recommended Action No action is required.
Error Message DEVICE_TEST-4-PRIMARY_BOOTROM_FAIL: Module [dec] has failed test [chars] [dec] times on device Primary BootROM due to error [chars]
Explanation Online diagnostics PrimaryBootROM test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-4-SECONDARY_BOOTROM_FAIL: Module [dec] has failed test [chars] [dec] times on device Secondary BootROM due to error [chars]
Explanation Online diagnostics SecondaryBootROM test has failed
Recommended Action No action is required.
Error Message DEVICE_TEST-4-THREAD_CREATE_FAIL: Thread creation failed
Explanation Device Test process could not create threads
Recommended Action No action is required.
Error Message DEVICE_TEST-4-TIMER_CREATE_FAIL: Timer creation failed
Explanation Device Test process could not create timer
Recommended Action No action is required.
Error Message DEVICE_TEST-4-TIMER_START_FAIL: Timer start failed
Explanation Device Test process could not start timer
Recommended Action No action is required.
Error Message DEVICE_TEST-5-NOTICE_TEST: Memory allocation failed notice
Explanation Device Test process could not allocate memory
Recommended Action No action is required.
Error Message DEVICE_TEST-6-INFO_TEST: Memory allocation failed info
Explanation Device Test process could not allocate memory
Recommended Action No action is required.
This section contains the DEV_LOG_SUP messages.
Error Message DEV_LOG_SUP-3-ERROR: [chars]
Explanation Dev_log_sup encountered an error
Recommended Action No action is required.
This section contains the DEV_LOG messages.
Error Message DEV_LOG-3-ERROR: [chars]
Explanation Dev_log_lc encountered an error
Recommended Action No action is required.
Error Message DEV_LOG-SLOT#-4-DEV_LOG_LC_ERROR: [chars]
Explanation Dev_log_lc encountered an error
Recommended Action No action is required.
This section contains the DFTM messages.
Error Message DFTM-SLOT#-2-DFTM_INTF_NOT_FOUND: Interface [chars] not found in DFTM database [chars]
Explanation DFTM database doesn't have the interface.
Recommended Action No action is required.
Error Message DFTM-SLOT#-2-DFTM_INVALID_FTAG_NUM: DFTM received invalid number of FTags [dec] from M2RIB
Explanation DFTM recvd invalid number of FTags from M2RIB.
Recommended Action No action is required.
Error Message DFTM-SLOT#-2-DFTM_INVALID_INTF_NUM: DFTM has invalid number of interfaces [dec] in the DB
Explanation DFTM has invalid number of interfaces in the DB.
Recommended Action No action is required.
Error Message DFTM-SLOT#-2-DFTM_PC_NUM_MEMB_INVALID: DFTM received invalid number of PC members [dec] from ELTM
Explanation DFTM recvd invalid number of PC members from ELTM.
Recommended Action No action is required.
Error Message DFTM-SLOT#-2-DFTM_VLAN_NOT_FOUND: VLAN [dec] not found in DFTM database [chars]
Explanation DFTM database doesn't have the VLAN.
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_BDDB_PROG_FAILED: DFTM failed to program BDDB Entry
Explanation DFTM failed to program BDDB Entry
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_BDT_PROG_FAILED: DFTM failed to program BD Table Entry
Explanation DFTM failed to program BD Table Entry
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_LAYER: Invalid Port Layer Received for interface: [chars]
Explanation Invalid Port Layer Received for interface
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_MODE: Invalid Port Mode Received for interface: [chars]
Explanation Invalid Port Mode Received for interface
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_TYPE: Invalid Port Type Received for interface: [chars]
Explanation Invalid Port Type Received for interface
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_IFIDX_TYPE_ERROR: Failed to get type for interface: [chars]
Explanation Failed to get type for the interface
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_INVALID_PRIM_SEC_VLAN_REQ: DFTM received prim-sec request for a non-exiting sec vlan [dec] on primary [dec]
Explanation DFTM recvd prim-sec vlan mapping request for a non-existing sec vlan on prim vlan
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_L2L3CT_PROG_FAILED: DFTM failed to program L2L3 Consistency Table Entry
Explanation DFTM failed to program L2L3 Consistency Table Entry
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_MFT_PROG_FAILED: DFTM failed to program Multicast FTag Table Entry
Explanation DFTM failed to program Multicast Ftag Table Entry
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_SDT_PROG_FAILED: DFTM failed to program SGT DGT Table Entry
Explanation DFTM failed to program SGT DGT Table Entry
Recommended Action No action is required.
Error Message DFTM-SLOT#-3-DFTM_VTT_PROG_FAILED: DFTM failed to program VLAN Translation Table Entry for vlan [dec], xlt_vlan [dec] on fe [dec]
Explanation DFTM failed to program VLAN Translation Table
Recommended Action No action is required.
This section contains the DHCLIENT messages.
Error Message DHCLIENT-2-DHCLIENT_DISCOVER_RECVD_NAK: [chars] - Received DHCP NAK
Explanation Received DHCP NAK
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_DISCOVER_START: [chars] - DHCLIENT DHCP Discover phase started
Explanation DHCLIENT DHCP Discover phase started
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_FAILURE: [chars]
Explanation DHCLIENT Failure
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_FLASH_FULL: DHCLIENT bootflash doesn't have enough space (85% FULL)
Explanation DHCLIENT bootflash doesn't have enough space (85% FULL)
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_INITED: [chars] - DHCLIENT process initialized
Explanation DHCLIENT process initialized
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_SCRIPT_DOWNLOADED: [chars] - Successfully downloaded DHCLIENT script file
Explanation Successfully downloaded DHCLIENT script file
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_SCRIPT_EXEC_SUCCESS: [chars] - DHCLIENT script execution success
Explanation DHCLIENT script execution success
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_SCRIPT_STARTED_MD5_NOT_VALIDATED: [chars] - DHCLIENT script execution started(MD5 not validated)
Explanation DHCLIENT script execution started(MD5 not validated)
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_SCRIPT_STARTED_MD5_VALIDATED: [chars] - DHCLIENT script execution started(MD5 validated)
Explanation DHCLIENT script execution started(MD5 validated)
Recommended Action No action is required.
Error Message DHCLIENT-2-DHCLIENT_SCRIPT_STARTED_MD5_VALIDATION_FAIL: [chars] - DHCLIENT boot file validation failed
Explanation DHCLIENT boot file validation failed.
Recommended Action No action is required.
Error Message DHCLIENT-4-DHCLIENT_WARNING: [chars]
Explanation DHCLIENT Warning
Recommended Action No action is required.
Error Message DHCLIENT-5-DHCLIENT_DISABLED: [chars] - DHCLIENT Disabled
Explanation DHCLIENT Service Disabled
Recommended Action No action is required.
Error Message DHCLIENT-5-DHCLIENT_ENABLED: [chars] - DHCLIENT Enabled
Explanation DHCLIENT Service nabled
Recommended Action No action is required.
Error Message DHCLIENT-6-DHCLIENT_INFO: [chars]
Explanation DHCLIENT Info
Recommended Action No action is required.
Error Message DHCLIENT-7-DHCLIENT_DEBUG: [chars]
Explanation DHCLIENT Debug
Recommended Action No action is required.
This section contains the DHCP_SNOOP messages.
Error Message DHCP_SNOOP-1-IPSG_WARN_MSG: Configuring IPSG on the interface will result in IPv6 traffic loss.
Explanation Configuring IPSG on the interface will result in IPv6 traffic loss.
Recommended Action No action is required.
Error Message DHCP_SNOOP-2-DHCP_SNOOP_PROGRAM_EXIT: [chars]
Explanation DHCP snoop process did an abnormal exit
Recommended Action No action is required.
Error Message DHCP_SNOOP-2-HWPGMFAILURE: Hardware programming has failed: [chars]
Explanation Hardware programming has failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message DHCP_SNOOP-2-INITFAIL: DHCP Daemon Initialization failed: [chars]
Explanation DHCP Daemon Initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message DHCP_SNOOP-2-PSSERROR: [chars]
Explanation DHCP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message DHCP_SNOOP-2-REGPARTREE: Unable to register par tree: [chars]
Explanation Could not register par tree. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation DHCP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-ASSERTION_FAILED: [chars]:[dec]
Explanation DHCP Snoop process has hit an assert condition at file [chars] line number [dec]
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-DHCPDENIEDARP: ARP frame denied due to DHCP snooping binding on interface [chars] vlan [dec] sender mac [chars] sender ip [chars] target mac [chars] target ip [chars].
Explanation [chars] identifies interface and [dec] identifies the vlan on which ARP packets have been denied. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies the target mac and [chars] identifies the target ip.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-DHCPRATELIMIT: Interface [chars] has been error disabled due to excessive ingress rate [dec] of DHCP packets.
Explanation [chars] identifies the interface which has been error disabled due to excessive ingress rate [dec].
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-INVDHCPPKTS: Validation errors while processing DHCP packet received on interface [chars] vlan [dec] Reason:[chars]. Dropping the packet
Explanation Validation errors DHCP packet receieved on the interface [chars] vlan [[dec]]. Reason:[chars]
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-IPV6APIINIT_FAILED: [chars]
Explanation DHCP Snoop process failed to do ipv6_api_init [chars]
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-IPV6REGISTER_FAILED: [chars]
Explanation DHCP Snoop process failed to do ipv6_register [chars]
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-MTSERROR: [chars]
Explanation DHCP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-PKTDROP: Packet dropped. Reason - [chars]
Explanation Dropping the packet. [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Explanation Failed to receive packet. [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-PKTSENDFAIL: Failed to send packet, - [chars]
Explanation Failed to send packet. [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-SETSOCKOPTFAIL: Failed to set socket option - [chars]
Explanation Failed to set socket option [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-SOCKBINDFAIL: Failed to bind to raw socket - [chars]
Explanation Failed to bind to socket. [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-3-SOCKOPENFAIL: Failed to open socket for receiving DHCP packets - [chars]
Explanation An attempt to open a socket for receiving DHCP packets failed. [char] identifies the reason.
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-ACL_DENY: [dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-DHCP_SNOOPING_DENY: [dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-ERROR_DISABLED: Interface [chars] has moved to error disabled state due to excessive rate [dec] of ingress ARP packets
Explanation Interface [chars] has moved to error disabled state due to excessive rate [dec] of ingress ARP packets
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-INVALID_ARP: [dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-SMARTRELAYMAXIPADDR: Smart relay is supported only on first [dec] IP addresses of the interface [chars].
Explanation There are more than SMARTRELAYMAXIPADDR addresses configured on the interface. [dec] is the number of IP addresses with which smart relay supported [chars] identifies the interface. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-SMARTRELAYMAXLMT: Smart relay MAX limit [dec] reached. All subsequent DHCP packets will be relayed with primary address of inbound interface as relay agent address.
Explanation Smart relay MAX limit reached. [dec] is the number of smart relay bindings This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-4-SUBNETBCASTRELAYMAXIPADDR: subnet-broadcast relay is supported only on first [dec] IP addresses of the interface [chars].
Explanation There are more than SUBNETBCASTRELAYMAXIPADDR addresses configured on the interface. [dec] is the number of IP addresses with which subnet-broadcast relay supported [chars] identifies the interface. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-ACL_PERMIT: [dec] ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-DHCPHOSTADD: A new Host is [chars] connected to interface [chars] in VLAN [dec] and is allocated IP address [chars] for [dec] secs.
Explanation A Host identified by [chars] has been added. [chars] identifies the interface. [dec] identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-DHCPLEASEEXPIRE: Lease expired for host [chars] having IP address [chars] connected to interface [chars] in VLAN [dec] for lease [dec] secs.
Explanation The lease for host identified by [chars] with IP address [chars] connected to interface [chars] in VLAN [dec] with lease [dec] has expired.
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-DHCP_SNOOPING_PERMIT: [dec] ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-VLANDISABLE: DHCP Snooping disabled on vlan [dec]
Explanation DHCP Snooping was disabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-5-VLANENABLE: DHCP Snooping enabled on vlan [dec]
Explanation DHCP Snooping was enabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DAIVLANDISABLE: DAI disabled on vlan [dec]
Explanation Dynamic ARP Inspection was disabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DAIVLANENABLE: DAI enabled on vlan [dec]
Explanation Dynamic ARP Inspection was enabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DHCPBINDSYNC: Binding entry with MAC [chars] interface [chars] VLAN [dec] IP address [chars] and lease time [dec] secs is synced.
Explanation Binding entry identified by [chars] has been synced. [chars] identifies the interface. [dec] identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DHCPEXIT: DHCP Daemon shutting down gracefully.
Explanation DHCP Daemon is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DHCPPERMITTEDARP: ARP frame permitted due to DHCP snooping binding on interface [chars] vlan [dec] sender mac [chars] sender ip [chars] target mac [chars] target ip [chars].
Explanation [chars] identifies interface and [dec] identifies the vlan on which ARP packets have been permitted. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies the target mac and [chars] identifies the target ip.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DHCPPKTFWD: Gracefully forwarding DHCP packet. Reason: [chars]
Explanation Gracefully forwarding DHCP packet. reason [chars]
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-DHCPUP: DHCP Daemon Up.
Explanation DHCP Daemon was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-INFO: [chars]
Explanation An event during switchover. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-INTFDISABLE: IP Src Guard disabled on intf [chars]
Explanation IP Src Guard was disabled on a given intf. [chars] is the intf-ID string that identifies the intf. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-INTFENABLE: IP Src Guard enabled on intf [chars]
Explanation IP Src Guard was enabled on a given intf. [chars] is the intf-ID string that identifies the intf. This is an informational message.
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-NONDHCPPKTFWD: Non DHCP packet with src port:[dec] dst port:[dec] on intf:[chars] vlan:[dec]. Forwarding on [chars]
Explanation Non DHCP packet arrived with UDP src/dst ports [dec], [dec] on interface [chars], vlan [dec]. Forwarding the packet on [chars]
Recommended Action No action is required.
Error Message DHCP_SNOOP-6-OPT82INSTFAIL: [chars] [chars]
Explanation Insertion of Option82 suboptions failed. [chars] tells the failure. [chars] explains the reason for failure. This is an informational message.
Recommended Action No action is required.
This section contains the DIAGCLIENT messages.
Error Message DIAGCLIENT-2-DIAG_BOOTUP_COMPLETE: Module <[dec]> Bootup Test <[chars]> has reported <[chars]>
Explanation Bootup Test completed
Recommended Action Nothing to be done if the test reports SUCCESS otherwise copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information
Error Message DIAGCLIENT-2-EEM_ACTION_HM_SHUTDOWN: Test <[chars]> has been disabled as a part of default EEM action
Explanation Informational Syslog
Recommended Action No action is required.
Error Message DIAGCLIENT-2-PSS_READ_FAILURE: Read from PSS failed on Module <[dec]>
Explanation Read operation from PSS store failed
Recommended Action No action is required.
Error Message DIAGCLIENT-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]>
Explanation Write operation on PSS store failed
Recommended Action No action is required.
Error Message DIAGCLIENT-3-ONDEMAND_FAIL_EXCESS: Module <[dec]> Test <[chars]> has failed more than <[dec]> number of times
Explanation Ondemand test has failed more than configured number of times
Recommended Action Copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information
Error Message DIAGCLIENT-4-LC_OFFLINE_FOR_CURR_SLOT: Received LC offline event for the current slot:[dec]. Ignoring it
Explanation Informational Syslog
Recommended Action No action is required.
Error Message DIAGCLIENT-4-MTS_SEND_FAILURE: MTS send failed, mts_opc: [chars], dest slot: [dec], dest SAP: [dec], error-id: [hex]
Explanation MTS send reports failure
Recommended Action No action is required.
Error Message DIAGCLIENT-5-CALLOC_FAILURE: Memory allocation failed
Explanation DiagClient process could not allocate memory
Recommended Action No action is required.
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_FINISH: Module [dec]: Ondemand test [chars] finished
Explanation Informational Syslog
Recommended Action No action is required.
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_START: Module [dec]: Ondemand test [chars] started
Explanation Informational Syslog
Recommended Action No action is required.
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_STOP: Module [dec]: Ondemand test [chars] stopped
Explanation Informational Syslog
Recommended Action No action is required.
Error Message DIAGCLIENT-5-DIAG_SCHED_COMPLETE: Module <[dec]> Test <[chars]> has completed Scheduled Testing
Explanation A scheduled Test was completed
Recommended Action No action is required.
Error Message DIAGCLIENT-5-ONDEMAND_FAIL: Module <[dec]> Test <[chars]> has failed in Test_Iteration <[chars]>
Explanation The specified test has reported FAILURE in this Iteration
Recommended Action No action is required.
Error Message DIAGCLIENT-5-ONDEMAND_SUCCESS: Module <[dec]> Test <[chars]> has completed successfully in Test_Iteration <[chars]>
Explanation The specified test has reported SUCCESS in this Iteration
Recommended Action No action is required.
Error Message DIAGCLIENT-7-DIAG_HM_FAIL: Module <[dec]> Health Monitoring Test <[chars]> has failed. Please use 'show diagnostic result
Explanation A Health Monitoring Test has reported failure
Recommended Action Ensure the line card is firmly in the slot, reseat if necessary, and attempt to run the test again if the line card is not seated properly in the slot. If the line card was properly seated in the slot, copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information.
Error Message DIAGCLIENT-7-PER_PORT_TEST_FAIL: Module <[dec]> Test <[chars]> has failed on Ports <[chars]> Please use 'show diagnostic result
Explanation Per Port Test has failed on the above all ports
Recommended Action No action is required.
This section contains the DIAGMGR messages.
Error Message DIAGMGR-2-MTS_SEND_FAILURE: MTS send failed, mts_opc: [chars], dest slot: [dec], dest SAP: [dec], error-id: [hex]
Explanation MTS send reports failure
Recommended Action No action is required.
Error Message DIAGMGR-2-PSS_DELETE_FAILURE: Read from PSS failed on Module <[dec]>
Explanation Read operation from PSS store failed
Recommended Action No action is required.
Error Message DIAGMGR-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]>
Explanation Write operation on PSS store failed
Recommended Action No action is required.
Error Message DIAGMGR-3-DIAG_MAJOR_DEFECT: Module <[dec]> Test <[chars]> detected a Major Error Please use 'show diagnostic result
Explanation A major error was detected during diagnostic testing
Recommended Action Re-seat the card and retry the test. If the same result occurs after reseating the card and retrying the test, copy the error message exactly as it appears on the screen and gather the output of show tech-support and any other relevant information. Contact your technical support representative with the gathered information.
Error Message DIAGMGR-3-DIAG_MINOR_DEFECT: Module <[dec]> Test <[chars]> detected a Minor Error Please use 'show diagnostic result
Explanation A minor error was detected during diagnostic testing
Recommended Action Re-seat the card and retry the test. If the same result occurs after reseating the card and retrying the test, copy the error message exactly as it appears on the screen and gather the output of show tech-support and any other relevant information. Contact your technical support representative with the gathered information
Error Message DIAGMGR-3-GET_CURR_SLOT_FAIL: Failed to get the current slot for the process. Error:[chars]
Explanation The process initialization failed to get the current slot.
Recommended Action This is an informational message stating that a process initialization failure.
Error Message DIAGMGR-4-CURR_SLOT_OFFLINE: Recevied an LC offline event for the current slot:[dec]. Ignoring it
Explanation The process received an offline event for the slot it is running. Ignoring it.
Recommended Action This is an informational message stating that an unexpected event has been encountered.
Error Message DIAGMGR-4-DISRPT_TST_START: Starting Test <[chars]> on Module <[dec]> is Disruptive
Explanation Starting a Disruptive Test can disturb the system's normal functionality
Recommended Action Reset target module
Error Message DIAGMGR-4-FIXED_INTRVL_CHANGED: The users are not allowed to change monitoring interval of Test <[chars]>
Explanation The specified health monitoring test interval is not user-configurable and therefore cannot be changed
Recommended Action Nothing. The specific health monitoring interval is not user- configurable by design so nothing can be done to change the interval
Error Message DIAGMGR-5-BOOTUP_CONF: Diagnostic Bootup Level: <[chars]>
Explanation Current Diagnostic BootUp Level being configure or changed
Recommended Action No action is required.
Error Message DIAGMGR-5-CALLOC_FAILURE: Memory allocation failure
Explanation Memory allocation in a call to malloc/calloc has failed
Recommended Action No action is required.
Error Message DIAGMGR-5-CHANGE_ALWAYS_HM: Health Monitoring test <[chars]> in Module <[dec]> is a must run and cannot be modified
Explanation The specified health monitoring test must be run and cannot be disabled
Recommended Action Nothing. The specific health monitoring test cannot be disabled by design. The system is working properly.
Error Message DIAGMGR-5-HM_START: Health monitoring test <[chars]> for Module <[dec]>
Explanation Health Monitoring Test started
Recommended Action No action is required.
Error Message DIAGMGR-5-HM_STOP: Disabling health monitoring test <[chars]> for Module <[dec]>
Explanation Health Monitoring Test has been stopped It can be enabled through the diagnostic monitor..... command
Recommended Action No action is required.
Error Message DIAGMGR-5-INTRVL_INCORRECT: Monitoring Interval is less than minimum of [dec] seconds required for Module <[dec]> test <[chars]>
Explanation Health Monitoring cannot be enabled for the specified test because the interval for the test has been incorrectly set
Recommended Action The system is working properly and no user action is required. If you want to specify a smaller testing interval, the error message text provides the lowest possible configurable interval for the specified monitoring interval
Error Message DIAGMGR-5-MODULE_MISSING: Diagnostic command issued on non-existing Module <[dec]>
Explanation A line card could not be located in a slot where a diagnostic action was requested
Recommended Action Ensure the targeted line card is properly seated in the specified slot. If the line card is properly seated, ensure the correct slot was indicated in the command-line interface. If the line card is well-seated and the correct slot was specified, copy the error message exactly as it appears on the screen as well as the output of show tech-support and paste the output into a separate file. Contact your technical support representative with the gathered information
Error Message DIAGMGR-5-NONHM_AS_HM: The Test <[chars]> cannot be used as health monitoring test
Explanation Non-HM test cannot be scheduled to run as a Health Monitoring test
Recommended Action No action is required.
Error Message DIAGMGR-6-BOOTUP_DIAG_OK: Module <[dec]>: Passed Online Diagnostics
Explanation The diagnostic tests did not detect any error on the card.
Recommended Action This is an informational message stating that the line card passed the diagnostic tests.
Error Message DIAGMGR-6-BOOTUP_TEST_STARTED: Module <[dec]>: Running [chars] Diagnostics
Explanation Starting bootup testing for above module
Recommended Action No action is required.
This section contains the DIAG_PORT_LB messages.
Error Message DIAG_PORT_LB-2-FIPS_RANDOM_ERROR: Random Number Generation Failure
Explanation Random Number genration failed in FIPS module
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-L2ACLREDIRECT_LOOPBACK_TEST_FAIL: Module:[dec] Test:L2ACLRedirect Loopback failed [dec] consecutive times. Faulty module:[chars] [chars] Error:[chars]
Explanation L2ACLRedirect Loopback test failed on the module consecutively
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-LCM_RESP_SEND_FAILURE: LC Inserted request response send to Module Manager failed . Error:[chars]
Explanation Failed to send the response for LC insertion to Module Manager.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-LIF_GET_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed to get Diagnostic LIF id
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-MALLOC_FAILURE: [chars]([dec]) Memory allocation failed.
Explanation Port Loopback test process could not allocate memory
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-PORTLOOPBACK_TEST_FAIL: Module:[dec] Test:PortLoopback failed [dec] consecutive times. Faulty module:[chars] [chars] Error:[chars]
Explanation PortLoopback test failed on the module consecutively
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-PROC_INIT_FAILURE: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed in process initialization
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-REWRITE_ENGINE_LOOPBACK_TEST_FAIL: Module:[dec] Test:RewriteEngine Loopback failed [dec] consecutive times. Faulty module:[chars] [chars] Error:[chars]
Explanation Rewrite Engine Loopback test failed on the module consecutively
Recommended Action No action is required.
Error Message DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL: Module:[dec] Test:SnakeLoopback failed [dec] consecutive times. Faulty module:[chars] affected ports:[chars] Error:[chars]
Explanation Snake test failed on the module consecutively
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-DIAG_FWD_PATH_SETUP_FAILURE: [chars]. Module:[dec] Error:[chars].
Explanation Forwarding path setup for port loopback tests failed
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-DIAG_PKT_SEND_FAILURE: [chars]([dec]) [chars]. Error:[chars]
Explanation Port Loopback test process failed to send loopback packets.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-FSM_LIB_ERROR: [chars]([dec]) [chars]. Error:[chars]
Explanation Port Loopback test process failed in MTS API.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-GET_DIAG_BD_FAIL: [chars]([dec]) Failed to get the BD for Diag VLAN:[dec]. Error:[chars].
Explanation Failed to get the BD corresponding to the Diag VLAN
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-IFINDEX_LIB_FAILURE: [chars]([dec]) [chars] [chars]:[hex] [chars] [chars]
Explanation Port Loopback test process failed in if_index library API
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-INVALID_TEST_REQUEST: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to get test request info.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-INVALID_TEST_RUN: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to get the current test run information
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-PDB_LIB_API_ERROR: Failed to [chars]. Error:[dec].
Explanation The port loopback test was not able to get chassis info
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-PIXM_LIB_ERROR: [chars]([dec]) Failed to convert [chars]:[hex] to [chars]. Error:[chars]
Explanation Port Loopback test process failed to convert port ifindex <-> port index.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-PORT_CLIENT_LIB_ERROR: [chars]([dec]) [chars]. Error:[chars]
Explanation Port Loopback test process failed in Port Client API.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-RESULT_ADD_FAILURE: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to add the port test result
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-RESULT_SEND_FAILURE: [chars]([dec]) [chars]
Explanation Port Loopback test process failed to send the test results
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-RW_ENGINE_LOOPBACK_TEST_SPINE_PATH_FAIL: Module:[dec] Test:RewriteEngine Loopback Spine path:[dec] failed [dec] consecutive times. Error:[chars]
Explanation Rewrite Engine Loopback test failed on the spine path consecutively
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-SOCKET_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed in socket operations
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-STATS_LIB_ERROR: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed in stats infra lib API.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-TEST_RES_SEND_FAIL: Failed to send [chars] test results back to Diagnostics Infrastucture. Error:[chars].
Explanation The port loopback test was not able to send the test results
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-TIMER_LIB_ERROR: [chars]([dec]) [chars]
Explanation Port Loopback test process timer handling failure.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-VLAN_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed to get Diagnostic VLAN info
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-VQI_GET_FAIL: Failed to get the Diag VQi from XBM. Error:[chars]
Explanation Rewrite Engine Loopback test failed to get the Diag VQi from XBAR Mgr
Recommended Action No action is required.
Error Message DIAG_PORT_LB-3-XBM_CFG_REQ_FAIL: Failed to conigure the XBAR mask while running the RewriteEngineLoopback test. Error:[chars]. Module:[dec] could have gone offline
Explanation Rewrite Engine Loopback test failed to set the XBAR mask while running the test. The target module could have gone offline
Recommended Action No action is required.
Error Message DIAG_PORT_LB-4-MTS_LIB_ERROR: [chars]([dec]) [chars]. Warning:[chars]
Explanation Port Loopback test process failed in MTS API.
Recommended Action No action is required.
Error Message DIAG_PORT_LB-4-PORT_CFG_REQ_SEND: [chars]([dec]) Failed to send request to configure port ifindex:[dec] for port loopback test
Explanation Failed to configure/restore the port to do/cleanup port loopback testing
Recommended Action No action is required.
Error Message DIAG_PORT_LB-5-DIAG_PORT_LB_DISABLED: DIAG_PORT_LB Disabled
Explanation DIAG_PORT_LB Service Disabled
Recommended Action No action is required.
Error Message DIAG_PORT_LB-5-DIAG_PORT_LB_ENABLED: DIAG_PORT_LB Enabled
Explanation DIAG_PORT_LB Service nabled
Recommended Action No action is required.
This section contains the DPVM messages.
Error Message DPVM-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for [chars]
Explanation Memory allocation failed for size [dec] for [chars]
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.
Error Message DPVM-2-DPVM_DUPL_REJECT: [chars]
Explanation Rejected duplicate pwwn query
Recommended Action Dpvm overwrite-duplicate-pwwn
Error Message DPVM-3-DB_ERR: [chars]
Explanation An error occured during an DPVM database operation. [chars] indicates the reason for the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message DPVM-3-DDAS_MODE_INVALID: [chars]
Explanation DDAS mode Invalid. [chars]
Recommended Action Flip DDAS mode
Error Message DPVM-3-INIT_FAIL: [chars]
Explanation An error happened during DPVM Initialization. [chars] indicates the reason for 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.
Error Message DPVM-3-MTS_ERR: [chars]
Explanation An error occured in processing of an MTS message. [chars] indicates the error that occured
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.
Error Message DPVM-3-PSS_ERR: [chars]
Explanation An error occured during an DPVM PSS operation. [chars] indicates the PSS operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message DPVM-4-ACTIVATION_FAIL: [chars]
Explanation Activation of DPVM device mappings failed due to [chars]
Recommended Action Correct the error and reactivate database again
Error Message DPVM-4-FEATURE_DISABLED: [chars]
Explanation DPVM is unavailable and disabled now
Recommended Action No action is required.
Error Message DPVM-6-FEATURE_ENABLED: [chars]
Explanation DPVM is available and enabled now
Recommended Action No action is required.
Error Message DPVM-6-INFO: [chars]
Explanation An event happened that affects DPVM. [chars] indicates the event
Recommended Action No action is required.
This section contains the DSTATS messages.
Error Message DSTATS-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex]
Explanation Dstats process pss initialization failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_CREATE_FAIL: pss create runtime database failed due to error: [hex]
Explanation Dstats process pss create runtime database failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [hex]
Explanation Dstats process pss delete runtime entry key [hex] failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to error: [hex]
Explanation Dstats process pss set runtime max key failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to error: [hex]
Explanation Dstats process pss set runtime max value failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_OPEN_FAIL: pss open runtime database failed due to error: [hex]
Explanation Dstats process pss open runtime database failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to error: [hex]
Explanation Dstats process pss reload runtime database failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to uri:[chars] failed due to error: [hex]
Explanation Dstats process pss snapshot of runtime debug to uri [string] failed due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars] failed due to error: [hex]
Explanation Dstats process pss snapshot of runtime to uri [string] failed due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
Error Message DSTATS-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex] failed due to error: [hex]
Explanation Dstats process pss store runtime entry key [hex] value [hex] failure due to error [hex].
Recommended Action Collect more information using command 'show flash'. See pss system error codes for reason.
This section contains the DT_HELPER messages.
Error Message DT_HELPER-2-MALLOC_FAILURE: Memory allocation failed
Explanation GOLD Test Helper process could not allocate memory
Recommended Action No action is required.
This section contains the ECHAT messages.
Error Message ECHAT-2-ECHAT_STATUS: TEST: [chars].
Explanation ECHAT status is reported as [chars].
Recommended Action No action is required.
Error Message ECHAT-3-ECHAT_INVALID_ADV: Received an invalid advertisement from Jabber ID: [chars].
Explanation Received an invalid advertisement
Recommended Action No action is required.
Error Message ECHAT-3-ECHAT_INVALID_SUMM_POLICY: Received and invalid summarization policy.
Explanation Summarization policy is invalid
Recommended Action No action is required.
Error Message ECHAT-5-ECHAT_CE_OFFLINE: Jabber ID [chars] has gone offline.
Explanation Received presence information
Recommended Action No action is required.
Error Message ECHAT-5-ECHAT_CE_ONLINE: Jabber ID [chars] has come online.
Explanation Received presence information
Recommended Action No action is required.
Error Message ECHAT-5-ECHAT_CHANGED_SUMM_POLICY: Summarization policy has been changed.
Explanation Summarization policy has been changed
Recommended Action No action is required.
Error Message ECHAT-5-ECHAT_SEQUENCE_SYNC: Received a sequence number out of sync from Jabber ID: [chars].
Explanation Received an out of sync sequence number
Recommended Action No action is required.
Error Message ECHAT-6-ECHAT_TOPO_CHANGE: Topology change caused by advertisement from Jabber ID: [chars].
Explanation Graph topology has been changed
Recommended Action No action is required.
This section contains the ELTMC messages.
Error Message ELTMC-SLOT#-2-ELTMC_GENERIC_DEBUG: [chars]
Explanation Logging some generic debugging info
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTERFACE_INTERNAL_ERROR: Internal error: [chars]:[chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_FOUND: Interface [chars] not found in ELTM database [chars]
Explanation ELTM database doesn't have the interface.
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_SUPP: Interface [chars] not supported by ELTM [chars]
Explanation ELTM doesn't support the interface for the specified operation
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTF_TO_LTL: Failed to get LTL for interface [chars] return status [chars]
Explanation ELTM Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_INTF_TO_SLOT: Failed to get slot for interface [chars] return status [chars]
Explanation ELTM Failed to get Slot for interface. Port-channels and L2 Learning might be effected
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_INTF: Failed to allocate L2 LIF entries in forwarding engine for interfac [chars]
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_VDC: Failed to allocate L2 LIF entries in forwarding engine
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding in this VDC
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_REALLOC_FAIL_INTF: Failed to realloc L2 LIF entries in forwarding engine for interface [chars]
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface. ISSU failed for certain interfaces
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_L3_INGRESS_LIF_ALLOC_FAIL_INTF: Failed to allocate L3 Ingress LIF entries in forwarding engine for interfac [chars]
Explanation ELTM Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect Layer 3 forwarding for the interface
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_LDB_REALLOC_FAIL: Failed to realloc LDB in forwarding engine for interface [chars] for non-XL linecard
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Shutdown the interfaces
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_LTL_ISSUE_EXT_COMP: Critical LTL clean-up issue (either ETHPM/PIXM) [chars]
Explanation LTL didnt get cleaned-up either bcos of ETHPM not sending DELETE or PIXM issuing a duplicate LTL
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_NONXL_LDB_REALLOC_FAIL: Failed to realloc LDB in forwarding engine for certain interfaces for non-XL linecard
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Shutdown the interfaces
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_RSVD_VLAN: Failed to get the reserved vlans. Failed with error [chars]
Explanation ELTM Failed to get the reserved vlan's. This will effect multicast forwarding on SVI interfaces
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_VDC_LIF_REALLOC_FAIL: Failed to realloc LDB in forwarding engine for vdc [dec]. Reload VDC after config reduction
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Remove the interfaces and then reload VDC
Recommended Action No action is required.
Error Message ELTMC-SLOT#-2-ELTMC_VLAN_INTERNAL_ERROR: Internal error: VLAN [dec]:[chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
This section contains the ELTM messages.
Error Message ELTM-2-INTERFACE_INTERNAL_ERROR: Internal error: [chars]:[chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message ELTM-2-INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message ELTM-2-INTF_NOT_FOUND: Interface [chars] not found in ELTM database [chars]
Explanation ELTM database doesn't have the interface.
Recommended Action No action is required.
Error Message ELTM-2-INTF_NOT_SUPP: Interface [chars] not supported by ELTM [chars]
Explanation ELTM doesn't support the interface for the specified operation
Recommended Action No action is required.
Error Message ELTM-2-INTF_TO_LTL: Failed to get LTL for interface [chars] return status [chars]
Explanation ELTM Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine
Recommended Action No action is required.
Error Message ELTM-2-QINQ_TRANSIT_ENABLE: ELTM Failed to set/reset qinq_transit_enable
Explanation ELTM Failed to set/reset qinq_transit_enable
Recommended Action No action is required.
Error Message ELTM-3-OTV_FEATURE_FAIL: Feature OTV failed : [chars]
Explanation Error in ELTM while handling feature OTV request from OIM
Recommended Action No action is required.
Error Message ELTM-5-EXT_COMP_ERR: [chars] component error [chars]
Explanation Recently applied Multicast config on the interface was unsuccessful, so reverting to the old state (before config)
Recommended Action No action is required.
Error Message ELTM-6-SVI_LIF_NOT_PRESENT: [chars]:[chars], collect output of show tech-support eltm/vlan/interface-vlan
Explanation Mismatch between SVI and vlan-mgr.
Recommended Action No action is required.
This section contains the EOU messages.
Error Message EOU-2-PBACL_APPLICATION_FAILURE: [chars] of host [chars] to/from pbacl group [chars] failed. Error : [chars]
Explanation Failure of host addition/deletion to/from pbacl group
Recommended Action Please verify the addition/deletion of the host using the cli "show object-group". If it was a delete request that failed, manual deletion of the host from the group is recommended
Error Message EOU-5-L2NAC_DISABLED: EOU Disabled
Explanation Service EOU Disabled
Recommended Action No action is required.
Error Message EOU-5-L2NAC_ENABLED: EOU Enabled
Explanation Service EOU enabled
Recommended Action No action is required.
Error Message EOU-6-AAA_DOWN: Default Policy ip: [chars]:retained
Explanation Policy retained
Recommended Action No action is required.
Error Message EOU-6-AUTHTYPE: Authtype: ip: [chars] Authtype:[chars]
Explanation Authentication type
Recommended Action No action is required.
Error Message EOU-6-BAD_PKT: Bad Packet: ip: [chars] Why: [chars]
Explanation Bad Packet because of reason specified
Recommended Action No action is required.
Error Message EOU-6-CTA: CTA: ip: [chars] status(detected/not detected): [chars]
Explanation CTA detected or not
Recommended Action No action is required.
Error Message EOU-6-IDENTITY_MATCH: Identity Match: ip: [chars] Policy: [chars]
Explanation Identity Matched or not
Recommended Action No action is required.
Error Message EOU-6-PBACL_APPLICATION_STATUS: [chars] of host [chars] to/from pbacl group [chars] succeeded
Explanation Status of host addition/deletion to pbacl group
Recommended Action No action is required.
Error Message EOU-6-POLICY: Policy on ip: [chars]: [chars]: [chars]
Explanation Policy applied
Recommended Action No action is required.
Error Message EOU-6-POSTURE: Posture:ip: [chars] Status: [chars], Interface: [chars]
Explanation Posture of host
Recommended Action No action is required.
Error Message EOU-6-SESSION: Session ip: [chars] Action:[chars] , Interface: [chars]
Explanation Session detected
Recommended Action No action is required.
Error Message EOU-6-SOCKET: Service eou on port: [dec]
Explanation Eou using above port
Recommended Action No action is required.
Error Message EOU-6-SQ_EAP_MSG: Status Query: ip: [chars] status: [chars]
Explanation Status query state
Recommended Action No action is required.
Error Message EOU-6-UNKN_EVENT_ERR: Unknow Event Err: ip: [chars] Message: [chars]
Explanation Error due to unknown event
Recommended Action No action is required.
Error Message EOU-6-VERSION_MISMATCH: Eou version mismatch ip: [chars] and version [dec]
Explanation Eou version mismatch
Recommended Action No action is required.
Error Message EOU-7-EOU_DISABLED_INTF: eou disabled on interface [chars]
Explanation Eou service disabled on interface
Recommended Action No action is required.
Error Message EOU-7-EOU_ENABLED_INTF: eou enabled on interface [chars]
Explanation Eou service enabled on interface
Recommended Action No action is required.
This section contains the EPP messages.
Error Message EPP-5-EPP_FAILURE: Interface [chars] EPP Failure
Explanation Trunk protocol failed
Recommended Action 'show epp internal event-history err' will indicate the errors encountered
Error Message EPP-5-EPP_LOOPBACK: Interface [chars] is looped back to the same switch
Explanation The interface is looped back to another interface on the same switch
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch
Error Message EPP-5-EPP_TRUNK_PROTOCOL_STATUS: epp trunk protocol is [chars] on switch
Explanation Epp trunk protocol enabled/disabled on the switch
Recommended Action No action is required.
This section contains the ETH-PORT-SEC messages.
Error Message ETH-PORT-SEC-2-ETH_PORT_SEC_ADDR_SEEN: MAC address already secured on peer-switch. Please re-configure after VPC comes up, if this interface is supposed to be a VPC PO
Explanation Mac already secured on peer
Recommended Action No action is required.
Error Message ETH-PORT-SEC-2-ETH_PORT_SEC_MISCONFIG: MAC Addresses present exceed the allowed number of MAC addresses on Port [chars]. Fix the inconsistency on this port.
Explanation MAC Addresses present exceed the allowed number of MAC addresses.
Recommended Action No action is required.
Error Message ETH-PORT-SEC-2-ETH_PORT_SEC_REGMAC_ADD_FAIL: Unable to add regmac [chars] for <[chars], vlan [dec]> since it is already registered for <[chars], vlan [dec]>
Explanation Duplicate regmac detected
Recommended Action No action is required.
Error Message ETH-PORT-SEC-2-ETH_PORT_SEC_SECURITY_VIOLATION: Triggered violation [chars] on Port [chars]
Explanation Violation action triggered on port due to security violation.
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_CONFIG_MAC_FAILED: Failed to configure MACs
Explanation Failed to configure MACs
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_INVALID_VLAN: Invalid VLAN configuration
Explanation Invalid VLAN configuration
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_PKTSENDFAIL: Failed to send packet, - [chars]
Explanation Failed to send packet. [char] identifies the reason.
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_SECURITY_VIOLATION_ANOTHER_PORT: Host [chars] bound to Port [chars] in Vlan [dec] is trying to access Port [chars] in Vlan [dec]
Explanation Moved the port to violation state due to a mac address seen on one port being seen on another
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_SECURITY_VIOLATION_MAX_MAC_VLAN: Port [chars] moved to [chars] state as host [chars] is trying to access the port in vlan [dec]
Explanation Moved the port to violation state due to exceeding address count
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_UNABLE_TO_DISABLE: Unable to disable eth_port_sec [chars].
Explanation Unable to disable eth_port_sec Service
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_UNABLE_TO_ENABLE: Unable to enable eth_port_sec [chars].
Explanation Unable to enable eth_port_sec Service
Recommended Action No action is required.
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_VIOL_UPDATE_FAILED: Failed to update violation mode
Explanation Failed to update violation mode
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_AGE_TIME_EXPIRY: Age Time expired for host [chars] in VLAN [dec] in port [chars]
Explanation Age time expired for host
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_DISABLED: eth_port_sec Disabled on if_index:[hex]
Explanation Eth_port_sec Service Disabled
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_DYNAMIC_MAC_ADDRESS_CLEARED: Dynamic MAC addresses for port [chars] cleared
Explanation Dynamic MAC address for port cleared
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_ENABLED: eth_port_sec Enabled on if_index:[hex]
Explanation Eth_port_sec Service Enabled
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_HOST_ADDITION: A new Host [chars] learnt on Port [chars] in Vlan [dec]
Explanation A new host is learnt on a port
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_HOST_DELETION: Host [chars] bound to secure port [chars] in Vlan [dec] has been removed
Explanation A host has been removed
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_INITFAIL: Eth Port Security Initialization failed: [chars]
Explanation Eth Port Security Initialization failed.[chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_MAX_LIMIT_EXCEED: Max Addr per port config cannot be accepted as it will violate the System Max limit. [chars]
Explanation System wide Max Limit Exceeds
Recommended Action No action is required.
This section contains the ETHPORT messages.
Error Message ETHPORT-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.
Error Message ETHPORT-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 'no shutdown' on the interface or removing and re-inserting the fibre optic cable.
Error Message ETHPORT-2-IF_ERROR_SHUT_LAN_NO_DCX: Shutting lan on interface [chars] that doesn't connect to a DCBX capable adaptor.
Explanation Shutting lan on interface that doesn't connect to a DCBX capable adaptor.
Recommended Action No action is required.
Error Message ETHPORT-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
Error Message ETHPORT-2-SYSLOG_ETHPM_CRITICAL: Critical failure: [chars]
Explanation There was a critical failure in the component.
Recommended Action Please collect system tech-support
Error Message ETHPORT-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 PortChannel interface that it belongs to
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported
Explanation The transceiver for the interface specified in the error 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
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-4-INVALID_MACADDR: Interface [chars] rejected IPv6-embedded mac [chars] config
Explanation The IPv6 derived mac-address is an invalid one.
Recommended Action No action is required.
Error Message ETHPORT-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]
Explanation Interface is admin up
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down)
Explanation Interface has been configured to be administratively down
Recommended Action Perform 'no shutdown'
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel admin down)
Explanation This interface belongs to a PortChannel and the PortChannel is configured to be administratively down
Recommended Action Perform 'no shutdown' on the PortChannel interface that it belongs to
Error Message ETHPORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface [chars] is down (Channel membership update in progress)
Explanation The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel
Recommended Action Retry the configuration again
Error Message ETHPORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to domain id assignment failure)
Explanation Isolated due to a failure while assigning a domain
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars] is down (Isolation due to domain manager other side not responding)
Explanation Remote end domain manager not responding
Recommended Action No action is required.
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars] is down (Isolation due to domain other side eport isolated)
Explanation Isolating this interface due to the remote end being isolated
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port src interface down)
Explanation Ethernet link to which the FCIP interface is bound is down
Recommended Action Ensure that the ethernet cable is connected, the interface is administratively enabled
Error Message ETHPORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port src interface link down)
Explanation Ethernet link to which the FCIP interface is bound is down
Recommended Action Ensure that the ethernet cable is connected and the remote end is also active
Error Message ETHPORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not present)
Explanation The FCOT has been removed
Recommended Action Insert an FCOT
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)
Explanation The module's hardware has failed
Recommended Action Collect more information about failed module using command 'show module internal all module'
Error Message ETHPORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive)
Explanation The port VSAN has been suspended or deleted
Recommended Action Assign a new active port VSAN to the interface
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down (Error disabled - Incompatible admin port mode)
Explanation The configured mode is not supported on this interface
Recommended Action Perform a 'show port internal info' to determine the list of modes supported on this interface
Error Message ETHPORT-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'
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)
Explanation The configured receive buffer size is not supported
Recommended Action Get the allowed receive buffer size from 'show port internal info'
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down (Error disabled - Incompatible admin port speed)
Explanation The configured speed is not supported on this interface
Recommended Action Perform a 'show port internal info' to determine the range of speed supported on this interface
Error Message ETHPORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down (Initializing)
Explanation The interface is in the process of coming up
Recommended Action If the interface is stuck in this state for a while, check the output of 'show port internal event-history' to determine what it is waiting for
Error Message ETHPORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)
Explanation Interface removed
Recommended Action No action is required.
Error Message ETHPORT-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
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down (Isolation due to port loopback to same switch)
Explanation The interface is looped back to another interface on the same switch
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch
Error Message ETHPORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module removed)
Explanation Interface is down because the module was removed
Recommended Action No action is required.
Error Message ETHPORT-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
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down)
Explanation Parent interface is down
Recommended Action No action is required.
Error Message ETHPORT-5-IF_DOWN_PARENT_DOWN: Interface [chars] is down (Parent interface is down)
Explanation The physical link on the parent interface has gone down
Recommended Action No action is required.
Error Message ETHPORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. closed by peer)
Explanation The FCIP peer connected to this interface closed the TCP connection
Recommended Action This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down (No operational members)
Explanation This is a PortChannel interface and all its members are operationally down
Recommended Action Enable at least one of the PortChannel's members
Error Message ETHPORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to port vsan mismatch)
Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and perform a 'shutdown' and a 'no shutdown'
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port software failure)
Explanation The software servicing the data path on the port has failed
Recommended Action No action is required.
Error Message ETHPORT-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
Error Message ETHPORT-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.
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode)
Explanation This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel
Recommended Action Change the mode and the trunking mode of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed)
Explanation This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel
Recommended Action Change the speed of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down (Suspended due to incompatible remote switch WWN)
Explanation This interface belongs to a PortChannel and 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
Error Message ETHPORT-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
Error Message ETHPORT-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:traceroute ipaddr
Error Message ETHPORT-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:traceroute ipaddr
Error Message ETHPORT-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:traceroute ipaddr
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to vsan mismatch)
Explanation This is a trunking interface and the VSANs configured 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
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is down (Isolation due to remote zone server not responding)
Explanation Isolated due to remote zone server not responding
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_PEER_LINK_DELAY_TIMER_OFF: The delay timer for peer-link [chars] has been turned off
Explanation The bringup delay timer for the peer-link has been turned off as a result of which the peer-link bringup will be resumed
Recommended Action No action is required.
Error Message ETHPORT-5-IF_PEER_LINK_DELAY_TIMER_ON: The delay timer for peer-link [chars] has been turned on
Explanation The bringup delay timer for the peer-link is on as a result of which the peer-link bringup will be delayed with the delay indicated by the configured value of the timer. Execute \show vpc\ to find out how much time is remaining
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-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
Error Message ETHPORT-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up
Explanation Interface [chars] is trunking, VLANs [chars] are up
Recommended Action No action is required.
Error Message ETHPORT-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.
Error Message ETHPORT-5-IF_UP: Interface [chars] is up [chars]
Explanation Interface is up in mode specified, if applicable
Recommended Action No action is required.
Error Message ETHPORT-5-SPEED: Interface [chars], operational speed changed to [chars]
Explanation Operational speed has changed when link came up
Recommended Action No action is required.
Error Message ETHPORT-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
Error Message ETHPORT-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.
Error Message ETHPORT-5-SYSTEM_INTERFACE_SHUTDOWN: The physical interfaces are being brought down as VDC going into maintenance mode
Explanation The physical interfaces are being brought down as VDC going into maintenance mode
Recommended Action No action is required.
This section contains the ETH_PORT_CHANNEL messages.
Error Message ETH_PORT_CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed [[chars]]
Explanation Module configuration failed
Recommended Action Module will be automatically reset
Error Message ETH_PORT_CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec])
Explanation No enough memory
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for [chars] [[chars]]
Explanation Parameter mapping failed
Recommended Action Specified service is misbehaving; check its status
Error Message ETH_PORT_CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [chars]: [chars]
Explanation Failed to send a multicast message to all modules, usually because some module went down
Recommended Action Run show port-channel consistency to check consistency
Error Message ETH_PORT_CHANNEL-2-RESET_MODULE: reset module [dec] for not responding or returning error
Explanation A module is reset for not responding or returning error
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-3-ADD_REM_MEMBERS_FAILURE: [chars]
Explanation Some service(s) failed to add or remove ports to port-channel
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-ALL_DROP_TIMEOUT: Some component(s) (sap:[chars]) timed out on dropping notif:[chars] (for:[chars]); Please collect
Explanation Some component did not respond to a request in stipulated time.
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-CLEAR_PORT_CLIENT_STATS_FAILURE: [chars]
Explanation Failed to clear stats for port [chars] err: [hex] ([chars])
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible
Explanation Compatibility check failed when adding ports to port-channel
Recommended Action Make sure the compatibility parameters are consistent while adding ports to port-channel, or use force option
Error Message ETH_PORT_CHANNEL-3-GENERAL_ERROR: [chars]
Explanation General error
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-3-MINLINK_REQ_NOT_MET_DUE_TO_BFD_CHANNEL_REINIT: [chars] does not meet min-link requirement based on BFD state. Reinit port-channel
Explanation Port-channel does not meet min-link requirement based on BFD state
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Explanation Failed to send a message
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-3-NUM_ACTIVE_PORTS_ERROR: Port-channel:[chars] active_nports [dec]; No member is active; Please collect
Explanation Port-channel num active ports error
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-PCM_HWCFG_FAIL_ERROR: Port-channel:[chars] mbr:[chars] SAP [dec] returned error [chars] for opc [chars]; if lacp port-channel please collect
Explanation Port-channel hwcfg fail error
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-PCM_INTERNAL_ERROR: Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect
Explanation Port-channel internal error
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-PCM_PORT_DEL_IN_PC_UP_ERROR: Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect
Explanation Port-channel port del in pc_up. Shut resp recvd before bundle member down
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-PCM_PORT_DOWN_IN_PC_UP_ERROR: Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect
Explanation Port-channel port down in pc_up. No bundle member down
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found
Explanation Cannot find port-channel in its database, which indicates an inconsistency with an external component
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-3-RESOURCE_ALLOC_FAILED_PORT_CHANNEL_DELETED: [chars] deleted
Explanation Port-channel deleted from running config
Recommended Action May need to re-configure the port-channel and its members
Error Message ETH_PORT_CHANNEL-3-RSP_TIMEOUT: Component [chars] timed out on response to opcode:[chars] (for:[chars])
Explanation Some component did not respond to a request in stipulated time.
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-SHADOW_MBR_CHANGE_FAILURE: [chars]
Explanation Some service failed shadow member change to port-channel
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-SHADOW_PC_CREATE_FAILURE: [chars]
Explanation Some service failed shadow port-channel create
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-SHADOW_PC_DELETE_FAILURE: [chars]
Explanation Some service failed shadow port-channel delete
Recommended Action None
Error Message ETH_PORT_CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], state [chars]]
Explanation Some operation timed out
Recommended Action Run show port-channel consistency to check all module connectivity and consistency
Error Message ETH_PORT_CHANNEL-4-PORT_CFG_DELETED: [chars] removed from [chars] (different module inserted)
Explanation Port is removed from a port-channel because a different module was inserted to the same slot
Recommended Action You lost some ports from port-channel, check if you want to add ports in the new module to the same port-channel.
Error Message ETH_PORT_CHANNEL-4-PORT_CHANNEL_RANGE: The total number of port channels configured in the range exceeds maximum: [dec].
Explanation The total number of port channels configured in the range exceeds maximum
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-4-PORT_CHANNEL_RESTORE: The total number of port channels restored: [dec] exceeds maximum: [dec]. This may corrupt TCAM entries. Please reduce port channel number to no greater than maximum.
Explanation The total number of port channels restored exceeds maximum
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally individual
Explanation The port is operating as an individual link even though it is locally or remotely configured to be part of a port channel
Recommended Action Check the configuration of the port locally and remotely to ensure that it can operate as part of a port channel
Error Message ETH_PORT_CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of port-channel
Explanation Cannot find the port in port-channel database, which indicates an inconsistency with an external component
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-4-RACE_WARN: [chars]
Explanation Warning of possible race condition
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from [chars]
Explanation Received an unexpected response and discarded
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Explanation Auto create process on the port failed
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-CREATED: [chars] created
Explanation A port-channel is created
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-DELETED: [chars] deleted
Explanation A port-channel is deleted
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-FOP_CHANGED: [chars]: first operational port changed from [chars] to [chars]
Explanation The first operational port in a port-channel is changed
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode
Explanation Compatibility check failed when adding ports to port-channel
Recommended Action Make sure the compatibility parameters are consistent between the ports and the port-channel
Error Message ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed
Explanation Operational compatibility check failed on the port in a port-channel
Recommended Action Make sure the compatibility parameters are consistent between the ports and the port-channel
Error Message ETH_PORT_CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come online because port channel interface
Explanation The port-channel number configured on the switch is larger than 128
Recommended Action Delete the set of port channel interface
Error Message ETH_PORT_CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Explanation Ports are added to a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_CHANNEL_DELAYED_LACP: [chars]: port-channel is up with member [chars] in delayed-lacp mode
Explanation Port-channel is up in delayed-lacp mode
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_CHANNEL_LACP_MODE: [chars]: [chars]
Explanation Port-channel is coming up in lacp mode
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Explanation Port goes down in a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY_DOWN: [chars]: hot-standby port [chars] is down
Explanation Port-channel hot-standby member goes down
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY: [chars]: [chars] goes to hot-standby
Explanation Port goes to hot-standby in a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN: individual port [chars] is down
Explanation Port-channel member operating in individual mode goes down
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Explanation Ports are removed from a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_SUSPENDED: [chars]: [chars] is suspended
Explanation Port is suspended in a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_UP: [chars]: [chars] is up
Explanation Port comes up in a port-channel
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-5-PORT_WAIT_BFD: [chars] waiting for BFD session to get established
Explanation Port waiting for BFD session establishment
Recommended Action None
Error Message ETH_PORT_CHANNEL-5-SUBGROUP_ID_CHANGE: Interface [chars] in port-channel[dec] subgroup-id changed from [dec] to [dec]
Explanation The port's subgroup-id got changed
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-6-RESYNC: resyncing [chars] with all modules
Explanation Resync modules with sup after an error or switchover
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-GSYNC_DONE: global synchronization is done
Explanation Port-channel manager finished global synchronization
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-GSYNC_REQ: requesting global synchronization
Explanation Port-channel manager requested a global synchronization from active sup
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-START_ACTIVE: started in active mode
Explanation Port-channel manager started in active mode
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-START_DEFAULT: started with default configuration
Explanation Port-channel manager started with default configuration
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-START_STANDBY: started in standby mode
Explanation Port-channel manager started in standby mode
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-START_STATEFUL: started statefully
Explanation Port-channel manager started with running configuration
Recommended Action No action is required.
Error Message ETH_PORT_CHANNEL-7-START_STATELESS: started statelessly
Explanation Port-channel manager started with startup configuration
Recommended Action No action is required.
This section contains the EVMC messages.
Error Message EVMC-3-MTS_OPERATION_FAILED: [chars]([dec]): [chars]
Explanation Internal IPC operation failed in Event Manager Client
Recommended Action No action is required.
Error Message EVMC-4-ACTION_CFG_MONITOR_COLLECT: [chars]([dec]): Action configuration disallowed for Monitor Collect Policy
Explanation Configuring Policy Action for Monitor Collect Policy isnot allowed and hence, has been rejected
Recommended Action No action is required.
Error Message EVMC-5-AVL_CREATE_FAIL: [chars]([dec]): AVL Tree creation failure
Explanation Event Manager could not initialize local policy store
Recommended Action No action is required.
Error Message EVMC-5-MALLOC_FAILURE: [chars]([dec]): Memory allocation failure
Explanation Event Manager Client process could not allocate memory
Recommended Action No action is required.
Error Message EVMC-5-RT_PSS_OP_FAILURE: [chars]([dec]): Failed to [chars]. Error:[chars]
Explanation Event Manager Client could not access HA store
Recommended Action No action is required.
This section contains the EVMED messages.
Error Message EVMED-2-EVMED_PSS_DELETE_FAILURE: Delete from PSS failed
Explanation Delete from PSS failed
Recommended Action No action is required.
Error Message EVMED-2-EVMED_PSS_WRITE_FAILURE: Write to PSS failed
Explanation Write to PSS failed
Recommended Action No action is required.
Error Message EVMED-5-EVMED_DISABLED: Event Detectors Disabled
Explanation Event manager event detector service disabled
Recommended Action No action is required.
Error Message EVMED-5-EVMED_ENABLED: Event Detectors Enabled
Explanation Event manager event detector service enabled
Recommended Action No action is required.
This section contains the EXAMPLE_TEST messages.
Error Message EXAMPLE_TEST-5-EXAMPLE_TEST_DISABLED: EXAMPLE_TEST Disabled
Explanation EXAMPLE_TEST Service Disabled
Recommended Action No action is required.
Error Message EXAMPLE_TEST-5-EXAMPLE_TEST_ENABLED: EXAMPLE_TEST Enabled
Explanation EXAMPLE_TEST Service nabled
Recommended Action No action is required.
This section contains the EXCEPTIONLOG messages.
Error Message EXCEPTIONLOG-SLOT#-2-LC_EXP_MSG: Linecard exception: [chars] is the affected Port bit map. [dec] Additional information - [chars]
Explanation LC Exception event.
Recommended Action No action is required.
This section contains the EX_SYSLOG messages.
Error Message EX_SYSLOG-0-EMER_MSG: Emergency Message - [dec]
Explanation A Dummy emergency message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-1-ALERT_MSG: Alert Message - [chars] [dec]
Explanation A Dummy alert message to test syslogd from ex_syslog. [chars] is the a dummy text. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-2-CRIT_MSG: Critical Message - [dec]
Explanation A Dummy critical message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-3-ERR_MSG: Error Message - [dec]
Explanation A Dummy error message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-4-WARNING_MSG: Warning Message - [dec]
Explanation A Dummy warning message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-5-NOTICE_MSG: Notice Message - [dec]
Explanation A Dummy notice message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-6-INFO_MSG: Info Message - [dec]
Explanation A Dummy info message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
Error Message EX_SYSLOG-7-DEBUG_MSG: Debug Message - [dec]
Explanation A Dummy debug message to test syslogd from ex_syslog. [dec] is the message count
Recommended Action No action is required.
This section contains the FCDOMAIN messages.
Error Message FCDOMAIN-2-DOMS_CONFLICT: Conflict detected: ([dec]) domain ID [dec] WWN [chars]
Explanation Conflict detected ([dec]) domain ID [dec] with WWN [chars].
Recommended Action Check which switches have the same WWN and change either one; then change either's domain ID.
Error Message FCDOMAIN-2-EPORT_ISOLATED: Isolation of interface [chars] (reason: [chars])
Explanation Fcdomain has isolated interface [chars] (reason: [chars].) Perform a show interface. Based on the reason specified, you might have to ensure domains are adequate and unique in the VSAN and perform a disruptive restart [fcdomain restart disruptive vsan
Recommended Action No action is required.
Error Message FCDOMAIN-2-FC2BIND_FAILED: Bind to FC2 Service failed
Explanation Fcdomain has not been able to contact the FC2 module.
Recommended Action No action is required.
Error Message FCDOMAIN-2-FC2_INITIALIZATION_FAILED: FC initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence with the Fibre Channel subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.
Recommended Action No action is required.
Error Message FCDOMAIN-2-FC2_SET_SOCKOPT_DM_SOCK_FAILED: set sockopt to FC2 Service failed
Explanation Fcdomain has not been able to setsockopt to the FC2 module.
Recommended Action No action is required.
Error Message FCDOMAIN-2-FCID_PERSISTENT_TBL_COMPLETELY_FULL: FCID persistent table is completely full
Explanation The FCID persistent table is full. Perform [show fcdomain fcid persistent vsan
Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries OR disable the feature on certain VSANs which are not critical enough [no fcdomain fcid persistent].
Error Message FCDOMAIN-2-HIGH_PRIORITY_MTSBIND_FAILED: Bind for high priority IPC failed
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module for its high priority queue.
Recommended Action No action is required.
Error Message FCDOMAIN-2-INITIALIZATION_FAILED: Initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.
Recommended Action No action is required.
Error Message FCDOMAIN-2-MTSBIND_FAILED: Bind to IPC failed
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module.
Recommended Action No action is required.
Error Message FCDOMAIN-2-MTSREGISTRATION_FAILED: Registration of opcodes with IPC Service failed
Explanation Fcdomain has not been able to register its messages with the Inter Process Communication (IPC) module.
Recommended Action No action is required.
Error Message FCDOMAIN-2-MTS_INITIALIZATION_FAILED: IPC initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence with the IPC (Inter Process Communication) subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.
Recommended Action No action is required.
Error Message FCDOMAIN-2-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch
Explanation It has been detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.
Recommended Action Check which switches have the same WWN and change either one; then change either's domain ID.
Error Message FCDOMAIN-2-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected conflict between two switches having the same non-virtual domain ID [dec] and the same WWN [chars]
Explanation It has been detected that two switches have the same non-virtual domain ID [dec] and the same WWN [chars].
Recommended Action Check which switches have the same WWN and change either one; then change either's domain ID.
Error Message FCDOMAIN-2-PSSBIND_FAILED: Bind to Persistent Storage Service failed
Explanation Fcdomain has not been able to contact the Persistent Storage Service (PSS).
Recommended Action No action is required.
Error Message FCDOMAIN-2-RDIRJT: Rejected request for domain ID [dec], WWN requestor [chars] reason code [dec] reason_code_expln [dec]
Explanation An invalid request for domain IDs has been rejected by fcdomain.
Recommended Action Perform [show fcdomain vsan
Error Message FCDOMAIN-2-SYSBIND_FAILED: Bind to System Manager service failed
Explanation Fcdomain has not been able to contact the System Manager.
Recommended Action No action is required.
Error Message FCDOMAIN-2-SYSMGR_INITIALIZATION_FAILED: System Manager initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence with the System Manager. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.
Recommended Action No action is required.
Error Message FCDOMAIN-3-COMMITERRORLOCALINVALIDALLOWEDDOMS: A remote switch attempted to locally apply an illicit allowed domains configuration
Explanation A remote switch attempted to locally apply an allowed domains configuration that doesn't include all currently assigned domains or the locally configured domain.
Recommended Action No action is required.
Error Message FCDOMAIN-3-COMMITERRORREMOTEINVALIDALLOWEDDOMS: A remote switch (domain ID [dec], WWN [chars]) refuses to locally apply the proposed allowed domains
Explanation The remote switch with domain ID [dec] and WWN [chars] refuses to locally apply the proposed allowed domains probably due to incompatibility with its local configured domain or the domain ID list.
Recommended Action Check the configuration on the remote switch, and make sure that the proposed allowed domains include it. Also, make sure that the the proposed allowed domains include all the domains in the domain ID list.
Error Message FCDOMAIN-3-MTSOPENTRX_FAILED: IPC failure (opening of a transaction failed)
Explanation Fcdomain was not able to open a transaction( HA Purposes.)
Recommended Action No action is required.
Error Message FCDOMAIN-3-MTSRECV_FAILED: IPC failure (receiving of a message failed)
Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive.)
Error Message FCDOMAIN-3-MTSRESP_FAILED: IPC failure replying to a request message (error [hex])
Explanation Fcdomain has not been able to reply to a request coming from the Inter Process Communication (IPC) module (error [hex]).
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive).
Error Message FCDOMAIN-3-MTSSENDREQ_FAILED: IPC failure (sending of a request failed)
Explanation Fcdomain was not able to send a request using the Inter Process Communication module.
Recommended Action Please perform [fcdomain restart vsan
Error Message FCDOMAIN-3-MTSSEND_FAILED: IPC failure (sending of a message (syserr [hex], opc [dec], mtsq [dec], sap.node [hex], sap_addr [dec]) failed)
Explanation Fcdomain has not been able to send a message to the Message Transactional Service (MTS).
Recommended Action Please perform [fcdomain restart vsan
Error Message FCDOMAIN-3-MTS_H_RECV_FAILED: IPC failure (receiving of a message failed)
Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive.)
Error Message FCDOMAIN-3-NVRAMFAILURE: NVRAM open failed
Explanation Reading the last assigned runtime domain IDs from Non Volatile RAM (NVRAM) failed.
Recommended Action Fcdomain is able to continue without access to the Non Volatile RAM (NVRAM.)
Error Message FCDOMAIN-3-PORT_SUSPENDED: Response (Cmd Code [hex]) for SWILS [hex] intended for [chars] is received on [chars]
Explanation An FC2 response frame (Command Code [hex]) for SWILS [hex] that was intended for interface [chars] has been received on [chars] instead.
Recommended Action Check the configuration of both interfaces on the local switch and the interfaces on the other side of their corresponding links. In particular, check whether they should all belong to the same port-channel.
Error Message FCDOMAIN-3-SDWRAPBIND_FAILED: Bind to debug server failed
Explanation Fcdomain feature has not been able to contact the debug service. Any problems occurring in the fcdomain feature will not be logged.
Recommended Action No action is required.
Error Message FCDOMAIN-3-SDWRAPHISTINIT_FAILED: Initialization of history message list failed.
Explanation Fcdomain feature has not been able to contact the debug history service. Any problems occurring in the fcdomain feature will not be logged to this debug history.
Recommended Action No action is required.
Error Message FCDOMAIN-3-VSAN_MERGE_DETECTED: Merge detected with VSAN [dec] (Common Fabric Name [chars])
Explanation The local VSAN and VSAN [dec] have the same principal switch [chars], hence are connected in the same logical fabric.
Recommended Action No action is required.
Error Message FCDOMAIN-4-DM_ALLOWED_DM_LIST_MOD_ON_SUBORDINATE: Allowed domain list for vsan [dec] modified on subordinate switch with fcdomain distribution enabled
Explanation When distribution is enabled, it is recommended to modify the allow domain list on the principal switch only.
Recommended Action Abort the current session on the local switch and start a new one on the principal switch.
Error Message FCDOMAIN-4-FABRICCONFSTARTRCF: Disruptive reconfiguration started
Explanation A disruptive reconfiguration (RCF phase) of the VSAN has started. This can happen when two or more fabrics merge disruptively, or when the user manually triggers a diruptive reconfiguration of the VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-4-FC2_CORRUPTED: Received malformed FC2 [chars] frame
Explanation Fcdomain received a malformed FC2-SWILS frame.
Recommended Action No action is required.
Error Message FCDOMAIN-4-FCID_PERSISTENT_TBL_ALMOST_FULL: FCID persistent table is almost full
Explanation Fcdomain has 80% or more of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan
Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries.
Error Message FCDOMAIN-4-SELECTIVE_RESTART_IN_INTEROP: Not all fcdomain optimizations are supported in interop VSANs. Selective-Restart disabled forcefully in VSAN [dec]
Explanation Selective-restart optimization is not supported in interop VSANs and disabled forcefully in affected VSAN
Recommended Action No action is required.
Error Message FCDOMAIN-5-DOMAIN_TYPE_IS_PREFERRED: The domain ID type is currently configured as preferred in all the existing VSANs
Explanation All the currently existing VSANs have the domain ID type configured as preferred. This means that with a low probability the domain ID of the local VSAN might change afer a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link.
Recommended Action Type [fcdomain domain
Error Message FCDOMAIN-5-FCIDP_DISABLED: FCID persistency feature is currently not enabled in any of the existing VSANs
Explanation All the currently existing VSANs have the FCID persistency feature disabled.
Recommended Action Type [fcdomain fcid persistent vsan
Error Message FCDOMAIN-5-FCID_PERSISTENT_TBL_HALF_FULL: FCID persistent table is half full
Explanation Fcdomain has 50% of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan
Recommended Action You may want to purge stale entries [purge fcdomain fcid] to obtain more free entries.
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSDATAREQUEST: Received CFS Data request from unknown domain [dec].
Explanation A CFS Data request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSLOCKREQUEST: Received CFS Lock request from unknown domain [dec].
Explanation A CFS Lock request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSRELEASEREQUEST: Received CFS Release request from unknown domain [dec].
Explanation A CFS Release request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Error Message FCDOMAIN-5-UNKNOWNDOMAININUNKNOWNCFSREQUEST: Received CFS request from unknown domain [dec].
Explanation A CFS request from the unknown domain [dec] has been received.
Recommended Action No action is required.
Error Message FCDOMAIN-6-BF_STARTED: BF started by [chars]
Explanation Build Fabric has been started in this VSAN
Recommended Action No action is required.
Error Message FCDOMAIN-6-CANNOTFREESINGLEFCID: Impossible to free single FCIDs
Explanation Impossible to free single FCIDs.
Recommended Action No action is required.
Error Message FCDOMAIN-6-CLEARLOCKNOTIFICATIONRECEIVED: Implict lock release.
Explanation Lock has been implicitly released due to a clear session operation.
Recommended Action No action is required.
Error Message FCDOMAIN-6-DEVICEALREADYOWNSDIFFERENTFCIDS: The device already owns different FCIDs
Explanation Requested different FCIDs without any freeing in between.
Recommended Action No action is required.
Error Message FCDOMAIN-6-DOMAINID_INVALID: Local domain ID invalid
Explanation The local domain ID is invalid.
Recommended Action No action is required.
Error Message FCDOMAIN-6-DOMAINID_VALID: Local domain ID [dec] available
Explanation The domain ID [dec] is available.
Recommended Action No action is required.
Error Message FCDOMAIN-6-DOWNSTREAM_SWITCHED: Downstream interface has been fast-switched from [chars] to [chars]
Explanation Because of a link failure the downstream interface has been fast-switched from [dec] to [dec].
Recommended Action No action is required.
Error Message FCDOMAIN-6-EPORT_ALREADY_CREATED: Interface [chars] already created
Explanation Interface [chars] already created.
Recommended Action No action is required.
Error Message FCDOMAIN-6-EPORT_ALREADY_DOWN: Interface [chars] is already down
Explanation Interface [chars] already down.
Recommended Action No action is required.
Error Message FCDOMAIN-6-EPORT_CLEANUP: Interface [chars] received cleanup request
Explanation Fcdomain on interface [chars] has received a cleanup request.
Recommended Action No action is required.
Error Message FCDOMAIN-6-EPORT_CREATED: Creation of interface [chars]
Explanation Fcdomain is going to create interface [chars].
Recommended Action No action is required.
Error Message FCDOMAIN-6-EPORT_DOWN: Interface [chars] is down
Explanation Fcdomain is going to remove interface [chars] from its database.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FABRICCONFSTARTBF: Non disruptive reconfiguration started
Explanation A non disruptive reconfiguration (BF phase) of the VSAN has started. This can happen when two or more fabrics merge, or when the user manually triggers a non diruptive reconfiguration of the VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FABRICNAME_INVALID: Fabric name not available
Explanation Fabric name not available.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FABRICNAME_VALID: Fabric name [chars] available
Explanation Fabric name [chars] available.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCIDALREADYFREE: FCIDs already free
Explanation FCIDs already free.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCIDNOTSTORED: FCIDs not stored
Explanation FCIDs not stored.
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCIDP_ENABLED_DOM_TYPE_PREFERRED: FCID persistency is enabled, but the domain ID type is configured as preferred
Explanation The FCID persistency feature is enabled, but the domain ID type is configured as preferred. This means that with a low probability the domain ID of the local VSAN might change afer a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link. Should the domain ID change, all the FCIDs associated with it would be invalidated.
Recommended Action Type [fcdomain domain
Error Message FCDOMAIN-6-FCIDS_ASSIGNED: Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex]
Explanation Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCIDS_FREED: Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex]
Explanation Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCID_ASSIGNED: Assigned single FCID [hex]:[hex]:[hex]
Explanation Assigned single FCID [hex]:[hex]:[hex].
Recommended Action No action is required.
Error Message FCDOMAIN-6-FCID_FREED: Freed single FCID [hex]:[hex]:[hex]
Explanation Freed single FCID [hex]:[hex]:[hex].
Recommended Action No action is required.
Error Message FCDOMAIN-6-INCORRECTDOMAINRANGE: Requested FCIDs with domain field not in expected range
Explanation Requested FCIDs with domain field not in expected range.
Recommended Action No action is required.
Error Message FCDOMAIN-6-INCORRECTDOMAIN: Requested FCIDs with domain field different from local domain
Explanation Requested FCIDs with domain field different from local domain.
Recommended Action No action is required.
Error Message FCDOMAIN-6-INVALIDARG: Requested FCID of type 00.00.YY, but specifying an entire area
Explanation Requested FCID of type 00.00.YY, but specifying an entire area.
Recommended Action No action is required.
Error Message FCDOMAIN-6-MY_SAME_WWN_DIFFERENT_DOMS_CONFLICTS: During VSAN merge detected local WWN [chars] is already in use by another switch (the two switches have different domain IDs: [dec] (local) and [dec])
Explanation It has been detected that the local switch has the same WWN [chars] of another switch, and that they have different domain IDs: [dec] (local) and [dec].
Recommended Action Check which switches have the same WWN and change either one.
Error Message FCDOMAIN-6-NODOMAIN: Local domain not available
Explanation The local domain is not available yet.
Recommended Action No action is required.
Error Message FCDOMAIN-6-NOFREEFCID: No free FCIDs
Explanation No free FCIDs.
Recommended Action No action is required.
Error Message FCDOMAIN-6-NOTOWNER: Feature [dec] cannot free FCID [dec]:[dec]:[dec] (feature [dec] is the actual owner)
Explanation Feature UUID [dec] cannot free FCID [dec]:[dec]:[dec] because it is not its owner (UUID actual owner is [dec]).
Recommended Action No action is required.
Error Message FCDOMAIN-6-OTHER_SIDE_VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected overlap with virtual IVR domain ID [dec] from across the link
Explanation It has been detected an overlap with the virtual IVR domain ID [dec] from across the link during an attempt to merge the local VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-6-PSWSSTARTED: Principal Switch Selection started
Explanation Fcdomain started a principal switch selection phase to elect a principal switch in this VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-6-RCF_STARTED: RCF started by [chars]
Explanation Reconfigure Fabric has been started in this VSAN
Recommended Action No action is required.
Error Message FCDOMAIN-6-REQSINGLEFCIDWITHINRESERVEDRANGE: Requested single FCIDs in area [dec] within the reserved range
Explanation Requested single FCIDs in area [dec] within the reserved range.
Recommended Action No action is required.
Error Message FCDOMAIN-6-REQUESTEDFCIDNOTFREE: Requested FCIDs not free
Explanation Requested FCIDs not free.
Recommended Action No action is required.
Error Message FCDOMAIN-6-REQUESTEDFCIDRESERVED: Requested reserved FCIDs
Explanation Requested reserved FCIDs.
Recommended Action No action is required.
Error Message FCDOMAIN-6-REQUESTEDRESERVEDFCIDMISMATCH: Requested persistent FCIDs, but there is a mismatch
Explanation Requested persistent FCIDs, but there is a mismatch.
Recommended Action No action is required.
Error Message FCDOMAIN-6-SAME_WWNS_DIFFERENT_DOMS_CONFLICTS: During VSAN merge detected two switches with same WWN [chars] and different non-virtual domain IDs [dec] and [dec]
Explanation It has been detected that two switches have the same WWN [chars], but different non-virtual domain IDs: [dec] and [dec].
Recommended Action Check which switches have the same WWN and change either one.
Error Message FCDOMAIN-6-TIMER_UNKNOWN: fcdomain has received a notification for an unknown timer expiration
Explanation A timer unknown to fcdomain has expired.
Recommended Action No action is required.
Error Message FCDOMAIN-6-UPSTREAM_SWITCHED: Upstream interface has been fast-switched from [chars] to [chars]
Explanation Because of a link failure the upstream interface has been fast-switched from [dec] to [dec].
Recommended Action No action is required.
Error Message FCDOMAIN-6-UUIDNOSPACEFOUND: No available space to store the identity of the requestor the FCIDs
Explanation No available space to store the identity of the requestor the FCIDs.
Recommended Action No action is required.
Error Message FCDOMAIN-6-UUIDNOTFOUND: Universal Unique ID (UUID) not found
Explanation Universal Unique ID (UUID) not found.
Recommended Action No action is required.
Error Message FCDOMAIN-6-VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected overlap with local virtual IVR domain ID [dec]
Explanation It has been detected an overlap with the local virtual IVR domain ID [dec] during an attempt to merge the local VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-7-EPORT_ALREADY_ISOLATED: Interface [chars] is already isolated or down
Explanation Fcdomain was going to isolate interface [chars], but the interface is already isolated.
Recommended Action No action is required.
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDBF: Non disruptive reconfiguration completed
Explanation A non disruptive reconfiguration (BF phase) completed. This can happen when two or more fabrics merged, or when the user manually triggered a non diruptive reconfiguration of the VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDRCF: Disruptive reconfiguration completed
Explanation A disruptive reconfiguration (RCF phase) of the VSAN has completed. This can happen when two or more fabrics merged disruptively, or when the user manually triggered a diruptive reconfiguration of the VSAN.
Recommended Action No action is required.
Error Message FCDOMAIN-7-FC2_RETRY: Retransmission of FC2 frame on interface [chars] (Cmd Code: [hex])
Explanation Fcdomain is retrying an FC2 frame on interface [chars] due to loss/no response. The Command Code of the frame is [hex].
Recommended Action No action is required.
Error Message FCDOMAIN-7-FCID_IN_USE_PURGING_FOR_FICON_MGR: FICON needs to purge the persistent FCID table, but at least one FCID is still in use, preventing this purge from completely remove all entries belonging to the VSAN.
Explanation There may be a problem in the sequence that shuts down all interfaces before fcdomain receives a request from FICON Manager to purge the persistent FCID table.
Recommended Action No action is required.
Error Message FCDOMAIN-7-FSM_FAILED: FSM transition failed on interface [chars] (current state [chars])
Explanation Fcdomain state machine generated an invalid event on interface [chars], for which no proper action was defined (current state [chars].)
Recommended Action No action is required.
Error Message FCDOMAIN-7-FSM_FORBIDDEN_TRANSITION: fcdomain state machine has hit a forbidden transition
Explanation Fcdomain state machine has tried to execute a forbidden transition.
Recommended Action No action is required.
Error Message FCDOMAIN-7-INTERFACERDY: Interface [chars] ready
Explanation Interface [chars] is ready.
Recommended Action No action is required.
Error Message FCDOMAIN-7-PREACTIONTYPE_UNKNOWN: fcdomain state machine has hit an unknown pre-action type
Explanation An undefined pre-action type has been used.
Recommended Action No action is required.
Error Message FCDOMAIN-7-PSWSCOMPLETED: Principal Switch Selection completed
Explanation A Principal Switch Selection (PSwS phase) completed.
Recommended Action No action is required.
Error Message FCDOMAIN-7-RDIACC: Assigned domain ID [dec], WWN of requestor [chars] (requested domain ID [dec])
Explanation Domain ID [dec] has been received by VSAN with WWN [chars] (requested domain ID was [dec].)
Recommended Action No action is required.
This section contains the FCD messages.
Error Message FCD-7-SB3_ABTS_EXCHANGE: sb3 aborted exchange [hex] from vsan:[dec] ch:[hex] chi:[hex] ccw:[hex] token:[hex] cmd:[hex] reason:[chars] state:[chars]:[dec]
Explanation SB3 aborted exchange due to reason given. Aborts are caused by either the channel or control unit detecting a device protocol error. Recovery actions are performed to restore communication. In certain circumstances aborts occur in normal operations.
Recommended Action No action is required if communication with CUP device is still operational.
Error Message FCD-7-SB3_UCS_PER_FILE_FN: VSAN:[dec] Unit Check for perform file function, reason: [chars]
Explanation SB3 failed perform file function. Failure is caused by error in the file main frame sent to director.
Recommended Action No action is required if communication with CUP device is still operational.
This section contains the FCFWD messages.
Error Message FCFWD-3-ERROR: [chars]
Explanation Fcfwd 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.
Error Message FCFWD-4-WARNING: [chars]
Explanation Fcfwd is generating a relevant notification
Recommended Action No action is required.
Error Message FCFWD-6-INFO: [chars]
Explanation An fcfwd event occurred
Recommended Action No action is required.
This section contains the FCNS messages.
Error Message FCNS-2-DB_HARD_LIMIT: : [chars]
Explanation Name server database is full. The max number of entries, [dec], of ports is already present in the database
Recommended Action No action is required.
Error Message FCNS-2-DB_SOFT_LIMIT: : [chars]
Explanation Number of FCNS DB entries should not exceed scale soft limit.
Recommended Action No action is required.
Error Message FCNS-2-INIT_FAILURE: : [chars]
Explanation Fcns initialisation has failed due to [chars].
Recommended Action No action is required.
Error Message FCNS-2-NO_RESPONSE: for query [chars] from domain [dec]
Explanation No response for query [chars] from domain [dec].
Recommended Action No action is required.
Error Message FCNS-2-PSS_VERSION_MISMATCH: : for [chars]
Explanation Version mismatch for pss of type [chars].
Recommended Action No action is required.
Error Message FCNS-2-RELOAD_FAILURE: : [chars]
Explanation Failed to reload information from PSS: [chars].
Recommended Action No action is required.
Error Message FCNS-3-BAD_FRAME: : [chars]
Explanation Received a bad frame from the network: [chars].
Recommended Action No action is required.
Error Message FCNS-3-CFG_FAILURE: : [chars]
Explanation A failure related to fcns configuration: [chars].
Recommended Action No action is required.
Error Message FCNS-3-CHUNK_FAILURE: : [chars]
Explanation Chunk memory failure: [chars].
Recommended Action No action is required.
Error Message FCNS-3-DB_FAILURE: : [chars]
Explanation A failure occured in fcns database: [chars].
Recommended Action No action is required.
Error Message FCNS-3-MALLOC_FAILURE: : [chars]
Explanation Malloc failed: [chars].
Recommended Action No action is required.
Error Message FCNS-3-MGMT_SEC_SDB_ERR: [chars] : [chars]
Explanation Mgmt-security shared-db [chars] : [chars].
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.
Error Message FCNS-3-MTS_FAILURE: : [chars] [chars]
Explanation Failure occured trying to do an MTS operation: [chars] [chars].
Recommended Action No action is required.
Error Message FCNS-3-PSS_FAILURE: : [chars]
Explanation Pss failure: [chars].
Recommended Action No action is required.
Error Message FCNS-4-MGMT_SEC_RJT: FC CT Managment request rejected: [chars]. command [hex], from FCID [hex]
Explanation Mgmt-security has rejected FC CT mgmt Server query: [chars]. command [hex]. from FCID [hex].
Recommended Action No action is required.
Error Message FCNS-4-QUERY_NO_RESPONSE: for query [chars] from domain [dec]
Explanation No response for query [chars] from domain [dec].
Recommended Action No action is required.
Error Message FCNS-6-DB_INFO: : [chars] [hex]
Explanation Database modification:[chars] for entry [hex].
Recommended Action No action is required.
Error Message FCNS-6-MGMT_SERVER_REQ: FCNS received FC CT Mgmt Server [chars]. Command [hex], from FCID [hex]
Explanation FCNS: received management server FC CT [chars]. Command [hex], from FCID [hex]
Recommended Action No action is required.
Error Message FCNS-6-PORT_NAME_MODIFY: FCID: [chars] Modifying pwwn from [chars] to [chars]. Collect fcns/fcr tech-support and logs
Explanation Port Name for an existing NS entry is being changed
Recommended Action No action is required.
Error Message FCNS-6-STATUS_INFO: : [chars]
Explanation A change in fcns status: [chars].
Recommended Action No action is required.
This section contains the FCOELC messages.
Error Message FCOELC-2-FCOELC_PSS_RESTORE_FAILED: FCoE-LC PSS Restore operation failed, error: [chars]
Explanation FCoE-LC PSS Restore operation failed
Recommended Action No action is required.
This section contains the FCOE_MGR messages.
Error Message FCOE_MGR-2-FCOE_MGR_MODULE_NOT_LICENSED: FCoE Manager Module:[dec] not licensed
Explanation FCOE_MGR Line Card not licensed
Recommended Action No action is required.
Error Message FCOE_MGR-2-FCOE_MGR_PSS_RESTORE_FAILED: FCoE Manager PSS Restore operation failed, error: [chars]
Explanation FCoE Manager PSS Restore operation failed
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_DISABLED: FCOE_MGR Disabled
Explanation FCOE_MGR Service Disabled
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_ENABLED: FCOE_MGR Enabled
Explanation FCOE_MGR Service Enabled
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_INFO: [chars]
Explanation FCoE Manager general info
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKIN: FCoE Manager License Checkin:[dec]
Explanation FCOE_MGR Line Card license checked in
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKOUT: FCoE Manager License Checkout:[dec]
Explanation FCOE_MGR Line Card license checked out
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_SOLICITATION_FROM_SAME_MAC: FCoE Manager received Mulicast Solication from same MAC: [chars]
Explanation FCoE Manager received Mulicast Solication from same MAC
Recommended Action No action is required.
Error Message FCOE_MGR-5-FCOE_MGR_VE_DUPLICATE_PEER_MAC: FCoE Manager has already received unicast advertisement from MAC [chars] on a different VE link. Bringing down this link
Explanation FCoE Manager has already received unicast advertisement from same MAC on a different VE link
Recommended Action No action is required.
This section contains the FCSP-MGR messages.
Error Message FCSP-MGR-2-DBG_INIT_FAILED: Debug Infrastructure Initialization failed ( [chars] )
Explanation .
Recommended Action No action is required.
Error Message FCSP-MGR-2-FC2_E_INIT_FAILED: Fibre-Channel Initialization of an E_Port failed ( [chars] )
Explanation FC-SP Manager has been unable to initialize with the FC-2 E-Port infrastructure.
Recommended Action No action is required.
Error Message FCSP-MGR-2-FC2_F_INIT_FAILED: Fibre-Channel Initialization of an F_Port failed ( [chars] )
Explanation FC-SP Manager has been unable to initialize with the FC-2 F-Port infrastructure.
Recommended Action No action is required.
Error Message FCSP-MGR-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown FC-2 frame on [chars]
Explanation .
Recommended Action No action is required.
Error Message FCSP-MGR-2-FCSP_AUTHENT_FAILURE: FC-SP Authentication failure on Port [chars] (FC-SP Failure Reason: [chars] [chars])
Explanation Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail [chars]). Please check password configurations and ensure appropriate security modes on this port as well as peer port
Recommended Action No action is required.
Error Message FCSP-MGR-2-FCSP_ESP_MISMATCH: ESP parameters mismatch failure on Port [chars] (reason:[chars])
Explanation Fibre-Channel ESP parameters mismatch with the peer on Port [chars].(Reason: [chars]). Please check ESP configurations on both side of the link and ensure appropriate ESP mode on this port as well as peer port
Recommended Action No action is required.
Error Message FCSP-MGR-2-FSMU_INIT_FAILED: State Machine Infrastructure Initialization failed ( [chars] )
Explanation .
Recommended Action No action is required.
Error Message FCSP-MGR-2-IPC_INIT_FAILED: IPC (Inter Process Communication) Initialization failed ( [chars] )
Explanation FC-SP Manager has been unable to initialize with the IPC infrastructure.
Recommended Action No action is required.
Error Message FCSP-MGR-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service exiting
Explanation License of [chars] is unavailable. Service will exit now
Recommended Action Please install the license file to continue using the feature.
Error Message FCSP-MGR-2-MEM_FAILED: Memory operations failed File: [chars] Line [dec] for size [hex] bytes
Explanation .
Recommended Action No action is required.
Error Message FCSP-MGR-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] )
Explanation .
Recommended Action No action is required.
Error Message FCSP-MGR-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed ( [chars] )
Explanation .
Recommended Action No action is required.
This section contains the FCS messages.
Error Message FCS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]
Explanation Memory allocation failed for size [dec]
Recommended Action Restart the process
Error Message FCS-2-CHUNK_ALLOC_FAILED: Chunk memory allocation failed for [chars] chunk
Explanation Chunk memory allocation failed. [chars] indicates the chunk name
Recommended Action Restart the process
Error Message FCS-2-NO_RESPONSE: Retried maximum number of times for [chars] to domain [dec] in VSAN [dec]
Explanation Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].
Recommended Action No action is required.
Error Message FCS-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version
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.
Error Message FCS-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.
Error Message FCS-3-DB_ERR: [chars]
Explanation An error occurred during an FCS database operation. [chars] indicates the reason for the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message FCS-3-FCS_MGMT_SEC_SDB_ERR: [chars] : [chars]
Explanation FC CT Mgmt Security shared db operation : [chars] : [chars].
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.
Error Message FCS-3-INIT_FAIL: [chars]
Explanation An error happened during FCS Initialization. [chars] indicates the reason for 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.
Error Message FCS-3-MTS_API_ERR: [chars] : [chars]
Explanation An error occurred in send or receive of an MTS message. [chars] indicates the error that occurred and [chars] indicates the error number
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.
Error Message FCS-3-MTS_ERR: [chars]
Explanation An error occurred in processing of an MTS message. [chars] indicates the error that occurred
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.
Error Message FCS-3-NO_MTS_RESP: [chars]
Explanation There was no response to an MTS request. [chars] indicates details of the MTS 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.
Error Message FCS-3-NO_REMOTE_RESP: No response for request [chars] from domain [dec] in VSAN [dec]
Explanation There was no response to an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID
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.
Error Message FCS-3-OTHER_ERR: [chars]
Explanation An FCS generic error occurred. [chars] indicates the description of the error
Recommended Action No action is required.
Error Message FCS-3-PSS_ERR: [chars]
Explanation An error occurred during an FCS PSS operation. [chars] indicates the PSS operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message FCS-3-SOCK_ERR: sd: [dec], [chars]
Explanation An FC-2 Socket error occurred on socket-ID [dec]. [chars] indicates the reason for 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.
Error Message FCS-4-FCS_MGMT_SEC_RJT: FC CT Management Server query Rejected: [chars]. from FCID [hex]
Explanation Mgmt-security has rejected FC CT Management Server query: [chars]. from FCID [hex].
Recommended Action No action is required.
Error Message FCS-5-API_FAIL: [chars]: [chars]
Explanation An API called by FCS failed. [chars] indicates the API name failed and [chars] the reason for failure
Recommended Action If this message is seen during a cold boot, it means that the queried module came up after FCS and this case can be ignored
Error Message FCS-5-DB_NOTICE: [chars]
Explanation An error occurred during an FCS database operation. [chars] indicates the reason for the error
Recommended Action No action is required.
Error Message FCS-6-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex]
Explanation An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].
Recommended Action No action is required.
Error Message FCS-6-FCS_MGMT_SERVER_REQ: FCS received FC CT Mgmt Server [chars]. Command code [hex], from FCID [hex].
Explanation FC CT request has been received from Managment Server. It is [chars]. Command code [hex], from FCId [hex]
Recommended Action No action is required.
Error Message FCS-6-INFORMATION: [chars]
Explanation An event happend that affects FCS. [chars] indicates the event
Recommended Action No action is required.
Error Message FCS-6-REXMIT_PKT: Retransmitting request [chars] to domain [dec] in VSAN [dec]
Explanation There was a retransmission of an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID
Recommended Action No action is required.
This section contains the FEATURE-MGR messages.
Error Message FEATURE-MGR-2-FM_AUTOCKPT_FAILED: AutoCheckpoint [chars] failed to be created for reason: [chars] ([hex])
Explanation AutoCheckpoint with the given name has been created successfully
Recommended Action No action is required.
Error Message FEATURE-MGR-2-FM_FEATURE_LICENSE_ERROR: license [chars] checkout failure for [chars], error [hex] ([chars])
Explanation License operation was not successful, check license validity for the feature
Recommended Action Please contact FM team
Error Message FEATURE-MGR-2-FM_FEATURE_OP_GENERIC_ERROR: Service [chars] with uuid [dec] ([hex]) encountered error:[hex]([chars]).Disable dependent features or contact service owner for details.
Explanation Operation was not successful
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FEATURE_OP_TIMEOUT_ERROR: feature [chars] operation failed on response timeout from service: [chars] with uuid ([hex])
Explanation The error seen at FM and service communication
Recommended Action Please contact service owner with given uuid and FM team
Error Message FEATURE-MGR-2-FM_FSET_ADD_CONFCHECK_ERROR: failed to add confcheck [hex] ([chars]) at installing feature-set [chars]
Explanation Failed to add confcheck at enabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_CFG_ALLOW_ERROR: Potential vdc_mgr issue: the allow request failed [hex] ([chars])
Explanation Vdc_mgr failed to response the allow request
Recommended Action Please contact FM/vdc_mgr team
Error Message FEATURE-MGR-2-FM_FSET_CKPT_ERROR: Checkpoint issue: failed on checkpoint with error [hex] ([chars]) at feature-set [chars]
Explanation Checkpoint did not response
Recommended Action Please contact FM/vdc_mgr and rollback team
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_ERROR: Potential sysmgr issue: disable feature-set [chars] on sup failed with error [hex] ([chars])
Explanation Some issues while disabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_FEATURES_ERROR: features failed to disable at feature-set [chars] with error [hex] ([chars])
Explanation Failed to disable feature at disabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_FEATURES_TIMEOUT: Potential [chars] issue: feature [chars] did not complete its disabling
Explanation Failed to disable feature at disabling feature-set
Recommended Action Please contact FM/sysmgr team and the feature owner
Error Message FEATURE-MGR-2-FM_FSET_INSTALL_ERROR: install feature-set [chars] returns error 0X[hex] ([chars])
Explanation Somes issues during install feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_LCS_DISABLE_ERROR: Potential sysmgr issue: disable feature-set [chars] failed on module [dec] with error [hex] ([chars])
Explanation Some issues on the lc while disabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_LCS_ENABLE_ERROR: enabling feature-set [chars] on module [dec] returns error 0X[hex] ([chars])
Explanation Somes issue on the lc while enabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_PRESEQ_REJECT: It rejects pre-sequence due to a service with sap [dec]: [chars]
Explanation The message seen when an application rejects feature-set disable request
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_SUP_ENABLE_ERROR: enabling feature-set [chars] on sup returns error 0X[hex] ([chars])
Explanation Some issues during enabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_UNGRACEFUL_DISABLE_ERROR: Potential sysmgr issue: ungraceful disable feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while ungraceful disable feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_UNGRACEFUL_UNINSTALL_ERROR: Potential sysmgr issue: ungraceful uninstall feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while ungraceful uninstall feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_UNINSTALL_ERROR: Potential sysmgr issue: uninstall feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while uninstall feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_VMM_OP_ERROR: [chars]
Explanation The error seen at FM and VMM interaction
Recommended Action Please contact FM/VMM team
Error Message FEATURE-MGR-2-FM_MPLS_NVE_DEPENDENCY: Feature MPLS Static and NV Overlay can't be configured together
Explanation Feature MPLS Static and NV Overlay can't be configured togethe
Recommended Action No action is required.
Error Message FEATURE-MGR-2-FM_MPLS_SR_VPC_DEPENDENCY: Feature MPLS SEGMENT ROUTING and VPC can't be configured together
Explanation Feature MPLS SEGMENT ROUTING and VPC can't be configured together
Recommended Action No action is required.
Error Message FEATURE-MGR-2-FM_MPLS_VPC_DEPENDENCY: Feature MPLS Static and VPC can't be configured together
Explanation Feature MPLS Static and VPC can't be configured together
Recommended Action No action is required.
Error Message FEATURE-MGR-2-MODULE_FM_DONE: feature manager completed
Explanation Feature manager completed
Recommended Action No action is required.
Error Message FEATURE-MGR-2-MODULE_FM_STARTED: feature manager started
Explanation Feature manager started
Recommended Action No action is required.
Error Message FEATURE-MGR-6-FM_AUTOCKPT_IN_PROGRESS: AutoCheckpoint [chars]'s creation in progress...
Explanation AutoCheckpoint creation has been requested and it should be in progress
Recommended Action No action is required.
Error Message FEATURE-MGR-6-FM_AUTOCKPT_SUCCEEDED: AutoCheckpoint [chars] created successfully
Explanation AutoCheckpoint with the given name has been created successfully
Recommended Action No action is required.
Error Message FEATURE-MGR-6-FM_FCOE_AUTOINSTALL_ON_NOT_ISOLA: auto-install feature-set fcoe on non-isola
Explanation Auto-install feature-set fcoe could be done on isola only
Recommended Action Please contact FM team
Error Message FEATURE-MGR-6-FM_FSET_ENABLED_AT_UNINSTALL: Uninstall aborted because feature set is still enabled in vdc [dec]
Explanation Feature set is in enabled state
Recommended Action No action is required.
This section contains the FEX messages.
Error Message FEX-2-FEXCONFIG_ON_VPC: A green start is a must after ISSU for VPC config on FPC([hex]) for AA-FEX bringup. Please ignore if you already reloaded the switch after upgrading to version >= 7.0.3(I5)2
Explanation Green start (post ISSU) is a must to ensure programming correctness before configuring AA-FEXes
Recommended Action No action is required.
Error Message FEX-2-FEX_NOT_ONLINE_SUP_ISSU: FEX [dec] did not come online after SUP ISSU
Explanation FEX did not come online after sup ISSU
Recommended Action No action is required.
Error Message FEX-2-FEX_OFFLINE: FEX [dec] has gone OFFLINE
Explanation FEX has gone OFFLINE
Recommended Action No action is required.
Error Message FEX-2-FEX_ONLINE: FEX [dec] has come ONLINE
Explanation FEX has come ONLINE
Recommended Action No action is required.
Error Message FEX-2-FEX_PORT_STATUS_CRIT: Uplink-ID [dec] of Fex [dec] that is connected with [chars] changed its status from [chars] to [chars]
Explanation Fex [decimal-digit] changed port status
Recommended Action No action is required.
Error Message FEX-2-NOHMS_ENV_FEX_OFFLINE: [chars]
Explanation Fex off-line
Recommended Action Show inventory
Error Message FEX-2-NOHMS_ENV_FEX_ONLINE: [chars]
Explanation Fex on-line
Recommended Action Show inventory
Error Message FEX-4-FEX_SCALING_LIMITS_REACHED: You have exceeded the advisable FEX scaling limits.
Explanation More FEX/FEX ports in the system than recommended by Cisco.
Recommended Action No action is required.
Error Message FEX-5-FEX_DISABLED: FEX Disabled
Explanation FEX Service Disabled
Recommended Action No action is required.
Error Message FEX-5-FEX_ENABLED: FEX Enabled
Explanation FEX Service Enabled
Recommended Action No action is required.
Error Message FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID [dec] of Fex [dec] that is connected with [chars] changed its status from [chars] to [chars]
Explanation Fex [decimal-digit] changed port status
Recommended Action No action is required.
Error Message FEX-5-PINNING_CHANGED: Fex [dec] pinning information is changed
Explanation Fex pinning information changed
Recommended Action No action is required.
Error Message FEX-5-SATMGR_DISABLE_FAILED: Disabling of feature FEX failed. Please remove FEX related configs from interfaces
Explanation Disabling of FEX feature failed
Recommended Action No action is required.
This section contains the FIB messages.
Error Message FIB-SLOT#-0-EMERG: [chars]
Explanation Fib caused a system 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.
Error Message FIB-SLOT#-1-ALERT: [chars]
Explanation Fib caused failures in other 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.
Error Message FIB-SLOT#-1-HW_RESOURCE: [chars]
Explanation Hardware resources are approaching limit.
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.
Error Message FIB-SLOT#-1-HW_RESOURCE: [chars]
Explanation Hardware resources are approaching limit.
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.
Error Message FIB-SLOT#-2-CRIT: [chars]
Explanation Fib encountered a catastrophic 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.
Error Message FIB-SLOT#-3-ERR: [chars]
Explanation Fib 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.
Error Message FIB-SLOT#-3-HW_FAIL: [chars]
Explanation Failed to program route into the hardware.
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.
Error Message FIB-SLOT#-3-NO_MEM: Out of memory
Explanation Fib does not have enough memory to continue proper operation.
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.
Error Message FIB-SLOT#-3-SEND_SUP: Cannot talk to supervisor
Explanation Fib to supervisor IPC 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.
Error Message FIB-SLOT#-4-CPU_HOG: Inactive or busy
Explanation Either fib was not scheduled to run, or fib was busy, and fib did not service the message or timer queue for an extended period.
Recommended Action Please perform 'debug fib error', then recreate the operation scenario, to find out more details.
Error Message FIB-SLOT#-4-WARN: [chars]
Explanation Fib encountered a possible 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.
Error Message FIB-SLOT#-6-FIB_INFO: [chars]
Explanation Information that a corrective action was taken by FIB
Recommended Action Message is informational only
This section contains the FICON messages.
Error Message FICON-2-E_DUPLICATE_PN_BRINGUP_FAIL: [chars]
Explanation This port has the same port number assigned to other port in the same FICON VSAN. No more than one port with duplicate port number can be up in each FICON VSAN
Recommended Action Avoid duplicate number assignment in each FICON VSAN\n
Error Message FICON-2-E_PN_PA_NOT_IN_BOUND: [chars]
Explanation Port number or port address in startup-configure is out of bound.
Recommended Action Change ficon port number assign configuration and save to startup-configure.\n
Error Message FICON-2-E_SAVE_FILE: [chars]
Explanation Failed to save file. Possibly due to asymmetric pdcm matrix. Look for retval for actual reason.
Recommended Action Configure port prohibits in symmetrically.\n
Error Message FICON-2-SHUTDOWN: FICON Manager process shutting down: [chars]
Explanation FICON Manager shutting down
Recommended Action This is a severe error. Provide the reason given in the message\n
Error Message FICON-3-E_ASSIGN_BINDING_PN_FAIL: [chars]
Explanation Port number has fcip or port channle binding can not be removed nor changed.
Recommended Action Remove port number binding of the logical interface first.\n
Error Message FICON-3-E_ASSIGN_INVALID_PN_PARAM: [chars]
Explanation Invalid port number parameters in command.
Recommended Action Check port numbers in the command.\n
Error Message FICON-3-E_ASSIGN_OVERLAP_PN_FAIL: [chars]
Explanation Port number assigned to physical and logical can not overlap.
Recommended Action Check port numbers in the command.\n
Error Message FICON-3-E_ASSIGN_PN_NOT_DOWN_FAIL: [chars]
Explanation Only port number assigned to a port in down state can be removed or changed.
Recommended Action Bring down the port first.\n
Error Message FICON-3-E_ASSIGN_PROHIBIT_PN_FAIL: [chars]
Explanation Logical port address can not be prohibited.
Recommended Action Check port numbers in the command.\n
Error Message FICON-3-E_DUPLICATE_PN_ASSIGN_WARNING: [chars]
Explanation This port has the same port number assigned to other port in the same FICON VSAN. No more than one port should have the same port number in each FICON VSAN
Recommended Action Avoid duplicate number assignment in each FICON VSAN\n
Error Message FICON-3-E_INVALID_PA_BRINGUP_FAIL: [chars]
Explanation This port either has an invalid port address assigned or has no port address assigned.
Recommended Action Assign a valid ficon port number to the port.\n
Error Message FICON-3-E_PORT_PROHIBIT_BRINGUP_FAIL: [chars]
Explanation This port has been prohibited. Prohibiting E or TE ports is not allowed. This port can not be configured in E mode or TE mode until the prohibit mask configuration is changed
Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring it up as an E or TE port in a FICON VSAN\n
Error Message FICON-3-E_UNASSIGN_NO_PN_FAIL: [chars]
Explanation Only port number already assigned can be removed.
Recommended Action Check port numbers in the command.\n
Error Message FICON-3-PDCM_CHANGE_REJ_E_PORT: [chars]
Explanation The FICON Prohibit Dynamic Connectivity Mask(PDCM) change rejected because an E or TE port is being prohibited. Prohibiting an E or TE port in not allowed
Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring the port up as an E or TE port in a FICON VSAN\n
Error Message FICON-5-STARTING: FICON Manager process starting
Explanation FICON Manager process is being started
Recommended Action No action is required.
Error Message FICON-6-PDCM_CHANGE: VSAN [dec] port-address [dec] prohibit mask set to [chars]
Explanation The FICON Prohibit Dynamic Connectivity Mask (PDCM) for this port has changed. VSAN [dec], port address [dec] prohibit mask (PDCM) is now set to [chars]
Recommended Action No action is required.
Error Message FICON-6-PORT_SWAP: port number [dec] [dec] swapped
Explanation FICON portnumbers swapped
Recommended Action No action is required.
Error Message FICON-6-VSAN_DISABLED: FICON disabled on VSAN [dec]
Explanation FICON has been disabled on the given VSAN
Recommended Action No action is required.
Error Message FICON-6-VSAN_ENABLED: FICON enabled on VSAN [dec]
Explanation FICON has been enabled on the given VSAN
Recommended Action No action is required.
This section contains the FIPS messages.
Error Message FIPS-0-FIPS_POST_CLEANUP_FAILED: Error cleaning up keys in FIPS mode : [chars]
Explanation FIPS cleanup failed [chars]
Recommended Action No action is required.
Error Message FIPS-0-SET_FIPS_MODE_FAILED: Error when setting FIPS mode : [chars]
Explanation FIPS mode failed [chars]
Recommended Action No action is required.
Error Message FIPS-6-SET_FIPS_MODE: FIPS mode is [chars] for service [chars]
Explanation FIPS mode is changed [chars] [chars]
Recommended Action No action is required.
This section contains the FLOGI messages.
Error Message FLOGI-1-MSG_FDISC_REJECT_TOO_MANY_LOGINS: [VSAN [dec], Interface [chars]] FDISC rejected - this interface has reached the max num of N-Ports ([dec])
Explanation An FDISC was rejected because the F-Port has reached the maximum allowed number of devices.
Recommended Action Check the configuration of the NPIV device connected to the port.
Error Message FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR: [VSAN [dec], Interface [chars]] (pwwn: [chars]) FLOGI rejected - FCID allocation failed with error [hex].
Explanation An FLOGI was rejected because the FCID allocation failed.
Recommended Action Check the fcid-interop configuration, purge the persistency table and check the output of "show flogi database details" and see if any of the "A area FCID allocation" entries can be turned to single fcid allocation as per Configuration Guide
Error Message FLOGI-1-MSG_FLOGI_REJECT_TOO_MANY_LOGINS: [VSAN [dec], Interface [chars]] FLOGI rejected - this interface has reached the max num of NL-Ports ([dec])
Explanation An FLOGI was rejected because the FL-Port has reached the maximum allowed number of devices.
Recommended Action Reduce the number of devices on the loop
Error Message FLOGI-1-MSG_NPIV_NOT_SUPPORTED_WITH_TRUNKING: [VSAN [dec], Interface [chars]] NPIV not supported - on this platform, NPIV is not supported on trunking interfaces
Explanation The N_Port requested NPIV, but this platform does not support NPIV on trunking F_Ports.
Recommended Action Disable NPIV, or move the N_Port to a switch that supports NPIV on trunking F_Ports
Error Message FLOGI-2-MSG_FLOGI_REJECT_NO_ACL_TCAM_AVAILABLE: [VSAN [dec], Interface [chars]] FLOGI rejected - ACLTCAM resource exausted
Explanation An FLOGI was rejected because the ACLTCAM hardware resource is completely used.
Recommended Action Reduce the number of nodes.
Error Message FLOGI-4-MSG_VF_FLOGI_FROM_NON_CISCO_OUI: [VSAN [dec], Interface [chars]] FLOGI with VF bit set from OUI [hex]:[hex]:[hex] (nwwn: [chars])
Explanation This interface received an FLOGI with VF bit set from a non CISCO OUI; in this release Virtual Fabrics are not supported on interfaces connected to third-party devices
Recommended Action Set the trunk mode of this interface to off
Error Message FLOGI-5-MSG_FLOGI_DROP_DUE_TO_SUSPENDED_VSAN: [VSAN [dec], Interface [chars]] FLOGI (pwwn: [chars]) has been dropped because the VSAN is suspended on this trunking interface
Explanation The switch received an FLOGI from a trunking interface on a VSAN which has been suspended; the FLOGI frame has been dropped.
Recommended Action To bring up the VSAN again on the trunking port, remove it from the allowed VSAN list and add it again
Error Message FLOGI-5-MSG_FLOGI_DUPLICATE_WWPN: [VSAN [dec], Interface [chars]] FLOGI (pwwn: [chars]) has been dropped because the host has a duplicate WWPN
Explanation The switch received an FLOGI from the interface, which has a duplicate PWWN value.
Recommended Action No action is required.
Error Message FLOGI-5-MSG_IF_REINIT_ALPA_CONFLICT: [VSAN [dec], Interface [chars]] FL/TL interface [chars] re-initialized as ALPA - PWWN map conflict occurred.
Explanation The FL/TL interface is re-initialized as ALPA used by device conflicts with an existing FLOGI session after the Loop Initialization Protocol (LIP). All the devices will re-login with new ALPA and PWWN mapping
Recommended Action No action is required.
Error Message FLOGI-5-MSG_PORT_LOGGED_IN: [VSAN [dec], Interface [chars]] Nx Port [chars] with FCID [chars] logged IN.
Explanation Nx port logged in with the specified information.
Recommended Action No action is required.
Error Message FLOGI-5-MSG_PORT_LOGGED_OUT: [VSAN [dec], Interface [chars]] Nx Port [chars] logged OUT.
Explanation Nx port logged out. The following commands will help determine why this Nx port logged out: 'show interface, show VSAN, show module'
Recommended Action No action is required.
This section contains the FS-DAEMON messages.
Error Message FS-DAEMON-2-FSD_ENOSPC_BOOTFLASH: Due to insufficient space, [chars] image could not be copied to standby bootflash. [chars] image is not present on standby. Please copy \'[chars]\' manually.
Explanation Move system images from RAM to bootflash to free up some memory
Recommended Action Please remove some unnecessary files on bootflash using \'delete\' CLI command and copy images from active supervisor or from remote location
Error Message FS-DAEMON-6-FSD_ENOSPC_LOGFLASH: System logflash usage has reached [dec]%. You may delete some old files on logflash to free up space
Explanation System logflash space is almost full
Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on logflash
Error Message FS-DAEMON-6-FSD_ENOSPC_ROOT: System root usage has reached [dec]%. You may delete some old files from root or /var/log to free up space
Explanation System root space is almost full
Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on root dir or /var/log
Error Message FS-DAEMON-6-FSD_ENOSPC_TMP: System temporary directory usage has reached [dec]%.
Explanation System /tmp space usage.
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.
Error Message FS-DAEMON-6-FSD_REEXPORT_NFS: Re-exported NFS mounts
Explanation Exported NFS mounts are not visible in kernel and had to be reexported
Recommended Action Please use 'show system internal flash' to make sure there are no Stale NFS handles
This section contains the FSCM messages.
Error Message FSCM-2-FABRIC_START_CFG_MGR_PROGRAM_EXIT: Fabric Start Cfg Mgr daemon exiting: [chars]
Explanation FABRIC_START_CFG_MGR 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.
This section contains the FSPF messages.
Error Message FSPF-2-SHUTDOWN: Routing daemon shutting down : [chars]
Explanation FSPF routing daemon is shutting down because of [chars] reason.
Recommended Action This is a severe bug. Provide the reason provided and the log files for FSPF.
Error Message FSPF-3-BAD_FC2_PKT: Received bad FC2 packet on interface [chars] : [chars]
Explanation FSPF received a bad FC2 packet on [chars] interface , error description is [chars].
Recommended Action FSPF daemon has received a bad FC frame. Provide the output of 'debug fc2 pkt '.
Error Message FSPF-3-CHECKSUM_FAIL: Checksum test failed for LSR domain [dec]
Explanation Periodic database checksum test failed for LSR for domain [dec]
Recommended Action This indicates that the internal database got corrupted because of some memory corruption bug. Provide output of 'show fspf database '. May need to power cycle the switch
Error Message FSPF-3-FC2_PROC_ERR: Error in processing [chars] packet on interface [chars], Error = [chars]
Explanation An error occurred in processing a [chars] FC2 packet on [chars] interface. The internal error code is [chars].
Recommended Action Turn on 'debug fspf error' to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Provide output of 'show fspf vsan x' 'show fspf vsan x interface' and 'debug fspf fc pkt ' for the specific interface
Error Message FSPF-3-FLOOD_ERR: Error in flooding the local LSR , Error = [chars]
Explanation FSPF had an error in flooding the local LSR , error description is [chars].
Recommended Action Provide output of 'debug fspf flood' , 'debug fspf error'. If error is reported in transmitting packet check if interface is up and turn on 'debug fc2 error'
Error Message FSPF-3-HELLO_MISMATCH: Mismatch in [chars] in the Hello packet on interface [chars]
Explanation There is a mismatch in the [chars] entry in the hello packet received on interface [chars]. The packet will be dropped.
Recommended Action Check the configuration of hello or dead interval on the switches on the two ends of the interface to see if there is a mismatch.
Error Message FSPF-3-INTF_TIMER_ERR: Error in processing interface timer event [chars] for interface [chars] , error = [chars]
Explanation FSPF had an error in processing timer event for interface chars, error is [chars].
Recommended Action Provide output of 'debug fspf error'
Error Message FSPF-3-IPC_PROC_ERR: Error in processing IPC message : Opcode = [dec], Error code = [hex]
Explanation FSPF had an error in processing message of [dec] opcode , the internal error code is [dec].
Recommended Action Possibly some wrong IPC message is received by FSPF . Provide output of 'debug fspf mts pkt' and 'debug fspf error ' trace.
Error Message FSPF-3-LOCK_FAIL: FSPF failure in gaining lock
Explanation There is a software failure in gaining lock of the shared resource between FSPF threads.
Recommended Action Provide output of 'debug fspf all '
Error Message FSPF-3-MTS_MSG_BEFORE_GSYNC: FSPF in standby received MTS message opcode = [hex] before GSYNC
Explanation FSPF in standby received an MTS message of opcode [dec] before receiving the GSYNC message.
Recommended Action Provide output of 'debug fspf mts pkt '
Error Message FSPF-3-RIB_ERR: Error in RIB : [chars]
Explanation FSPF had an error in interacting with RIB, error description is [chars].
Recommended Action Check if rib application is running using 'show processes'. Provide output of 'debug fspf route' and RIB debug traces.
Error Message FSPF-3-ROUTE_COMPUTE_ERR: Error in computing or sending routes : Error = [chars]
Explanation FSPF had an error in computing routes , error description is [chars].
Recommended Action Provide the error code and output of 'debug fspf error' and 'debug fspf route' if problem is reproducible
Error Message FSPF-3-UNLOCK_FAIL: FSPF failure in releasing lock
Explanation There is a software failure in releasing lock of the shared resource between FSPF threads.
Recommended Action Provide output of 'debug fspf all '
Error Message FSPF-3-VSAN_TIMER_ERR: Error in processing VSAN timer event [chars], error description = [chars]
Explanation FSPF had an internal error in processing timer event , error description is [chars].
Recommended Action Provide output of 'debug fspf error'
Error Message FSPF-4-FC2_DOWN_INTF: Received FC2 packet on DOWN interface [chars]
Explanation FSPF received a FC2 packet on inactive interface [chars] .
Recommended Action This message may be printed for the first FSPF packet when an interface is brought up. If the message is seen continuously check if FSPF is disabled on one end for the interface or the VSAN. Otherwise check 'show interface ' output to see if interface is physically up only on one side. Also check if there is any error message printed for IPC_PROC_ERR
Error Message FSPF-4-FC2_DOWN_VSAN: Received FC2 packet on inactive vsan
Explanation FSPF received a FC2 packet on inactive vsan.
Recommended Action If message seen continuously check if FSPF is disabled on the VSAN Investigate if VSAN is active and valid domain has been assigned on the switch Also check if IPC_PROC_ERR message is printed in the syslog
Error Message FSPF-4-ILLEGAL_FSM_EVENT: Illegal FSM event for state [chars] in interface [chars]
Explanation An illegal protocol event has occurred for the FSPF state machine. The old state was [chars] for the interface [chars].
Recommended Action It is possible to get this message if some protocol packet gets dropped but the it should recover and move back to FULL state. Do 'show fspf interface' to check the state of the interface. If it is stuck in state other than FULL provide output of 'debug fspf event' and 'debug fspf fc pkt ' for the interfaces involved.
Error Message FSPF-4-LSR_DROPPED: [chars], Dropping LSR [dec] received on interface [chars]
Explanation A LSR packet is dropped due to [chars] reason. LSR belonged to domain [dec] and was received on interface [chars].
Recommended Action Provide the reason given for dropping the LSR and output of 'debug fspf fc pkt' If the reason is checksum failure investigate possible packet corruption or truncation
Error Message FSPF-4-LSR_MIN_LS_ARRIVAL: Packet arrived before MIN_LS_ARRIVAL, Dropping LSR [dec] on interface [chars]
Explanation A LSR packet is dropped as it arrived before MIN_LS_ARRIVAL. LSR belonged to domain [dec] and was received on interface [chars].
Recommended Action This can occur in transient situation and protocol recovers by retransmitting the LSR. If the message is seen continuously provide output of 'debug fspf flood ' , 'debug fspf retrans' and 'debug fspf error '. The message may be seen more often when interoperating with other vendors
Error Message FSPF-4-LSU_RX_INIT: Dropping LSU received in state INIT on interface [chars]
Explanation A LSU packet is dropped as interface [char] is in INIT state when it received the LSU.
Recommended Action This can occur in some transient situation. If the problem persists provide output of 'show fspf vsan x interface' and 'debug fspf fc pkt ' and 'debug fspf event vsan x'
Error Message FSPF-5-STARTING: Routing daemon started
Explanation FSPF routing daemon has been started.
Recommended Action No action is required.
Error Message FSPF-6-ADD_LSR: New LSR added for domain [dec]
Explanation A new LSR is added to the database for domain [dec] .
Recommended Action No action is required.
Error Message FSPF-6-DELETE_LSR: LSR deleted for domain [dec]
Explanation The LSR for domain [dec] is deleted from the database.
Recommended Action No action is required.
Error Message FSPF-6-INTF_OPER_DOWN: Down on interface [chars]
Explanation FSPF has become operationally down on interface [chars].
Recommended Action No action is required.
Error Message FSPF-6-INTF_OPER_UP: Up on interface [chars]
Explanation FSPF has become operational on interface [chars].
Recommended Action No action is required.
Error Message FSPF-6-MAX_AGE: LSR [dec] reached Maxage
Explanation The LSR for domain [dec] reached the maximum age and will be deleted from all the connected switches .
Recommended Action No action is required.
Error Message FSPF-6-ROLLOVER: Rolling over the incarnation number of Local LSR
Explanation The incarnation number of local LSR reached the maximum value and is rolling over.
Recommended Action No action is required.
Error Message FSPF-6-SELF_ORIGINATED: Received local LSR with higher incarnation number
Explanation A LSR for the local domain was received with incarnation number higher than the one in database. This situation should only occur initially on a topology change. If this situation persists the domain assignment of switches may not be unique
Recommended Action If this message is received continuously check if domain assignment is unique in the fabric.
Error Message FSPF-6-STATE_CREATED: Internal state created [chars]
Explanation FSPF has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message FSPF-6-VSAN_OPER_DOWN: Down on vsan
Explanation FSPF has become operationally down on VSAN.
Recommended Action No action is required.
Error Message FSPF-6-VSAN_OPER_UP: Up with local domain [dec]
Explanation FSPF has started with local domain [dec].
Recommended Action No action is required.
Error Message FSPF-7-ROUTE_THREAD_STARTED: Thread number [dec] started
Explanation Route computation thread number [dec] has been started for FSPF.
Recommended Action No action is required.
This section contains the HSRP_ENGINE messages.
Error Message HSRP_ENGINE-3-BFD_GLOBAL_SESSION_REMOVAL_ERROR: Failed to remove all the HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation Refer logs for more details
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove few HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation Refer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BFD_SESSION_ADD_ERROR: Failed to add few HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation TRefer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information([hex] [hex]), Refer logs
Explanation Refer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove few HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation Refer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BUNDLE_ASID_REG_FAIL: Switch-id:[dec] DRAP registration failed for bundle:[dec].
Explanation DRAP registration failure
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BUNDLE_LPSS_FAIL: LPSS [chars] for bundle:[dec] failed.
Explanation Libanycast ADD/DEL is failing
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-BUNDLE_VLAN_DOWN: Vlan [dec] DOWN for Bundle [dec], Traffic for group [dec] will be lost on this node.
Explanation If any of the Vlan for the bundle goes down, then bundle remains UP untill the last Vlan of the bundle also goes down, this results into traffic loss for Vlans which are down but bundle is UP.
Recommended Action User can shut the bundle on this node, so that all traffic coming to this node can be switched to other anycast nodes
Error Message HSRP_ENGINE-3-ERROR_IN_ADD_VIP_TO_U6RIB: Failed to Add VIP [chars] to U6RIB (errno [hex]), Refer logs
Explanation Refer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-ERROR_IN_DEL_VIP_FROM_U6RIB: Failed to delete VIP [chars] from U6RIB (errno [hex]), Refer logs
Explanation Refer logs for more details.
Recommended Action No action is required.
Error Message HSRP_ENGINE-3-NOSOCKET: Unable to open socket
Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Make sure that there is at least one interface configured to run IP.
Error Message HSRP_ENGINE-3-VIP_ADD_FAILED1: Falied to retain Address on interface [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on interface [chars] address removed.
Explanation The HSRP virtual IP address cannot be reapplied as as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Verify that the reported IP address is not present on the device/vdc in the same vrf. If its not present, collect show tech-support netstack detail and show tech-support hsrp.
Error Message HSRP_ENGINE-3-VIP_ADD_FAILED2: Falied to retain Address on interface [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application address removed.
Explanation The HSRP virtual IP address cannot be reapplied as as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Verify that the reported IP address is not present on the device/vdc in the same vrf. If its not present, collect show tech-support netstack detail and show tech-support hsrp.
Error Message HSRP_ENGINE-4-BADAUTH2: Bad authentication from [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
Error Message HSRP_ENGINE-4-BADAUTH: Bad authentication from [chars], group [dec], remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
Error Message HSRP_ENGINE-4-BUNDLE_GROUP_NOTEXIST: Group [dec] not found on Intf [chars] for Bundle [dec], Traffic for this group will be lost on this node.
Explanation If any of the groups for the bundle are missing due to misconfig and the bundle is UP, this results into traffic loss for groups which are not configured.
Recommended Action User need to configure the missing groups for the bundle on this node
Error Message HSRP_ENGINE-4-DIFFVIP1: [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
Explanation The HSRP virtual IP address contained in the Hello message from the Active router is different to that configured locally.
Recommended Action Check the configuration on all HSRP routers.
Error Message HSRP_ENGINE-4-DUPADDR: Duplicate address %i on [chars], sourced by %e
Explanation The IP address in an HSRP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration, or because of a malfunctioning switch
Recommended Action Check the configurations on all the HSRP routers, and make sure that any switches you have are functioning properly.
Error Message HSRP_ENGINE-4-DUPVIP1: [chars] Grp [dec] address [chars] is already assigned to a HSRP group on this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group.
Recommended Action Check the configuration on all HSRP routers.
Error Message HSRP_ENGINE-4-DUPVIP2: [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.
Recommended Action Check the configuration on all HSRP routers.
Error Message HSRP_ENGINE-4-DUPVIP3: [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Check the configuration on all HSRP routers.
Error Message HSRP_ENGINE-5-ACTIVEROUTERPRIORITY: Interface [chars] [chars] Grp [dec] Active router priority changed to [dec]
Explanation The priority of the Active router for the group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-ACTIVE_CHANGE: Interface [chars] [chars] Grp [dec] Active router is [chars]
Explanation The Active router for the group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-AUTOCONFIG_VIPLEARN: Interface [chars] grp [dec] learnt autoconfig virtual ip address [chars]
Explanation The local router has generate virtual ip address
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-BUNDLE_DOWN_REASON: Cannot bringup bundle <[dec]:[chars]>, Reason: [chars]
Explanation Display the reason why bundle is down
Recommended Action Address the reason why the bundle is down
Error Message HSRP_ENGINE-5-BUNDLE_STATE_CHANGE: Bundle State change from: [chars] To: [chars].
Explanation Bundle State change
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-GRPSTATECHANGE: Interface [chars] [chars] Grp [dec] state changed from [chars] to [chars] reason [chars]
Explanation The HSRP router has changed state
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-MACADDRESS_CHANGE: Interface [chars] [chars] Grp [dec] mac-address changed to [chars]
Explanation The mac address of the group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-MASTER_NAME_CHNGD: Master Name conflict for grp [dec], using default
Explanation Name conflict between two master, later will fallback to default
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-PRIORITY: Interface [chars] [chars] Grp [dec] priority changed to [dec]
Explanation The current priority of the HSRP group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-STANDBYROUTERPRIORITYCHANGE: Interface [chars] [chars] Grp [dec] Standby router priority changed to [dec]
Explanation The priority of the Standby router for the group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-STANDBY_CHANGE: Interface [chars] [chars] Grp [dec] Standby router is [chars]
Explanation The Standby router for the group has changed.
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-TIMER: Interface [chars] [chars] Grp [dec] [chars] timer changed to [dec] [chars]
Explanation The hello/hold timer value for the HSRP group has changed
Recommended Action No action is required.
Error Message HSRP_ENGINE-5-VIPLEARN: Interface [chars] [chars] Grp [dec] learnt virtual ip address [chars]
Explanation The local router has learnt virtual ip address from the incoming HSRP packet.
Recommended Action No action is required.
Error Message HSRP_ENGINE-6-STATECHANGE2: [chars] [chars] Grp [dec] state moving from [chars]
Explanation The router has changed state
Recommended Action No action is required.
Error Message HSRP_ENGINE-6-STATECHANGE: [chars] [chars] Grp [dec] state move to [chars]
Explanation The router has changed state
Recommended Action No action is required.
This section contains the ICAM messages.
Error Message ICAM-2-APBR_CORRUPT: RISE APBR: in Corrupt State, RS IP: [chars], port: [dec], Proto: [dec], nhop IP: [chars], slot ID: [dec], vlan: [dec]. Reason: [chars].
Explanation RMAP
Recommended Action ACL cannot be completely deleted.
Error Message ICAM-2-DISCOVERY_CHANNEL_DOWN: service '[chars]' is down (slot id [dec]), Reason: [chars]
Explanation See reason string in the error message with the following possibilities: 1. Error in bootstrap/health-monitoring response. 2. Timed out while waiting for bootstrap/health-monitoring response. 3. Failed to send bootstrap/health-monitorying message. 4. Control VLAN interface is not operational. 5. RISE interface [chars] is not operational. 6. RISE interface [chars] does not have control VLAN [dec] as trunk member. 7. Control VLAN ([dec]) interface does not have valid IP. 8. RISE port channel po [dec] has no member ports. 9. Failed to send vlan-group. 10. RISE IP [chars] is already assigned to another service, slot id [dec].
Recommended Action Take corrective action per the reason
Error Message ICAM-2-ITD_LICENSE_EXPIRED: ITD License: license grace-period expired. Please install ENHANCED_LAYER2_PKG.
Explanation License or grace-period has expired.
Recommended Action Take steps to renew license. Feature will be disabled.
Error Message ICAM-2-ITD_LICENSE_MISSING: Feature ITD license missing: ENHANCED_LAYER2_PKG
Explanation License does not exist when attempting to enable ITD feature.
Recommended Action Acquire license or grace-period permission.
Error Message ICAM-2-LICENSE_EXPIRED: RISE License: license grace-period expired. Please install ENHANCED_LAYER2_PKG.
Explanation License or grace-period has expired.
Recommended Action Take steps to renew license. Feature will be disabled.
Error Message ICAM-2-LICENSE_MISSING_COPY_RS: RISE license missing: ENHANCED_LAYER2_PKG. Removing RISE config.
Explanation RISE license missing after NXOS version upgrade. Previous version ran RISE without a license.
Recommended Action Acquire license or grace-period permission.
Error Message ICAM-2-LICENSE_MISSING_ISSU: RISE license missing: ENHANCED_LAYER2_PKG. Removing RISE config.
Explanation RISE license missing after ISSU. Previous version ran RISE without a license.
Recommended Action Acquire license or grace-period permission.
Error Message ICAM-2-LICENSE_MISSING: RISE license missing: ENHANCED_LAYER2_PKG
Explanation License does not exist when attempting to enable RISE feature.
Recommended Action Acquire license or grace-period permission.
Error Message ICAM-3-APBR_ACLMGR_ERROR: RISE APBR: ACL was not [chars], apbr payload: [chars].
Explanation Acl was not created/deleted.
Recommended Action Check TCAM resource limit, and the sys admin.
Error Message ICAM-3-APBR_INGRESS_INT_NOT_FOUND: RISE APBR: can't find the ingress interface for RS IP: [chars].
Explanation 7K cannot find a route to the real server.
Recommended Action Check real server network reachablity in the current switch.
Error Message ICAM-3-APBR_PURGE_ERROR: RISE APBR: Purge failure, slot id: [dec].
Explanation PBR entries for RISE cannot be deleted cleanly.
Recommended Action Manually delete pbr entries.
Error Message ICAM-3-APBR_RPM_ERROR: RISE APBR: RPM returns internal error, rpm resp msg: [chars], apbr payload: [chars].
Explanation Rmap step was not completed.
Recommended Action Check TCAM resource limit, or rmap collision on the same interface, and the sys admin.
Error Message ICAM-3-RHI_ROUTE_ISSUE: RISE RHI: slot [dec] route [chars] cannot be [chars]. Reason:[chars].
Explanation URIB dropped this RHI request. See reason string with the following possibilities: 1. SVI for data vlan [dec] does not exist. 2. SVI for data vlan [dec] is down. 3. urib issues.
Recommended Action Take corrective action per the reason.
Error Message ICAM-4-APBR_MAX_LIMIT: RISE APBR: Reached max apbr entries [dec] per RISE. slot id: [dec].
Explanation PBR entries for RISE cannot be deleted cleanly.
Recommended Action Manually delete pbr entries.
Error Message ICAM-4-APBR_PBR_DISABLED: RISE APBR: feature PBR Disabled.
Explanation APBR will not function correctly without pbr feature.
Recommended Action Manually enable pbr feature.
Error Message ICAM-4-ISSU_PRE_UPGRADE_TIMEOUT: RISE ISSU: pre-upgrade timed out, reason: [chars].
Explanation See the reason.
Recommended Action Try again with the upgrade.
Error Message ICAM-4-ISSU_UNEXPECTED_SLOT_MSG: RISE ISSU: unexpected msg from slot [dec], opcode: [dec].
Explanation Application should not send msg during ISSU. iSCM will ignore.
Recommended Action No action is required.
Error Message ICAM-4-LICENSE_EXPIRING: RISE License: ENHANCED_LAYER2_PKG license expires in [dec] days [dec] hours [chars]econds.
Explanation License or grace-period expiration warning.
Recommended Action Take steps to renew license. Prepare for feature disable.
Error Message ICAM-5-NAM_CLI_ISSUE_CARD_ID: Module [dec] card type is NOT NAM!
Explanation See the reason.
Recommended Action Check show module to see which module is NAM.
Error Message ICAM-5-NAM_CLI_ISSUE_SC_ONLINE: Module [dec] not in SC_ONLINE
Explanation See the reason.
Recommended Action Check show module to see if app state is OK.
Error Message ICAM-5-NAM_CLI_ISSUE_SVC: Service cannot be found for the given module [dec]
Explanation See the reason.
Recommended Action Check the module using show service nam summary.
Error Message ICAM-5-TRANSPORT_ISSUE: RISE Transport: slot [dec] failed to send, reason : [chars].
Explanation See the reason.
Recommended Action Check the network connectivity and the appliance status.
This section contains the IDEHSD messages.
Error Message IDEHSD-1-MANUAL_FORMAT: logflash needs to be formatted
Explanation Logflash is not accessible; use \format logflash:\ to format it
Recommended Action No action is required.
Error Message IDEHSD-2-AUTO_FORMAT: logflash auto-format [chars]
Explanation Logflash auto-format event
Recommended Action No action is required.
Error Message IDEHSD-2-DISK_BUSY_FAILED: Cannot umount [chars],
Explanation The specified disk interface is in use it can not be un mounted, The user may experience file system correuption
Recommended Action Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again
Error Message IDEHSD-2-DISK_FSCK_FAIL: file system check returned error on slot [dec]
Explanation Flash fliesyetm may be corrupted, the flash was taken while it was being accessed
Recommended Action Reformat the extarnal flash
Error Message IDEHSD-2-DISK_MOUNT_FAIL: disk mount unsuccessful on [chars]
Explanation Unknown flash filesystem or not cleanly un mounted
Recommended Action Use vfat flash only and make sure external slot is not being accessed then re-insert flash
Error Message IDEHSD-2-DISK_RESCAN_FAIL: disk rescan unsuccessful on [chars]
Explanation Flash fliesyetm was not cleanly un mounted
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Error Message IDEHSD-2-DISK_UMOUNT_FAIL: disk umount unsuccessful for [chars]
Explanation Flash fliesyetm is busy the system could noy un-mount it
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Error Message IDEHSD-2-FORK: fork failed ([chars] process)
Explanation The flash daemon failed to fork
Recommended Action No action is required.
Error Message IDEHSD-2-INTERNAL_ERROR: Internal Error [dec]
Explanation The flash daemon interface returns error
Recommended Action Restart the idehsd deamon
Error Message IDEHSD-2-MOUNT: [chars] online
Explanation Flash daemon mounting slot
Recommended Action No action is required.
Error Message IDEHSD-2-UMOUNT: [chars] offline
Explanation Flash daemon un mounting slot
Recommended Action No action is required.
Error Message IDEHSD-2-USB_SWAP: USB insertion or removal detected
Explanation USB swap event
Recommended Action No action is required.
Error Message IDEHSD-3-DEVICEOPEN_FAILED: device open failed. Component [chars]
Explanation The flash daemon device open failed The failure is due to the sub-component [chars]
Recommended Action No action is required.
Error Message IDEHSD-5-DISK_SWAP: [chars] [chars]
Explanation Compach flash swap event
Recommended Action No action is required.
Error Message IDEHSD-6-DISK_BUSY: trying to un mount disk [chars]
Explanation Flash daemon trying to umount busy slot
Recommended Action No action is required.
Error Message IDEHSD-6-DISK_EVENT: slot [dec] [chars]
Explanation Flash daemon found a disk hotswap handler event
Recommended Action No action is required.
Error Message IDEHSD-6-IDEHSD_INFO: [chars]
Explanation Flash daemon informational message
Recommended Action No action is required.
Error Message IDEHSD-6-IOCTL: ioctl: [chars] returns [dec]
Explanation Flash daemon trying to umount busy slot
Recommended Action No action is required.
Error Message IDEHSD-6-STARTING: deamon started
Explanation The compact flash swap daemon successfully started
Recommended Action No action is required.
Error Message IDEHSD-7-IDEHSD_TRACE: [chars]() [chars]:[dec] disk=[dec]
Explanation Flash daemon debug message to trace code path
Recommended Action No action is required.
This section contains the IFTMC messages.
Error Message IFTMC-SLOT#-1-IFTMC_GENERIC_ERROR: [chars]
Explanation [chars]
Recommended Action No action is required.
Error Message IFTMC-SLOT#-1-IFTMC_MPLS_SUBINTF_WARNING: Please enable mpls on main interface also, for subinterface mpls forwarding to work
Explanation MPLS on subinterface cannot work without enabling on main interface. Please configure on main interface too.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTERFACE_INTERNAL_ERROR: Internal error: [chars]:[chars], collect output of show tech-support eltm
Explanation IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support eltm
Explanation IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTF_NOT_FOUND: Interface [chars] not found in IFTMC database [chars]
Explanation IFTMC database doesn't have the interface.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTF_NOT_SUPP: Interface [chars] not supported by IFTMC [chars]
Explanation IFTMC doesn't support the interface for the specified operation
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTF_TO_LTL: Failed to get LTL for interface [chars] return status [chars]
Explanation IFTMC Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INTF_TO_SLOT: Failed to get slot for interface [chars] return status [chars]
Explanation IFTMC Failed to get Slot for interface. Port-channels and L2 Learning might be effected
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_INVALID_FTAG_NUM: IFTMC received INVALID Number of FTAGs in the message.. [chars]
Explanation IFTMC Failed: Received INVALID Ftags
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_INTF: Failed to allocate L2 LIF entries in forwarding engine for interfac [chars]
Explanation IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_VDC: Failed to allocate L2 LIF entries in forwarding engine
Explanation IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding in this VDC
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_L3_INGRESS_LIF_ALLOC_FAIL_INTF: Failed to allocate L3 Ingress LIF entries in forwarding engine for interfac [chars]
Explanation IFTMC Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect Layer 3 forwarding for the interface
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_RSVD_VLAN: Failed to get the reserved vlans. Failed with error [chars]
Explanation IFTMC Failed to get the reserved vlan's. This will effect multicast forwarding on SVI interfaces
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-ELTMC_VLAN_INTERNAL_ERROR: Internal error: VLAN [dec]:[chars], collect output of show tech-support eltm
Explanation IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-IFTMC_FCOE_FEATURE_REQ_FAIL: FCOE feature request for interface [chars] cannot be processed
Explanation FCOE feature request cannot be processed with ILM sharing, failure status does not get returned to calling app. Possible ACLQOS verify/commit fail prior to this feature request.
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-IFTMC_RES_ALLOC_FAIL: IFTMC resource allocation failure: [chars]
Explanation IFTMC failed resource allocation
Recommended Action No action is required.
Error Message IFTMC-SLOT#-2-IFTMC_RSVD_VLAN: FEX_RESERVED_VLAN_ERR: [chars]
Explanation VLAN_MGR SDB call returned FAILURE for FEX
Recommended Action No action is required.
This section contains the IKE messages.
Error Message IKE-3-CRYPTO_INIT_ERROR: IKEv2 crypto init error: [chars]
Explanation Crypto initialization error
Recommended Action No action is required.
Error Message IKE-3-ENABLE_ERROR: Unable to store enable flag in configuration (error-id [hex]).
Explanation Service failed to store the enable flag in configuration. As a result, it will exit
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.
Error Message IKE-3-FIPS_MODE_ERROR: Could not set FIPS mode
Explanation The FIPS mode could not be set by IKE
Recommended Action No action is required.
Error Message IKE-3-IKE_PROGRAM_EXIT: [chars]
Explanation IKE process did an abnormal exit
Recommended Action No action is required.
Error Message IKE-3-MAX_HALF_CONN_LIMIT_REACHED: IKEv1 : Exceeded the limit for number of half open Phase 1 connections
Explanation The number of half open connections has exceeded the maximum limit
Recommended Action No action is required.
Error Message IKE-3-PHASE1_NEGOTIATION_FAILED: IKEv1: Phase 1 negotiation failed for peer [chars]
Explanation IKE policy negotiation failed for peer [chars].
Recommended Action No action is required.
Error Message IKE-3-PHASE1_PROPOSAL_MISMATCH: IKEv1: No matching phase 1 proposal found for peer [chars]
Explanation There is a IKE policy mismatch for the peer.
Recommended Action No action is required.
Error Message IKE-3-PHASE2_NEGOTIATION_FAILED: IKEv1: Phase 2 negotiation failed for peer [chars]
Explanation IPsec policy negotiation failed for peer [chars].
Recommended Action No action is required.
Error Message IKE-3-PHASE2_PROPOSAL_MISMATCH: IKEv1: No matching phase 2 proposal found for peer [chars]
Explanation There is a IPsec policy mismatch for the peer.
Recommended Action No action is required.
Error Message IKE-3-UNSUPPORTED_EXCHANGE: IKEv1: Unsupported exchange [dec] received from [chars]
Explanation A unsupported IKE exchange type [digits] was received from [chars]
Recommended Action No action is required.
Error Message IKE-4-INVALID_PAYLOAD_APPEAR: IKEv2 received message (from [chars]) with payload ([chars]) appeared in [chars]([chars])
Explanation Received a payload in an inappropriate exchange
Recommended Action No action is required.
Error Message IKE-4-MESSAGE_ERROR: IKEv2 message (from [chars]) message error: [chars]
Explanation Received a malformed message which doesn't adhere to the protocol
Recommended Action No action is required.
Error Message IKE-4-PARSING_ERROR: IKEv2 message (from [chars]) parsing error: [chars]
Explanation Received a malformed message which can not be parsed appropriately
Recommended Action No action is required.
Error Message IKE-4-UNKNOWN_PAYLOAD: IKEv2 received message (from [chars]) with un-recognized payload ([chars])
Explanation Received an invalid payload
Recommended Action No action is required.
Error Message IKE-4-UNSUPPORT: [chars] is not supported (message from [chars])
Explanation Received something unsupported
Recommended Action No action is required.
Error Message IKE-6-POLL_START_DONE: IKE is exiting since it is not enabled
Explanation IKE is exiting since it is not enabled in the configuration
Recommended Action No action is required.
This section contains the ILC-SPAN messages.
Error Message ILC-SPAN-3-ERROR: [chars]
Explanation Ilc_span_mgr 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.
This section contains the IMAGE_DNLD messages.
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_FAILED: Module image download process failed. [chars]
Explanation Addon image download to module failed. This module is not operational until an addon image has been successfully installed.
Recommended Action Verify the location and version of your module image. Use the install module cli command to download a new module image.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_COMPLETE: Module image download process. [chars]
Explanation Image download completed. Module image is being installed.
Recommended Action No action is required.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FAILED: Module image download process. [chars]
Explanation Image download failed. Module may be inoperable.
Recommended Action Use show module cli command to verify the state of this module. Retry image download with install module cli command.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_CHECK_ERROR: File System check failed: [chars]
Explanation File system consistency check failed
Recommended Action File-system repair is needed using fsck
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_STARTED: Module image download process. [chars]
Explanation Image download started. Module image downloads are non-disruptive to module operation.
Recommended Action No action is required.
Error Message IMAGE_DNLD-SLOT#-4-IMG_DNLD_FILE_SYSTEM_RECREATION: [chars]. Partition was erased and successfully recreated.
Explanation File system checking and recreation if necessary for \/images\.
Recommended Action No action is required.
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_COMPLETE: Addon module image download process completed. [chars]
Explanation Addon image download to module has completed.The module should now be installing this new image.
Recommended Action This message is informational only.
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_STARTED: Addon module image download process started. [chars]
Explanation Addon image download to module has started. This is a disruptive download and this module will be inoperable until this download process is complete.
Recommended Action This message is informational only.
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_SUCCESSFUL: Addon module image download and install process successful. [chars]
Explanation Addon image download and install to module is successful.
Recommended Action Use the show module cli command to verify the module's operational status.
This section contains the IMP messages.
Error Message IMP-5-IMP_DISABLED: IMP Disabled
Explanation IMP Service Disabled
Recommended Action No action is required.
Error Message IMP-5-IMP_ENABLED: IMP Enabled
Explanation IMP Service nabled
Recommended Action No action is required.
This section contains the IM messages.
Error Message IM-3-IM_IF_FEATURE_BIND_FAILURE: Interface feature bind failed [chars]
Explanation Interface feature bind failed, so applications in that feature set may not behave correctly.
Recommended Action No action is required.
Error Message IM-3-IM_LC_OFFLINE_ERROR: LC Offline could not be sent to vdc:[dec]
Explanation LC Offline was not relayed to some vdc, so applications may not behave correctly.
Recommended Action No action is required.
Error Message IM-3-IM_RESP_ERROR: Component [chars] opcode:[chars] in vdc:[dec] returned error:[chars]
Explanation Some component returned an error.
Recommended Action No action is required.
Error Message IM-3-IM_SEQ_ERROR: Error ([chars]) while communicating with component [chars] opcode:[chars] (for:[chars])
Explanation Some component did not respond to a request in stipulated time.
Recommended Action No action is required.
Error Message IM-5-IM_DEMUX_ERROR: [chars]
Explanation Demux function returned error
Recommended Action No action is required.
Error Message IM-5-IM_INTERNAL_ERROR: [chars]
Explanation Internal error occurred
Recommended Action No action is required.
Error Message IM-5-IM_MGMT_INTF_STATE: [chars] [chars]
Explanation Management interface state changed.
Recommended Action No action is required.
Error Message IM-5-IM_UNKNOWN_INTERFACE: [chars]
Explanation Interface is not supported or not found
Recommended Action No action is required.
This section contains the INSTALLER messages.
Error Message INSTALLER-1-UPGRADE_EXCEEDED_DOWNTIME: Switch control plane down more than 80 seconds.
Explanation This message indicates that control plane was down for more than 80 seconds.
Recommended Action No action is required.
Error Message INSTALLER-5-UPGRADE_ABORTED: System upgrade aborted.
Explanation This message indicates that system wide upgrade has aborted.
Recommended Action No action is required.
Error Message INSTALLER-5-UPGRADE_COMPLETED: System upgrade completed.
Explanation This message indicates system wide upgrade has completed.
Recommended Action No action is required.
Error Message INSTALLER-5-UPGRADE_INITIATED: System upgrade initiated.
Explanation System wide upgrade has been initiated by the user.
Recommended Action No action is required.
Error Message INSTALLER-5-UPGRADE_LOW_SPACE: System upgrade stopped. Please [chars]
Explanation This message indicates that memory available to perform issu is low.
Recommended Action No action is required.
Error Message INSTALLER-5-UPGRADE_STOPPED: System upgrade stopped.
Explanation This message indicates that system wide upgrade has been stopped by the user.
Recommended Action No action is required.
This section contains the INTERFACE_VLAN messages.
Error Message INTERFACE_VLAN-4-SVI_IF_CONFIG_DELETED_NOTIF_DELAYED_DROPPED: Interface VLAN Delete Notification Not Processed on Time by SAP [dec] ([chars])
Explanation This SAP took long time in processing Interface VLAN delete notification and caused timeout
Recommended Action No action is required.
Error Message INTERFACE_VLAN-4-SVI_IF_CONFIG_REMOVED_NOTIF_DELAYED_DROPPED: Interface VLAN Remove Notification Not Processed on Time by SAP [dec] ([chars])
Explanation This SAP took long time in processing Interface VLAN remove notification and caused timeout
Recommended Action No action is required.
Error Message INTERFACE_VLAN-4-SVI_VLAN_DOES_NOT_EXIST: Vlan [dec] does not exist
Explanation Vlan not created before assignment
Recommended Action Interface-vlan
Error Message INTERFACE_VLAN-4-SVI_WARN_SVI_UP_IN_NON_ROUTABLE_VDC: Interface VLAN [dec] is being kept up in non-routable VDC. Reason: management configuration enabled. Please disable all the routing protocols
Explanation Keeping Interface VLAN up in non-routable VDC may cause potenital traffic blackhole
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down(Administratively Down)
Explanation Interface has been configured to be administratively down
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down. Reason [dec]
Explanation The interface encountered an error while configuring it
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive)
Explanation Interface VLAN has been suspended or deleted
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_DISABLED: SVI Disabled
Explanation SVI Service Disabled
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_ENABLED: SVI Enabled
Explanation SVI Service Enabled
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_GET_MAC_FAILED: Failed to acquire MAC address for SVI [hex]
Explanation SVI failed to acquire MAC address
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_INIT: SVI intialization failed with error [hex]
Explanation SVI initialziation error
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_IOD_RELEASE_ERROR_RESPONSE: IM failed to release SVI IOD error [hex]
Explanation IM failed to release SVI IOD
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_MTS_SEND_FAILURE: MTS send failure for opcode [dec], error [hex]
Explanation SVI encountered an error in with MTS message
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_MTS_TIME_OUT: MTS send timed out
Explanation SVI did not recieve response for mts message
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_RSRVD_VLAN_FAILED: Failed to get list of reserved vlans [hex]
Explanation SVI failed to get the list reserved vlans
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_SDB_UPDATE_FAILED: sdb update failed with ret_val [dec]
Explanation SDB updated failed for SVI
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-SVI_SEC_VLAN_FAILED: Failed to get list of secondary vlans [hex]
Explanation SVI failed to get the list of secondary vlans
Recommended Action No action is required.
Error Message INTERFACE_VLAN-5-UPDOWN: Line Protocol on Interface [chars], changed state to [chars]
Explanation Line protocol status changed for an interface
Recommended Action No action is required.
This section contains the IOA_LC messages.
Error Message IOA_LC-5-IOA_DISABLED: IOA Disabled
Explanation IOA Service Disabled
Recommended Action No action is required.
Error Message IOA_LC-5-IOA_ENABLED: IOA Enabled
Explanation IOA Service nabled
Recommended Action No action is required.
This section contains the IPFIB messages.
Error Message IPFIB-2-FIB_HW_ECMP_ADJ_CREATE_FAILURE: ECMP hardware programming failed.
Explanation Programming of ECMP adjacency in hardware failed. Programming only one next-hop.
Recommended Action No action is required.
Error Message IPFIB-2-FIB_HW_ECMP_AUTO_RECOVERY_COMPLETE: ECMP auto recovery completed. [dec] v4 and [dec] v6 routes recovered.
Explanation ECMP auto recovery process completed.
Recommended Action No action is required.
Error Message IPFIB-2-FIB_HW_ECMP_AUTO_RECOVERY_PARTIAL_COMPLETE: ECMP auto recovery partially completed. [dec] v4 and [dec] v6 routes recovered.
Explanation ECMP auto recovery process completed. Routes were recovered partially
Recommended Action No action is required.
Error Message IPFIB-2-FIB_HW_ECMP_AUTO_RECOVERY_START: ECMP auto recovery start.
Explanation ECMP auto recovery process started.
Recommended Action No action is required.
Error Message IPFIB-2-FIB_WEIGHTED_ROUTES_NOT_SUPPORTED: Weighted Routes are not supported in Resilient Mode. Disable using CLI:"no hardware profile ecmp resilient"
Explanation Weighted Routes are not supported in Resilient Mode.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_ECMP_AUTO_RECOVERY_DISABLED: ECMP auto recovery disabled.
Explanation ECMP auto recovery disabled.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_ECMP_AUTO_RECOVERY_ENABLED: ECMP auto recovery enabled, trigger will kick-in if atleast [dec] hardware ECMP path(s) are free.
Explanation ECMP auto recovery enabled.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_ECMP_FP_ENTRY_EXHAUSION: Hardware MPLS ACL entries exceeded in hardware TCAM, ECMP MPLS forwarding may not work.
Explanation Hardware ACL resources exhausted
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_ECMP_TABLE_FULL: ECMP hardware table full.
Explanation ECMP hardware table full condition detected.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_IPV4_TUNNEL_DECAP_TABLE_FULL_CLRD: IPv4 tunnel decap hardware table full exception cleared
Explanation The Tunnel IPv4 decap table is with in limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_IPV4_TUNNEL_DECAP_TABLE_FULL: IPv4 tunnel decap hardware table full. IP tunnel decapsulation may not work for some GRE/IPinIP traffic
Explanation The Tunnel V4 decap table is full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_IPV6_TUNNEL_DECAP_TABLE_FULL_CLRD: IPv6 tunnel decap hardware table full exception cleared
Explanation The Tunnel IPv6 decap table is with in limits.
Recommended Action Ipfib
Error Message IPFIB-SLOT#-2-FIB_HW_IPV6_TUNNEL_DECAP_TABLE_FULL: IPv6 tunnel decap hardware table full. IP tunnel decapsulation may not work for some GRE/IPinIP traffic
Explanation The Tunnel V6 decap table is full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_IP_TUNNEL_DECAP_TABLE_FULL_CLRD: IP TUNNEL decap hardware table full exception cleared
Explanation The Tunnel decap table is with in limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_IP_TUNNEL_DECAP_TABLE_FULL: IP TUNNEL decap hardware table full. IP tunnel decapsulation may not work for some GRE/IPinIP traffic
Explanation The Tunnel decap table is full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_MPLS_IIF_ENTRY_EXHAUSION: MPLS L3 IF hardware table full. MPLS forwarding may not work on this linecard
Explanation MPLS L3 IF hardware table full condition detected
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_MPLS_TUNNEL_TABLE_FULL: MPLS TUNNEL hardware table full. MPLS tunnel encapsulation may not work for IP->MPLS traffic on this linecard
Explanation MPLS TUNNEL hardware table full condition detected
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_TUNNEL_DMAC_TABLE_FULL: MPLS DMAC hardware table full. MPLS forwarding may not work on this linecard
Explanation MPLS DMAC hardware table is full. MPLS forwarding may not work on this linecard
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_HW_TUNNEL_ENCAP_TABLE_FULL: MPLS Encap hardware table full. MPLS tunnel encap/decap may not work on this linecard
Explanation MPLS Encap hardware table is full. MPLS tunnel encap/decap may not work on this linecard
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_BIDIR_ACL_MISSING_N3K: MCAST-BIDIR TCAM region not carved , use 'hardware profile tcam region mcast-bidir 256' to carve the region.
Explanation FIB MCAST-BIDIR tcam not carved
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_BIDIR_ACL_MISSING: mcast-bidir TCAM region not carved on unit: [dec] or failed init. Use 'hardware profile tcam resource template
Explanation FIB MCAST Bidir tcam not carved
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_LIMIT_REACHD: Multicast Route Limit Exceeded.
Explanation The Multicast Route Limit in the host table has reached.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_LOAD_BALANCING: OIFL Sharing Enabled. Load Balancing for Multicast traffic across groups is not possible.
Explanation OIFL Sharing Enabled. Load Balancing for Multicast traffic across groups is not possible.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_REPL_RESOURCE_EXHAUSTION: FIB MCAST replication resource exhaustion
Explanation FIB MCAST replication resource exhaustion. Failed to program IPMC index [dec] on unit [dec]
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MCAST_TABLE_FULL: Multicast route add failed due to Table full or Hash collision. vrf/vlan [dec] group [chars] source [chars].
Explanation The multicast route table is full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_MPLS_EGRESS_SW_INDEX_ALLOC_FAILURE: MPLS egress software index alloc failure
Explanation FIB MPLS egress sw index alloc failure
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXCEP_CLRD: FIB TCAM resource usage exception cleared
Explanation The TCAM device in the L3 forwarding ASIC is within system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXCEP_LPM_65_TO_127_IPV6_CLRD: FIB TCAM resource usage exception for IPV6 routes in LPM-65_TO_127 cleared
Explanation The TCAM device in the L3 forwarding ASIC is within system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_HOST_IPV4: FIB TCAM exhausted for IPV4 routes in Host table, IPV4 Host routes will be programmed in LPM table if possible
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV4 entries in host table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_HOST_IPV6: FIB TCAM exhausted for IPV6 routes in Host table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV6 entries in host table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_HOST: FIB TCAM exhausted for IPV4/IPV6 routes in the Host table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV4/IPV6 entries in the host table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_LPM_128_IPV6: FIB TCAM exhausted for IPV6 routes in LPM-128 table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV6 entries in LPM-128 table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_LPM_65_TO_127_IPV6: FIB TCAM exhausted for IPV6 routes in LPM-65_TO_127 table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV6 entries in LPM-65_TO_127 table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_LPM_IPV4: FIB TCAM exhausted for IPV4 routes in LPM table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV4 entries in LPM table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_LPM_IPV6: FIB TCAM exhausted for IPV6 routes in LPM table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV6 entries in LPM table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION_LPM: FIB TCAM exhausted for IPV4/IPV6 routes in the LPM table
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits for IPV4/IPV6 entries in the LPM table.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TCAM_RESOURCE_EXHAUSTION: FIB TCAM exhausted
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TRIE_RESOURCE_EXCEP_CLRD: FIB TRIE resource usage exception cleared
Explanation The TRIE resources in the L3 forwarding ASIC is within system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TRIE_RESOURCE_EXHAUSTION_LPM_IPV4: FIB TRIE exhausted for IPV4 LPM routes
Explanation The TRIE tiles in the L3 forwarding ASIC has reached its system limits for IPV4 entries
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TRIE_RESOURCE_EXHAUSTION_LPM_IPV6: FIB TRIE exhausted for IPV6 LPM routes
Explanation The TRIE tiles in the L3 forwarding ASIC has reached its system limits for IPV6 entries
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-FIB_TUNNEL_DEL_PENDING: Tunnel [hex] delete in-progress, please wait for completion
Explanation Tunnel interface is deleted but there are still routes depend on it
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TAHOE_TCAM_SIZE_BELOW_FULL: Tcam resource is available in IPSG tcam region[[dec]/[dec]].
Explanation Can add new TCAM entries. tcam resource is available.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TAHOE_TCAM_SIZE_BELOW_THRESHOLD: IPSG tcam region's usage has been below its threshold [dec]% [[dec]/[dec]].
Explanation Less than 90 percent of entries are used in TCAM IPSG region
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TAHOE_TCAM_SIZE_FULL: No resource available in IPSG tcam region[[dec]/[dec]].IPSG tcam is full.
Explanation Cannot add new TCAM entries. All entries are used.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TAHOE_TCAM_SIZE_OVER_THRESHOLD: IPSG tcam region's usage has reached its threshold [dec]% [[dec]/[dec]].
Explanation More than 90 percent of entries are used in TCAM IPSG region
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TCAM_SIZE_BELOW_FULL: Tcam resource is available in IPSG tcam region[[dec]/[dec]] on instance [dec] of Slot [dec].
Explanation Can add new TCAM entries. tcam resource is available.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TCAM_SIZE_BELOW_THRESHOLD: IPSG tcam region's usage has been below its threshold [dec]% [[dec]/[dec]] on instance [dec] of Slot [dec]
Explanation Less than 90 percet of entries are used in TCAM IPSG region
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TCAM_SIZE_FULL: No resource available in IPSG tcam region[[dec]/[dec]] on instance [dec] of Slot [dec].IPSG tcam is full.
Explanation Cannot add new TCAM entries. All entries are used.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TCAM_SIZE_OVER_THRESHOLD: IPSG tcam region's usage has reached its threshold [dec]% [[dec]/[dec]] on instance [dec] of Slot [dec]
Explanation More than 90 percet of entries are used in TCAM IPSG region
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-IPFIB_IPSG_TCAM_SIZE_ZERO: IPSG tcam region is not configured. Please configure IPSG TCAM region and retry
Explanation Cannot add TCAM entries. IPSG TCAM region is not configured.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-LFIB_HASH_COLLISION: MPLS label create failed due to hash collision for [chars] unit [dec] VRF: [dec], [dec], flags:[hex], Error: [chars]([hex])
Explanation MPLS Label creation failed due to hash collision
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-LFIB_MAX_LABEL_STACK_LIMIT_REACHED: Max Label count exceeded, truncating the label stack
Explanation Max limit for number of labels in the stack exceeded hence pruning extra labels.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_BIDIR_GENERIC_ERROR: Unexpected confition verified. [chars] . Please collect mifib logs
Explanation Generic bidir error
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_MAX_BIDIR_GRP_RANGE_REACHED: Num of BiDir group ranges installed [dec] has reached maximum Bidir group range limit. Please correct the Bidir config to be within limit
Explanation Num of maximum Bidir group ranges supported exceeded
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_MAX_BIDIR_ROUTES_REACHED_EXPAND: Num of BiDir routes installed exceeded max allowed [dec] while expanding ([chars]/[dec]). Please correct the Bidir config to be within limit
Explanation Num of maximum Bidir routes supported exceeded
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_MAX_BIDIR_ROUTES_REACHED: Num of BiDir routes installed exceeded max allowed [dec] . Please correct the Bidir config to be within limit
Explanation Num of maximum Bidir routes supported exceeded
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_MAX_ROUTE_LIMIT_REACHED: Maximum number of routes reached.(8192)
Explanation The maximum number of total (*,G) and (S,G) allowed on the system are 8192. And this limit is reached
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_NON_SSM_TO_SSM_CONV: Converting Routes from Non-SSM to SSM. Please run "clear ip mroute *".
Explanation Converting Routes from Non-SSM to SSM. Clear all routes
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-MFIB_SSM_TO_BIDIR_CONV: Converting Routes from SSM to Bidir. Please run "clear ip mroute *".
Explanation Converting Routes from SSM to Bidir. Clear all routes
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_GRP_CREATE: Multicast IPv4 (*,G) create failed for [chars]
Explanation Multicast group creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_GRP_UPDATE: Multicast IPv4 (*,G) update failed for [chars]
Explanation Multicast group update failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_INVALID_ARGUMENT: Multicast IPv4 invalid argument for (*,[chars])
Explanation Multicast invalid argument
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_MCAST_DA_TCAM_FULL: Multicast DA TCAM resource exhaustion ([chars])
Explanation Multicast DA TCAM FULL
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_MCAST_SA_TCAM_FULL: Multicast SA TCAM resource exhaustion ([chars])
Explanation Multicast SA TCAM FULL
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_MCINFO_L2PTR: Multicast IPv4 get mcinfo l2ptr failed for ([chars],[chars])
Explanation Multicast mcinfo l2ptr error
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_MCINFO_LOC: Multicast IPv4 mcinfo get location failed for ([chars],[chars])
Explanation Multicast mcinfo get loc error
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_MCINFO_WRITE: Multicast IPv4 mcinfo programming failed for ([chars],[chars])
Explanation Multicast mcinfo creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_SG_CREATE: Multicast IPv4 (S,G) create failed for ([chars],[chars])
Explanation Multicast (S,G) creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_SG_PGM: Multicast IPv4 (S,G) programming failed for ([chars],[chars])
Explanation Multicast (S,G) programming failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_SG_UPDATE: Multicast IPv4 (S,G) update failed for ([chars],[chars])
Explanation Multicast (S,G) update failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_SRC_CREATE: Multicast IPv4 source create failed for [chars]/[dec]
Explanation Multicast S/32 creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_TABLE_FULL: Multicast S/32 or G/32 create failed for ([chars],[chars]) due to hash collision
Explanation Insert failed due to hash collision
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V4_TCAM_INVALID_INDEX: Multicast IPv4 invalid tcam index for (*,[chars])
Explanation Multicast invalid tcam index
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_GRP_CREATE: Multicast IPv6 (*,G) create failed for [chars]
Explanation Multicast group creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_GRP_UPDATE: Multicast IP64 (*,G) update failed for [chars]
Explanation Multicast group update failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_INVALID_ARGUMENT: Multicast IPv6 invalid argument for (*,[chars])
Explanation Multicast invalid argument
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_MCINFO_L2PTR: Multicast IPv6 get mcinfo l2ptr failed for ([chars],[chars])
Explanation Multicast mcinfo l2ptr error
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_MCINFO_LOC: Multicast IPv6 mcinfo get location failed for ([chars],[chars])
Explanation Multicast mcinfo get loc error
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_MCINFO_WRITE: Multicast IPv6 mcinfo programming failed for ([chars],[chars])
Explanation Multicast mcinfo creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_SG_CREATE: Multicast IPv6 (S,G) create failed for ([chars],[chars])
Explanation Multicast (S,G) creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_SG_PGM: Multicast IPv6 (S,G) programming failed for ([chars],[chars])
Explanation Multicast (S,G) programming failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_SG_UPDATE: Multicast IPv6 (S,G) update failed for ([chars],[chars])
Explanation Multicast (S,G) update failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_SRC_CREATE: Multicast IPv6 source create failed for [chars]/[dec]
Explanation Multicast S/128 creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_TABLE_FULL: Multicast S/128 or G/128 create failed for ([chars],[chars]) due to hash collision
Explanation Insert failed due to hash collision
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-TAH_MFIB_V6_TCAM_INVALID_INDEX: Multicast IPv6 invalid tcam index for (*,[chars])
Explanation Multicast invalid tcam index
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_ADJ_ROLLBACK: Unicast adjacency create failed, rolling back for index: [dec], LIF: [dec], version: [dec], pos: [dec]
Explanation Unicast Routing route destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_BAD_SW_INDEX: Egress Object destroy: Bad sw-index for Egr-ID: [dec]
Explanation Unicast Routing route destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_EGRESS_TABLE_EXHAUSTION_CLEARED: Egress Adjacency Table Full exception cleared for unit [dec]
Explanation The TCAM device in the L3 forwarding ASIC is within system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_EGRESS_TABLE_EXHAUSTION: Egress Adjacency Table Full exception for unit [dec]
Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_HASH_COLLISION: Unicast host create failed due to hash collision for [chars] unit [dec] VRF: [dec], [chars], flags:[hex], Error: [chars]([hex])
Explanation Unicast Routing Host route creation failed due to hash collision
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_HOST_CREATE: Unicast host create failed for [chars] unit [dec] VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], Error: [chars]([dec])
Explanation Unicast Routing Host route creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_MALLOC_FAIL: Heap memory alloc fail at [chars] ([chars]:[dec]) type [dec] for [dec] bytes
Explanation Allocated heap has exceeded configured heap size
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_MULTIPATH_EGRESS_CREATE: Unicast Routing ECMP-[dec] for size [dec] creation failed [chars]([dec])
Explanation Unicast Routing multipath ecmp-group creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_MULTIPATH_EGRESS_MAX_CREATE: Unicast ecmp max size [dec] create fail [chars]([dec]) ([dec] [dec] [hex] [dec])
Explanation Unicast Routing multipath ecmp-group creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_MULTIPATH_TABLE_EXHAUSTION: Unicast ecmp table exhausted - max index [dec]
Explanation Unicast Routing multipath ecmp-group creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_ROUTE_CREATE: Unicast route create failed for [chars] unit [dec], VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], Error: [chars]([dec])
Explanation Unicast Routing route creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_SA_ROUTE_CREATE: Unicast route create failed in Multicast SA TCAM for [chars] unit [dec], VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], Error: [chars]([dec])
Explanation Multicast SA tcam route creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-2-UFIB_VOBJ_ROLLBACK: Unicast vobj create failed, rolling back for index:[dec], num-cnhs: [dec], bcm-nhcount: [dec], ecmp-id: [dec]
Explanation Unicast Routing route destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-FIB_MCAST_ROUTE_DELETION_FAILED: FIB MCAST route deletion failed
Explanation FIB MCAST route deletion failed Failed to delete hw route ([chars], [chars]) vlan [dec] on unit [dec]
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_BCM_MULTIPATH_EGRESS_DESTROY: Unicast Routing ecmp-group for unit [dec], index [dec] destroy failed [chars]([dec])
Explanation Unicast Routing multipath ecmp-group destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_HOST_DESTROY: Unicast host destroy failed for [chars] unit [dec] VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], Error: [chars]([dec])
Explanation Unicast Routing host route destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_MULTIPATH_EGRESS_DESTROY: Unicast Routing ecmp-group for index [dec] destroy failed [chars]([dec])
Explanation Unicast Routing multipath ecmp-group destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_ROUTE_DESTROY: Unicast route destroy failed for [chars] unit [dec] VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], Error: [chars]([dec])
Explanation Unicast Routing route destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_V4_EGRESS_CREATE: Unicast IPv4 Egress-create failed for [chars]/[chars], unit [dec], flags [hex], error: [chars]([dec])
Explanation Unicast Routing next-hop Egress object creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-3-UFIB_V6_EGRESS_CREATE: Unicast IPv6 Egress-create failed for [chars]/[chars], unit [dec], flags [hex], error: [chars]([dec])
Explanation Unicast Routing next-hop Egress object creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-FIB_HW_ENABLE_MPLS_TCAM_WARNING: MPLS TCAM region not carved , use 'hardware access-list tcam region' to carve a region.
Explanation Enable MPLS TCAM for MPLS forwarding to work
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-FIB_MCAST_TABLE_ALMOST_FULL: Multicast Route entry table is [dec]% full.
Explanation The Multicast Route entry table is threshold% full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-FIB_MCAST_TABLE_EXCEEDED_OR_FULL: Multicast Route entry table is [dec] exceeded or full.
Explanation The Multicast Route entry table is exceeded or full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-FIB_NS_CACHE_FULL: Forwarding cache entries for EOQs is full, some flows will not use EOQ buffers.
Explanation Cache entries needed for EOQ operation have reached its system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-FIB_TCAM_RESOURCE_WARNING: FIB TCAM usage is at 95 percent
Explanation The TCAM device in the L3 forwarding ASIC is reaching its system limits.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_BCM_EGRESS_DESTROY: Unicast Routing next-hop for unit [dec], index [dec] destroy failed [chars]([dec])
Explanation Unicast Routing multipath ecmp-group destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_DEFAULT_ROUTE: Default route created for VRF: [dec], [chars]/[dec], flags:[hex], intf:[hex], ret: [chars]([dec])
Explanation Unicast Routing route creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_ECMP_PROG: ECMP-id [hex] Mbr-cnt [dec] Intf [hex] Hw-egr-adj [dec]
Explanation Unicast Routing route creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_EGRESS_CREATE_PORT_INFO_MISSING: Unicast Routing next-hop creation port [dec] error [chars]
Explanation Unicast Routing next-hop creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_EGRESS_CREATE: Ucast IPv[dec] Egress sw-index [dec] Update in the same buffer as Create, Error!
Explanation Unicast Routing next-hop creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_EGRESS_DESTROY: Unicast Routing next-hop for index [dec] destroy failed [chars]([dec])
Explanation Unicast Routing multipath ecmp-group destroy failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_NH_BUFFER_FAILED: Cannot allocate SDK Next-hop buffer of size [dec]
Explanation Unicast Routing next-hop creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_NUM_EGRESS_CREATE: Flushing [dec] (FIB num-tlvs [dec]) Egress-create/update TLVs
Explanation Unicast Routing next-hop creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_PIXMC_ERR: Unicast adjacency dmod/dport lookup failed ifindex: [hex], lif:[dec] error [dec] ([chars])
Explanation Unicast Routing next-hop creation failed
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_PLATFORM_ERR: Unicast get platofrm card-id type failed
Explanation Unicast Routing failed to get the right fib mode for entry population
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_PLATFORM_TABLE_ID_ERR: Failed to get table id for intf [hex], vrf [dec]
Explanation Failed to get the table id
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_PLATFORM_VPN_ERR: Reserved / Unsupported vpn id passed, vrf [dec]
Explanation Reserved / Unsupported vpn id
Recommended Action No action is required.
Error Message IPFIB-SLOT#-4-UFIB_TABLE_THRESHOLD_REACHED: Unicast Routing [chars] table usage has reached [dec]% threshold
Explanation Unicast Routing Host/LPM Table usage has reached the threshold value
Recommended Action No action is required.
Error Message IPFIB-SLOT#-6-FIB_MCAST_TABLE_LESS_THAN_ALMOST_FULL: Multicast Route entry table is now less than [dec]% full.
Explanation The Multicast Route entry table is now less than threshold% full.
Recommended Action No action is required.
Error Message IPFIB-SLOT#-6-UFIB_TABLE_BELOW_THRESHOLD: Unicast Routing [chars] table usage has come below [dec]% threshold
Explanation Unicast Routing Host/LPM Table usage has come below the threshold value
Recommended Action No action is required.
This section contains the IPQOSMGR messages.
Error Message IPQOSMGR-2-QOSMGR_DCBXP_PFC_CMP_FAIL_MSG: [chars] - qos config [chars] not compatible with the peer
Explanation Port_id [chars] has qos config [chars] which is incompatible with the peer.
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_HA_FAILURE: Failed to do high availability operation: [chars].
Explanation Failed to do high availability operation. [chars] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_INIT_FAILED: Initialization failed for QoS Manager: [chars], reason: [hex].
Explanation Initialization failed for QoS Manager due to [chars], reason: [hex].
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_LLFC_APPLY_FAILURE_BUFFER_FULL: Unable to apply flow-control configuraiton on interface: [chars] due to \'[chars]\'. Please manually remove the configuration
Explanation Failed to apply flow-control configuration on Port_id [chars] due to error [chars]
Recommended Action Manually delete flow-control configuration on the port to keep the config accurate
Error Message IPQOSMGR-2-QOSMGR_LLFC_APPLY_FAILURE: Unable to apply flow-control configuraiton on interface: [chars] due to \'[chars]\'.
Explanation Failed to apply flow-control configuration on Port_id [chars] due to error [chars]
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_MTS_FAILURE: Failed to do MTS operation: [chars].
Explanation Failed to do MTS operation. [chars] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec].
Explanation MTS options setting to [hex] failed for opCode: [dec].
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_NETWORK_QOS_POLICY_CHANGE: Policy [chars] is now active
Explanation [chars] is the new active network-qos policy
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].
Explanation Failed to do PSS operation [chars]. [hex] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-2-QOSMGR_PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.
Recommended Action No action is required.
Error Message IPQOSMGR-3-QOSMGR_CONFIG_ERROR: Configuration error: [chars].
Explanation Configuration error. [chars] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-3-QOSMGR_NVDC_PFF_ERROR: PPF verify/commit failed in vdc [dec] error: [hex] for global qos command
Explanation For global qos command, PPF verify/commit failed in vdc [dec] with reason [hex].
Recommended Action No action is required.
Error Message IPQOSMGR-3-QOSMGR_PPF_ERROR: PPF library error: [chars].
Explanation PPF library errors. [chars] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-4-QOSMGR_ING_QUEUING_DCBX_WARNING: Input direction queuing config is being allowed for FCoE/DCBX exchange but will not be applied.
Explanation Input direction Queuing config is unsupported on N9K but config is being allowed for DCBX compatibility with peer.
Recommended Action No action is required.
Error Message IPQOSMGR-4-QOSMGR_LC_ERROR_MSG: Linecard [dec] returned an error: [chars]
Explanation Linecard [dec] returned an error message which is reported as [chars].
Recommended Action No action is required.
Error Message IPQOSMGR-4-QOSMGR_POLICIES_PRESENT_ON_DELETED_VLANS: Some VLANs (id: [chars]) which are getting deleted now are still having qos service-policy attached. These policies will be effective only when the VLANs get created again.
Explanation VLAN(s) [chars] is(are) getting deleted now. This is an informationsl message to notify that qos service-policies are present when the vlan is deleted. If the service-policies are not needed, please detach them from the vlans
Recommended Action No action is required.
Error Message IPQOSMGR-4-QOSMGR_PPF_WARNING: PPF library warning: [chars].
Explanation PPF library warning. [chars] is the reason.
Recommended Action No action is required.
Error Message IPQOSMGR-4-QOSMGR_WARNING_MSG: [chars] [dec]
Explanation QOSMGR warning messages is reported as [chars] [dec].
Recommended Action No action is required.
Error Message IPQOSMGR-5-QOSMGR_LC_STAT_SESSION_ERROR_MSG: Linecard [dec] returned the following error for [chars] session: [chars].
Explanation Linecard [dec] returned an error message for session of type [chars] which is reported as [chars]. This message may be seen during linecard reload if there is an active session going on.
Recommended Action No action is required.
Error Message IPQOSMGR-6-QOSMGR_DCBXP_CMP_FAIL_MSG: [chars] - qos config [chars] not compatible with the peer
Explanation Dcbxp warning: Port_id [chars] has qos config [chars] which is incompatible with the peer.
Recommended Action No action is required.
Error Message IPQOSMGR-6-QOSMGR_INFO: QOSMGR Info: [chars].
Explanation QOSMGR info is reported as [chars].
Recommended Action No action is required.
Error Message IPQOSMGR-6-QOSMGR_STATUS: QOSMGR Status: [chars].
Explanation QOSMGR status is reported as [chars].
Recommended Action No action is required.
This section contains the IPS messages.
Error Message IPS-2-ISCSI_IPS_INIT: IPS initialization of [chars] [chars]
Explanation IPS 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.
Error Message IPS-3-DUP_IPV4_ADDR_DETECTED: duplicate IP address ([chars]) sent from link address ([chars])
Explanation Duplicate IPv4 address is configured in the network
Recommended Action No action is required.
Error Message IPS-3-FCIP_FTA_ACCEL_CHAIN_ABORTED: Exch Aborted FC oxid [hex] My oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] (Internal [hex]:[hex])
Explanation FTA Exch being aborted
Recommended Action Informational no action required
Error Message IPS-3-FCIP_FTA_DATA_SENSE: Sense data with ERA [hex] sent to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Sense data with ERA sent
Recommended Action SYSLOGDOC_CONTACT_TAC
Error Message IPS-3-FCIP_FTA_ERA_35: ERA 0x35 presented to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP got an ERA 35
Recommended Action SYSLOGDOC_CONTACT_TAC
Error Message IPS-3-FCIP_FTA_ERA_38: ERA 0x38 received CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] at tape capacity: [dec] MB
Explanation FCIP got an ERA 38
Recommended Action SYSLOGDOC_CONTACT_TAC
Error Message IPS-3-FCIP_FTA_LOCATE_RBID_MISMATCH: Permanent Error due to Locate RBID Mismatch, CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP-FTA got a Permanent Error
Recommended Action Informational no action required
Error Message IPS-3-FCIP_FTA_PERM_ERR: Permanent Error, ERA [hex] rcvd CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] sense_byte[2,6]: [[hex], [hex]]
Explanation FCIP-FTA got a Permanent Error
Recommended Action Informational no action required
Error Message IPS-3-FCIP_FTA_RETRY_ERROR: [chars] retries [dec] FC oxid [hex] My oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FTA Command timed out
Recommended Action Informational no action required
Error Message IPS-3-FCIP_LINK_STAT_LOSS_OF_SYNC: [chars]: Loss of Sync ([chars])
Explanation FCIP Link Failed with Loss of Sync.
Recommended Action No action is required.
Error Message IPS-3-IPS_CRYPTO_FIPS_FAILED: IPS module [dec] has failed FIPS tests. FIPS info - [chars]
Explanation FIPS error occurred in the IPS module.
Recommended Action 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.
Error Message IPS-3-IPS_EGRESS_PERR: Parity error on dma-bridge egress. Count: [dec]
Explanation Parity error occured in dma-bridge egress direction.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message IPS-3-IPS_FIPS_MODE_ERROR: IPS FIPS error: [chars]
Explanation IPS module FIPS mode error
Recommended Action No action is required.
Error Message IPS-3-IPS_FIPS_TEST_FAILED: IPS FIPS compliance test failed
Explanation IPS FIPS compliance test failed
Recommended Action No action is required.
Error Message IPS-3-IPS_INGRESS_PERR: Parity error on dma-bridge ingress. Count: [dec]
Explanation Parity error occured in dma-bridge ingress direction.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message IPS-3-ISLB_CFS_CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the CFS lock. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_COMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while commiting the cfs config data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_CONFIG_FAILED: [chars]; [chars]
Explanation An error occurred while distributing the CFS config data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the CFS lock. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_ACTIVATION_FAILED: [chars]; [chars]
Explanation An error occurred while activating merged configuration. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_CLEARED: [chars]
Explanation Merge cleared, reason: [chars]
Recommended Action No action is required.
Error Message IPS-3-ISLB_CFS_MERGE_COMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while commiting the cfs merge config data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_CONFIG_FAILED: [chars]; [chars]
Explanation An error occurred while distributing the CFS merge config data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_FAILED: [chars]; [chars]
Explanation An error occurred while merging the iSLB CFS fabrics. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_PRECOMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while precommiting merge data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_MERGE_REQ_REJECTED: [chars]
Explanation Merge requested rejected, reason: [chars]
Recommended Action No action is required.
Error Message IPS-3-ISLB_CFS_MERGING_CONFIG_DB_FAILED: [chars]; [chars]
Explanation An error occurred while merging the config data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_PRECOMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while precommiting data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_PWWN_RESV_CLAIM_FAILED: [chars]
Explanation PWWN reservation claim failed. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_PWWN_RESV_RELEASE_FAILED: [chars]
Explanation PWWN reservation release failed. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the CFS lock. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_CFS_VRRP_DIST_FAILED: [chars]
Explanation An error occurred while distributing the VRRP CFS runtime data. The reason for the failure : [chars]
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.
Error Message IPS-3-ISLB_ZONE_ACTIVATION_FAILED: iSLB zoneset activation returned [hex] for VSAN [dec]
Explanation ISLB zoneset activation 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.
Error Message IPS-3-ISLB_ZONE_ACTIVATION_RETRY: iSLB zoneset activation returned [hex] for VSAN [dec]
Explanation ISLB zoneset activation failed. Zone server busy.
Recommended Action Retry the iSLB zonest activation.
Error Message IPS-3-ISLB_ZONE_NO_ACTIVE_ZONESET: iSLB zoneset activation returned [hex] for VSAN [dec]
Explanation ISLB zoneset activation failed. No active zoneset.
Recommended Action Activate a zoneset in the specified VSAN and retry
Error Message IPS-3-RED_PACKET_DROPS: Congestion detected on GigabitEthernet port (buffer pool size: [dec])
Explanation Congestion detected on GigabitEthernet port due to RED threshold limit
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.
Error Message IPS-4-FCIP_FTA_CFG_MISMATCH: [chars]: Mismatch in FCIP Ficon Tape Acceleration configuration with peer
Explanation The FCIP Ficon Tape Acceleration configuration does not match with peer's configuration
Recommended Action Fix the FCIP Ficon Tape Acceleration configuration to be consistent with the peer
Error Message IPS-4-FCIP_FTA_VSAN_UPDATE_WARNING: FCIP FICON tape acceleration VSAN update had an error ([chars]) on interface [chars] causing a flap of the interface
Explanation The FCIP FICON tape acceleration VSAN configuration experienced an error when disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and re-enabled as a result of this error to ensure data integrity.
Recommended Action No action is required.
Error Message IPS-4-FCIP_LICENSE_BIND_FAILED: Bind failed for [chars] due to [chars] for license failure; configuration accepted but bind failed
Explanation The FCIP configuration was accepted, but the FCIP interface did not bind to a physical interface because the appropriate license was not available. If a license becomes available in the future, this FCIP interface will bind to a physical interface automatically.
Recommended Action Check the license state with "show license usage" and acquire the necessary FCIP license
Error Message IPS-4-FCIP_XRCE_LICENSE_FAILED: XRC Acceleration deactivated due to license failure
Explanation The XRC Acceleration configuration was accepted, but will remain inactive until a valid license is available. When the appropriate license is installed, XRC accelaration will be activated.
Recommended Action Check the license state with "show license usage" and acquire the necessary XRC_ACCL license
Error Message IPS-4-FCIP_XRCE_LICENSE_INSTALLED: XRC Acceleration activated due to valid license
Explanation The XRC Acceleration configuration is activated as a valid license has been installed.
Recommended Action No action is required.
Error Message IPS-5-FCIP_BIND_FAILED: Bind failed for [chars] due to [chars] for [chars]
Explanation FCIP/ISCSI Interface bind to Ethernet port failed
Recommended Action No action is required.
Error Message IPS-5-FCIP_BPORT_KEEPALIVES_NOT_SUPPORTED: Bport Keepalives not supported for FCIP [chars]
Explanation Bport Keepalives not supported in this release
Recommended Action Informational no action required
Error Message IPS-5-FCIP_BPORT_NOT_SUPPORTED: Bport not supported for FCIP [chars]
Explanation Bport not supported in this releas
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_ALREADY_OFF: FTA Already Off, [chars] VSAN: [dec]
Explanation FTA Already Off
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_ALREADY_ON: FTA Already ON, [chars] VSAN: [dec]
Explanation FTA Already ON
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_CB_DOWN: FTA [chars] is DOWN
Explanation FTA is DOWN
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_CB_UP: FTA [chars], is UP
Explanation FTA is UP
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_DISBAND_GRP_CMD: Disband Group message processed PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP Disbanded a Group
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_EST_GRP_CMD: Path Group establised for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP established a Path Group
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS1: RSCN Cleanup Pass1 [chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]
Explanation Doing RSCN Cleanup, Pass 1
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS2: RSCN Cleanup Pass2 [chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]
Explanation Doing RSCN Cleanup, Pass 2
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_RESIGN_GRP_CMD: Resign group processed for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP Resigned a Group
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_RESP_3490: 3490 device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Device type discovered is 3490
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_RESP_3590: 3590 device discovered by FCIP CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Device type discovered is 3590
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_RESP_NOT_TAPE: Non-tape device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP discovered a non-tape device
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_TURN_OFF_LAST_VSAN: FTA turned off for the Last VSAN, [chars] VSAN: [dec]
Explanation FTA turned off for the Last Vsan
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_TURN_OFF_NONLAST_VSAN: FTA turned off for the Non-Last VSAN, [chars] VSAN: [dec]
Explanation FTA turned off for the Non-Last Vsan
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_TURN_ON: Turn ON FTA, [chars] VSAN: [dec]
Explanation FTA turned ON
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTA_WARNING: FTA Warning :[chars]
Explanation Generic FTA Warning
Recommended Action Informational no action required
Error Message IPS-5-FCIP_FTRA_CFG_MISMATCH: [chars]: Mismatch in FCIP FICON Tape Read Accelerator configuration with peer
Explanation The FCIP FICON Tape Read Accelerator configuration does not match with peer's configuration
Recommended Action Fix the FCIP FICON Tape Read Accelerator configuration to be consistent with the peer
Error Message IPS-5-FCIP_IF_CR_DEL: Interface [chars] [chars]
Explanation FCIP Interface was Created or Deleted
Recommended Action No action is required.
Error Message IPS-5-FCIP_MODE1_CHANGED_TO_MODE2: Changing mode1 compression to mode2 for [chars], on a MSM/SSN-16 linecard
Explanation Change mode1 compression to mode2 on a MSM/SSN-16 linecard
Recommended Action Informational no action required
Error Message IPS-5-FCIP_NUM_TCP_CONNS_MISMATCH: [chars]: configured for 2 tcp connections but currently operating with 1 connection
Explanation Number of configured tcp connections don't match number of connections currently up
Recommended Action No action is required.
Error Message IPS-5-FCIP_PEER_CAVIUM: Peer FCIP [chars] is a MSM/SSN-16 linecard
Explanation Peer linecard is a MSM/SSN-16
Recommended Action Informational no action required
Error Message IPS-5-FCIP_PEER_NON_CAVIUM: Peer FCIP [chars] is a non MSM/SSN-16 linecard
Explanation Peer linecard is non MSM/SSN-16
Recommended Action Informational no action required
Error Message IPS-5-FCIP_RA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Read Acceleration capability with peer
Explanation The FCIP Tape Read Acceleration capability does not match with peer's configuration
Recommended Action Fix the FCIP Tape Read Acceleration capability to be consistent with the peer
Error Message IPS-5-FCIP_SF_NOT_SUPPORTED: Special-Frame not supported for FCIP [chars]
Explanation Spl-Frame not supported in this release
Recommended Action Informational no action required
Error Message IPS-5-FCIP_TA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Acceleration configuration with peer
Explanation The FCIP Tape Acceleration configuration does not match with peer's configuration
Recommended Action Fix the FCIP Tape Acceleration configuration to be consistent with the peer
Error Message IPS-5-FCIP_TA_ITL_MISMATCH: [chars]: Mismatch in FCIP Write/Tape Acceleration software capability with peer
Explanation The FCIP Write/Tape Acceleration software capability does not match with peer's software capability
Recommended Action Fix the FCIP software to be consistent with the peer
Error Message IPS-5-FCIP_TSTAMP_CHK_FAILED: [chars]: Timestamp check failed on ingressing frames
Explanation Timestamp between local and remote side exceeds the configured tolerance
Recommended Action No action is required.
Error Message IPS-5-FCIP_UNBIND_FAILED: UNBIND failed for [chars] due to [chars] for [chars]
Explanation FCIP/ISCSI Interface UNBIND from Ethernet port failed
Recommended Action No action is required.
Error Message IPS-5-FCIP_WA_CFG_MISMATCH: [chars]: Mismatch in FCIP Write Acceleration configuration with peer
Explanation The FCIP Write Acceleration configuration does not match with peer's configuration
Recommended Action Fix the FCIP Write Acceleration configuration to be consistent with the peer
Error Message IPS-5-FCIP_WA_XFER_RDY_ERR: [chars]: FCIP Write Acceleration received XFER-RDY after exhcange cleanup. Host [hex] Target [hex]
Explanation FCIP Write/Tape Acceleration received XFER-RDY after exchange cleanup
Recommended Action No action is required.
Error Message IPS-5-FCIP_XRCE_CFG_MISMATCH: [chars]: Mismatch in FCIP XRC Emulator configuration with peer
Explanation The FCIP XRC Emulator configuration does not match with peer's configuration
Recommended Action Fix the FCIP XRC Emulator configuration to be consistent with the peer
Error Message IPS-5-IPS_IPACL_LOG_MSG: [chars]
Explanation Details of the packet dropped due to ACLs
Recommended Action No action is required.
Error Message IPS-5-IPS_MGR_FEATURE_ENABLE: ips:[dec] iscsi:[dec] fcip:[dec] iscsi-intf-vsan:[dec] ips-lc:[dec]
Explanation IPS Manager feature enabled/disabled
Recommended Action No action is required.
Error Message IPS-5-IPS_TCP_PORT_IN_USE: Cannot bringup interface [chars], local port already in use
Explanation FCIP and iSCSI interface are trying to use the same local port, please use different ports
Recommended Action No action is required.
Error Message IPS-5-ISCSI_BAD_DATA_DIGEST_CRC: iSCSI ingress data digest error from initiator [chars] alias [chars] S_ID [hex] to D_ID [hex]
Explanation ISCSI Ingress Data Digest CRC failed
Recommended Action No action is required.
Error Message IPS-5-ISCSI_CONN_DOWN_BATCH: [chars]: [dec] iSCSI sessions failed in last [chars], reason: [chars]
Explanation Number of iSCSI session down during the last time interval
Recommended Action No action is required.
Error Message IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI session down from initiator [chars] alias [chars] ip [chars] to target [chars], reason: [chars]
Explanation ISCSI session goes down
Recommended Action No action is required.
Error Message IPS-5-ISCSI_CONN_UP: [chars]: iSCSI session up from initiator [chars] alias [chars] ip [chars] to target [chars]
Explanation ISCSI session comes up and reaches Full-Feature phase
Recommended Action No action is required.
Error Message IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSI initiator [chars] alias [chars] ip [chars] target [chars]. FC session failed over to port [chars]
Explanation FC session for the iSCSI session failed over to newly active port
Recommended Action No action is required.
Error Message IPS-5-ISCSI_SB_GET_TGT: iSCSI SB get [dec] targets, initiator [chars] alias [chars] ip [chars]
Explanation ISCSI FCNS query response
Recommended Action No action is required.
Error Message IPS-5-ISCSI_SESSION_CREATE_FAILURE: [chars]: iSCSI Session initiator [chars] target [chars] create failed. [chars]
Explanation ISCSI Session Create failed
Recommended Action No action is required.
Error Message IPS-5-ISCSI_SESSION_CREATE_REDIRECT: [chars]: iSCSI Session initiator [chars] target [chars] redirected to [chars]/[chars]
Explanation ISCSI Session Create redirected
Recommended Action No action is required.
Error Message IPS-5-ISCSI_SESSION_REDIRECT_TIMEOUT: iSCSI Session initiator [chars] to [chars] redirected to [chars] timeout
Explanation ISCSI Session Redirect timeout
Recommended Action No action is required.
Error Message IPS-5-ISLB_CFS_SESSION_CLEARED: CFS Session Cleared
Explanation CFS Session Cleared by user
Recommended Action No action is required.
Error Message IPS-5-LRTP_HDR_FCID_MISMATCH: LRTP header s_id([hex]) d_id([hex]) do not match Inner header s_id([hex]) d_id([hex]) Initiator ([chars]) Target([chars])
Explanation The s_id and/or the d_id field in the frame's LRTP header does not match the s_id or d_id field in the inner header
Recommended Action No action is required.
Error Message IPS-5-PORT_IPCFG_FAILED: Cannot configure IP address for interface [chars]
Explanation Cannot configure IPS port IP address
Recommended Action No action is required.
Error Message IPS-5-SB_MGR_CORE_FAILED: Ethernet Processing core [chars] failed due to [chars]
Explanation Ethernet Processing Core failed
Recommended Action No action is required.
Error Message IPS-5-SFRAME_ENTITY_ID_MISMATCH: [chars]: special frame profile ID mismatch
Explanation Special frame received and destination profile ID does not match local profile ID
Recommended Action No action is required.
Error Message IPS-5-SFRAME_FABRIC_WWN_MISMATCH: [chars]: special frame fabric wwn mismatch
Explanation Special frame received and source/destination fabric wwn does not match local destination/ source fabric wwn
Recommended Action No action is required.
Error Message IPS-5-SFRAME_IF_ADMIN_DOWN: [chars]: special frame received if down
Explanation Special frame received and interface is admin down
Recommended Action No action is required.
Error Message IPS-5-SFRAME_IF_NOT_ENABLED: [chars]: special frame not enabled
Explanation Special frame received and interface special frame configuration is disabled
Recommended Action No action is required.
Error Message IPS-5-SFRAME_INVALID_NONCE: [chars]: special frame response has invalid nonce for FCIP
Explanation Special frame response has a different nonce than was originally sent in the special frame
Recommended Action No action is required.
Error Message IPS-5-SFRAME_NOT_RECV: [chars]: special frame was not received by passive-side FCIP
Explanation Special frame was not received by the passive-side of the FCIP TCP tunnel within given time period
Recommended Action No action is required.
Error Message IPS-5-SFRAME_RESP_MISMATCH: [chars]: special frame response has byte mismatch for FCIP
Explanation Special frame response has a mismiatch in one of the bytes from what was sent from the FCIP special frame sender
Recommended Action No action is required.
Error Message IPS-5-SFRAME_RESP_NOT_RECV: [chars]: special frame response was not received by active-side FCIP
Explanation Special frame response was not received by the active-side of the FCIP TCP tunnel within given time period
Recommended Action No action is required.
Error Message IPS-6-FCIP_FTA_READ_ACCEL_STARTED: Read Acceleration started for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP-FTA Read Acceleration started
Recommended Action Informational no action required
Error Message IPS-6-FCIP_FTA_READ_ACCEL_STOPPED: Read Acceleration stopped for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to [chars] after [dec] MB reads
Explanation FCIP-FTA Read Acceleration stopped
Recommended Action Informational no action required
Error Message IPS-6-FCIP_FTA_WRITE_ACCEL_STARTED: Write Acceleration started for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP-FTA Write Acceleration started
Recommended Action Informational no action required
Error Message IPS-6-FCIP_FTA_WRITE_ACCEL_STOPPED: Write Acceleration stopped for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to [chars] after [dec] MB writes
Explanation FCIP-FTA Write Acceleration stopped
Recommended Action Informational no action required
Error Message IPS-7-ISCSI_FCNS_QUERY_REQ: return [hex], wait [dec], VSAN [dec], Init: [chars]
Explanation ISCSI FCNS query
Recommended Action No action is required.
Error Message IPS-7-ISCSI_FCNS_QUERY_RESP: result [hex], [dec] targets, wait [dec], Init: [chars]
Explanation ISCSI FCNS query response
Recommended Action No action is required.
Error Message IPS-7-ISCSI_NEW_FCNS_QUERY_REQ: return [hex], VSANs [chars], Init: [chars]
Explanation ISCSI FCNS query
Recommended Action No action is required.
Error Message IPS-7-ISCSI_NEW_FCNS_QUERY_RESP: result [hex], [dec] entries, [dec] targets, [dec] total targets Init: [chars]
Explanation ISCSI FCNS query response
Recommended Action No action is required.
Error Message IPS-7-ISNS_SVR_ERR_RESPONSE: iSNS server returned following error code on iSNS request for interface [chars] : [dec]
Explanation ISNS server returned an error for register/deregister request. For select error codes iSNS client would retry and re-register all target nodes corresponding to the interface
Recommended Action No action is required.
This section contains the IPV6 messages.
Error Message IPV6-2-ALLOC_MEMORY: Memory allocation failed
Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Error Message IPV6-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error: [chars]
Explanation Writing to a file failed probably due to no space.
Recommended Action Ipv6
Error Message IPV6-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Error Message IPV6-4-DAD_FAILED_EVENT: Duplicate address detection failed for [chars] on [chars]
Explanation Duplicate address detection for IP address failed.
Recommended Action Ipv6
Error Message IPV6-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Explanation Configuration message that needs to be logged.
Recommended Action No action is required.
Error Message IPV6-6-INTERFACE_DELETED: The interface [chars] has been deleted
Explanation The specified interface has been deleted. The service will delete all the configuration on that interface.
Recommended Action No action is required.
Error Message IPV6-6-INTERFACE_EVENT: IP address [chars] [chars] on interface [chars]
Explanation The IP address [chars] has been successfully [chars] on the interface [chars].
Recommended Action No action is required.
Error Message IPV6-6-ROUTE_NOT_ACTIVE: The [chars] is not active
Explanation The specified route is successfully configured but currently is not active.
Recommended Action Check that the route is correct and the outgoing interface is operationally up.
Error Message IPV6-6-STARTING: IP configuration Manager started
Explanation The IP Configuration Manager service has successfully started.
Recommended Action No action is required.
This section contains the IP messages.
Error Message IP-1-DHCP_CLIENT_FAILED: dhcp-client failed to get the ip address
Explanation Dhcp-client failed to get the ip from server, probably due to server lease unavailability or cable disconnectivity .
Recommended Action Ip
Error Message IP-2-ALLOC_MEMORY: Memory allocation failed
Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Error Message IP-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error: [chars]
Explanation Writing to a file failed probably due to no space.
Recommended Action Ip
Error Message IP-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Error Message IP-4-DAD_FAILED_EVENT: Duplicate address detected for [chars] on [chars]
Explanation Duplicate address detected for IP address.
Recommended Action Ip
Error Message IP-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Explanation Configuration message that needs to be logged.
Recommended Action No action is required.
Error Message IP-6-DHCP_CLIENT_SUCCESS: dhcp_client got ip address:[chars],netmask:[chars] for mgmt interface,got from server:[chars]
Explanation Dhcp-client is able to get the ip address from server,
Recommended Action No action is required.
Error Message IP-6-INTERFACE_DELETED: The interface [chars] has been deleted
Explanation The specified interface has been deleted. The service will delete all the configuration on that interface.
Recommended Action No action is required.
Error Message IP-6-INTERFACE_EVENT: IP address [chars] [chars] on interface [chars]
Explanation The IP address [chars] has been successfully [chars] on the interface [chars].
Recommended Action No action is required.
Error Message IP-6-ROUTE_NOT_ACTIVE: The [chars] is not active
Explanation The specified route is successfully configured but currently is not active.
Recommended Action Check that the route is correct and the outgoing interface is operationally up.
Error Message IP-6-STARTING: IP configuration Manager started
Explanation The IP Configuration Manager service has successfully started.
Recommended Action No action is required.
This section contains the ISNS messages.
Error Message ISNS-2-ISNS_CFS_OPERATION_FAILED: iSNS CFS [chars] failed
Explanation ISNS CFS operation 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.
Error Message ISNS-2-ISNS_INIT: iSNS initialization of [chars] [chars]
Explanation ISNS 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.
This section contains the KIM messages.
Error Message KIM-2-KIM_BIND_MOUNT_FAILED: Bind mount of /proc/self/ns/net from pid [dec] for namespace [chars] failed with errno [dec] ([chars])
Explanation NS bind mount failed
Recommended Action No action is required.
Error Message KIM-2-KIM_GET_LNX_IFINDEX_FAILED: Failed to get linux ifindex for interface [chars] (ifindex [dec]). err: [dec] errno: [dec] (sock: [dec])
Explanation Get of linux ifindex failed
Recommended Action No action is required.
Error Message KIM-2-KIM_GET_RSVD_VLAN_FAILED: Failed to get the reserved vlan range
Explanation Get of reserved vlan range failed
Recommended Action No action is required.
Error Message KIM-2-KIM_MOUNT_BIND_FAILED: mount --bind of [chars] failed with errno: [dec] ([chars])
Explanation Mount bind failed
Recommended Action No action is required.
Error Message KIM-2-KIM_MOUNT_SHARED_FAILED: mount --make-shared of [chars] failed with errno: [dec] ([chars])
Explanation Mount shared failed
Recommended Action No action is required.
Error Message KIM-2-KIM_NS_CREATE_FAILED: Failed to create a new network namespace "[chars]". errno: [dec] ([chars])
Explanation Namespace creation failed
Recommended Action No action is required.
Error Message KIM-2-KIM_NS_FILE_NOT_PRESENT: Namespace file [chars] doesn't exist. access returned errno: [dec] ([chars])
Explanation NS file not present
Recommended Action No action is required.
Error Message KIM-2-KIM_NS_OPEN_FAILED: Open of [chars] failed with errno: [dec] ([chars])
Explanation NS file open failed
Recommended Action No action is required.
Error Message KIM-2-KIM_UNLINK_NETNS_FAILED: Unlink of namespace file [chars] from pid [dec] failed with errno: [dec] ([chars])
Explanation NS unlink failed
Recommended Action No action is required.
This section contains the L2MCAST messages.
Error Message L2MCAST-SLOT#-0-L2MCAST_CLI_INIT_FAILED: CLI library initialization failed!
Explanation L2MCAST failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-0-L2MCAST_TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation L2MCAST failed to initialize timer library. This is a fatal error.
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-2-L2MCAST_MAC_FULL_LC: Failed to insert entry in MAC table for FE [dec] swidx [dec] ([hex]) with err ([chars]). To avoid possible multicast traffic loss, disable OMF. Use the configuration CLI: "no ip igmp snooping optimise-multicast-flood"
Explanation Failed to program the MAC table. MAC table line full for this entry
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-2-L2MCAST_VLAN_NOT_FOUND: VLAN [dec] not found in L2MCAST database!
Explanation L2MCAST failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-2-L2MCAST: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-3-L2MCAST_HW_INSTALL_FAIL: Hw install failed for vlan [dec] ([dec], [chars], [chars]) entry!
Explanation L2MCAST failed to insert bd, g, s entry in hardware. Igmp snooping may not be effective on vlan for that group and source
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-6-L2MCAST_INITIALIZED: Internal state created [chars]
Explanation L2MCAST has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in L2MCAST was successful.
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_REMOVED: VDC [dec] Removed
Explanation L2MCAST has successfully removed VDC [dec] from its databases.
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_CREATED: VLAN [dec] created
Explanation L2MCAST has added VLAN [dec].
Recommended Action No action is required.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_REMOVED: VLAN [dec] removed from VDC [dec]
Explanation L2MCAST has successfully removed VLAN [dec] from VDC [dec].
Recommended Action No action is required.
This section contains the LACP messages.
Error Message LACP-3-GENERAL_ERROR: [chars]
Explanation General error
Recommended Action No action is required.
Error Message LACP-3-LACP_SUSPEND_HALF_DUPLEX_PORT: Port [chars] is in half duplex mode. suspend port
Explanation LACP is not supported in half duplex mode. Suspend port
Recommended Action No action is required.
Error Message LACP-3-LACP_SUSPEND_MINLINK: LACP port [chars] of port-channel [chars] is suspended as min-link requirement not met.
Explanation LACP suspend ports due to min-link
Recommended Action No action is required.
Error Message LACP-3-LACP_UPGRADE_READY_FAILED: Upgrade ready failed.
Explanation Upgrade ready event failed because atleast one port channel member is in intermediate state.
Recommended Action No action is required.
Error Message LACP-3-PACKET_TRANSMIT_ERR: [chars]: Could not send LACP packet err=[dec]
Explanation There was an error in sending LACP packet
Recommended Action No action is required.
Error Message LACP-3-SYN_COLL_DIS_EN: [chars] [[chars]]: SYNC, COLLECT and DISTRIBUTE flags enabled too early by partner
Explanation Potential interop issue. Partner system seems to have enabled sync as well collecting or distributing flags too early even before actor has selected an aggregator
Recommended Action No action is required.
Error Message LACP-3-SYSTEM_MAC_ERR: [chars]: Could not get system mac[[chars]]
Explanation There was an error in acquiring system mac from VDC Mgr
Recommended Action No action is required.
Error Message LACP-5-LACP_DISABLED: LACP Disabled
Explanation LACP Service Disabled
Recommended Action No action is required.
Error Message LACP-5-LACP_DOES_NOT_MEET_MINLINK_REQ: LACP port-channel [chars] is brought down as min-link requirement not met.
Explanation LACP port-channel down as min-link requirement not met
Recommended Action No action is required.
Error Message LACP-5-LACP_ENABLED: LACP Enabled
Explanation LACP Service Enabled
Recommended Action No action is required.
Error Message LACP-5-LACP_MEETS_MINLINK_REQ: LACP port-channel [chars] meets min-link requirement. Reint port-channel
Explanation LACP port-channel meets min-link requirement
Recommended Action No action is required.
Error Message LACP-5-LACP_RATE_FAST_NOT_RECOMENDED: 'lacp rate fast' not recomended if 'vpc peer-link' configured.
Explanation Can cause traffic outage
Recommended Action No action is required.
Error Message LACP-5-LACP_REMOTE_NOTIFY_SUCCESS: Remote notify event.
Explanation Remote notify event was successful.
Recommended Action No action is required.
Error Message LACP-5-LACP_REMOTE_PDU_SEND: Pre/Post ISSU hello sent.
Explanation Remote notify event was successful.
Recommended Action No action is required.
Error Message LACP-5-LACP_SUSPEND_INDIVIDUAL: LACP port [chars] of port-channel [chars] not receiving any LACP BPDUs suspending (individual) port
Explanation LACP suspend individual ports
Recommended Action No action is required.
Error Message LACP-5-LACP_UPGRADE_READY_SUCCESS: Upgrade ready successful.
Explanation Upgrade ready event is successful as all port channel members are in steady state.
Recommended Action No action is required.
Error Message LACP-5-PORT_PRIORITY_CHANGED: [chars]: LACP port priority changed from [dec] to [dec]
Explanation LACP port priority has been changed
Recommended Action No action is required.
Error Message LACP-5-SYSTEM_PRIORITY_CHANGED: LACP system priority changed from [hex] to [hex]
Explanation LACP system priority has been changed
Recommended Action No action is required.
This section contains the LC-SPAN messages.
Error Message LC-SPAN-3-ERROR: [chars]
Explanation Lc_span_mgr 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.
This section contains the LC_PORT_CHANNEL messages.
Error Message LC_PORT_CHANNEL-SLOT#-1-MALLOC_FAILED: cannot allocate memory (size [dec])
Explanation No enough memory
Recommended Action No action is required.
Error Message LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_IDXMAP_FAILURE: could not lookup port index for interface [chars]
Explanation Could not look up port index
Recommended Action No action is required.
This section contains the LDAP messages.
Error Message LDAP-2-LDAP_PROGRAM_EXIT: LDAP daemon exiting: [chars]
Explanation LDAP 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.
Error Message LDAP-3-LDAP_ERROR_MESSAGE: [chars]
Explanation LDAP Error Message
Recommended Action No action is required.
Error Message LDAP-5-LDAP_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Ldap server monitor status change
Recommended Action No action is required.
Error Message LDAP-5-LDAP_SERVER_STATUS: [chars] server [chars] with 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 Ldap server status change
Recommended Action No action is required.
Error Message LDAP-6-LDAP_MESSAGE: [chars]
Explanation LDAP Message
Recommended Action No action is required.
This section contains the LIBBASE_SVC messages.
Error Message LIBBASE_SVC-2-IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED: [chars] cannot be bound for site [chars], as the interfaces reached the maximum flow limit
Explanation IT Load Balancing failed
Recommended Action No action is required.
Error Message LIBBASE_SVC-2-LOG_ERR_BASE_SVC_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.
Error Message LIBBASE_SVC-4-FCR_VER2_NOT_ENABLED: FCR Version2 is not enabled. May affect flows. Please enable fc-redirect version2
Explanation FCR Version2 not enabled
Recommended Action No action is required.
Error Message LIBBASE_SVC-5-FLOW_NOT_ALLOWED: Flow [chars] <-> [chars] disallowed in multiple clusters
Explanation Flow creation failed
Recommended Action No action is required.
Error Message LIBBASE_SVC-5-IT_NEXUS_FAILURE: [chars]. [chars] bind failure. Reason: [chars]: [hex]
Explanation IT Nexus bind failed
Recommended Action No action is required.
Error Message LIBBASE_SVC-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface [chars] exceeded the optimum flow limit
Explanation Iterface Flow Limit
Recommended Action No action is required.
This section contains the LIBIFMGR messages.
Error Message LIBIFMGR-5-ALL_COUNTERS_CLEARED: All interface counters cleared by user
Explanation All interface counters cleared by user.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message LIBIFMGR-5-INTF_COUNTERS_CLEARED: Interface [chars]counters cleared by user
Explanation Interface counters cleared by user.
Recommended Action LOG_STD_SH_TECH_ACTION
This section contains the LICMGR messages.
Error Message LICMGR-0-LOG_LIC_GRACE_EXPIRED: Grace period expired for feature [chars].
Explanation Unlicensed feature [chars] has exceeded it's grace time period. Applications using will be shut down immediately.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-1-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for feature [chars].
Explanation The named feature has exceeded it's evaluation time period. Applications using the license will be shut down after a grace period.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-1-LOG_LIC_LICENSE_EXPIRY_WARNING_ALERT: Evaluation license for feature [chars] will expire in [dec] days.
Explanation Feature [chars] has very limited time for expiry. Feature will expire in [dec] days and will be shut down.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-1-LOG_LIC_NO_LIC_ALERT: No license(s) present for feature [chars]. Application(s) running in grace-period and will be shut down in [dec] days.
Explanation Feature [chars] has not been licensed. The feature will work for a grace period of [dec] days after which application(s) using the feature will be shut down.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-2-LOG_LICAPP_EXPIRY_WARNING: Application [chars] evaluation license [chars] expiry in [dec] days.
Explanation Application [chars1] will exceed it's evaluation time period in [dec] days and will be shut down after a grace period unless a permanent license for feature [chars2] is installed.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-2-LOG_LICAPP_NO_LIC: Application [chars] running without [chars] license, shut down in [dec] days.
Explanation Application [chars1] has not been licensed. The application will work for a grace period of [dec] days after which it will be shut down unless a license file for feature [chars2] is installed.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-2-LOG_LIC_EXIT: License manager exiting: [chars]
Explanation License 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.
Error Message LICMGR-2-LOG_LIC_INVALID_SERVER_LINE: License file [chars] contains invalid "SERVER" line. Contact TAC
Explanation Invalid SERVER line in license 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.
Error Message LICMGR-2-LOG_LIC_NO_LIC: No license(s) present for feature [chars]. Application(s) shut down in [dec] days.
Explanation Feature [chars] has not been licensed. The feature will work for a grace period of [dec] days after which application(s) using the feature will be shut down.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-2-LOG_LIC_NO_OE_LICENSE: Missing license to run NXOS on open environment platform, will be shut down in [dec] days.
Explanation Open environment platform requires a license to run NXOS. Please get a license and instal it. Features will not be able to function properly, the box will shut down after few days unless licensed.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-2-LOG_LIC_NVRAM_DISABLED: Licensing NVRAM is not available. Grace period will be disabled: [chars]
Explanation The Supervisor NVRAM block may have a hardware problem and may need to be replaced
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.
Error Message LICMGR-2-LOG_LIC_VENDOR_DOWN: License file contains invalid "SERVER" line. Vendor daemon down
Explanation Vendor daemon is down
Recommended Action Licensing
Error Message LICMGR-3-LOG_LIC_FILE_MISSING: License file(s) missing for feature [chars].
Explanation One or more license files for feature [chars] are missing and must be reinstalled.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-3-LOG_LIC_INVALID_HOSTID: Invalid license hostid VDH=[chars] for feature [chars].
Explanation Feature [chars2] has a license with an invalid license hostid VDH=[chars1]. This can occur if a supervisor card with licensed features for one switch is installed on another switch.
Recommended Action No action is required.
Error Message LICMGR-3-LOG_LIC_MESSAGE_ERROR: could not handle message: [chars] of type [dec] from addr [dec]:[dec].
Explanation Could not handle a IPC message [chars] of type [dec1] sent by a component running on node [dec2] with sap [dec3].
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.
Error Message LICMGR-3-LOG_LIC_SERVER_DOWN: License Server Down [dec]
Explanation A connection to the license server was lost.
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.
Error Message LICMGR-3-LOG_LIC_SPROM_LIC: Feature [chars] issued [dec] licenses without a valid license file.
Explanation Feature [chars] has been licensed [dec] times without a valid license file. This means one or more license files are missing for feature [chars] and must be reinstalled.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-3-LOG_LIC_TOO_MANY_LIC: Only [dec] licenses are supported for [chars] feature, where as [dec] licenses are installed.
Explanation More licenses are installed than allowed.
Recommended Action 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.
Error Message LICMGR-4-LOG_LIC_LICENSE_EXPIRY_WARNING: Evaluation license for feature [chars] will expire in [dec] days.
Explanation Feature [chars] will exceed it's evaluation time period in [dec] days and will be shut down.
Recommended Action Please install the license file to continue using the feature.
Error Message LICMGR-6-LOG_CHECKPOINT_CREATED: auto checkpoint [chars] created during license expiry.
Explanation When a license expires, auto checkpoint is created to prevent configuration loss.
Recommended Action Rollback can be done to the created checkpoint when a new license is installed.
Error Message LICMGR-6-LOG_LIC_FEATURE_CLEARED: Cleared [dec] license(s) for feature [chars].
Explanation Uninstalled [dec] license(s) for feature [chars].
Recommended Action Use the 'show license usage' command to verify this license feature removal.
Error Message LICMGR-6-LOG_LIC_FEATURE_INSTALLED: Installed [dec] license(s) for feature [chars].
Explanation Installed [dec] license(s) for feature [chars].
Recommended Action Use the 'show license usage' command to verify this license feature installation.
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED_ALL: Cleared all licenses.
Explanation Cleared all license files.
Recommended Action No action is required.
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED: Cleared license file [chars].
Explanation Uninstalled the named license file.
Recommended Action Use the 'show license' command to verify this license removal.
Error Message LICMGR-6-LOG_LIC_LICENSE_INSTALLED: Installed license file [chars].
Explanation Installed the named license file.
Recommended Action Use the 'show license' command to verify this license installation.
This section contains the LIM messages.
Error Message LIM-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.
Error Message LIM-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 'no shutdown' on the interface or removing and re-inserting the fibre optic cable.
Error Message LIM-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
Error Message LIM-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
Error Message LIM-2-SYSLOG_LIM_CRITICAL: Critical failure: [chars]
Explanation There was a critical failure in the component.
Recommended Action Please collect system tech-support
Error Message LIM-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 PortChannel interface that it belongs to
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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
Error Message LIM-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported
Explanation The transceiver for the interface specified in the error 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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]
Explanation Interface is admin up
Recommended Action No action is required.
Error Message LIM-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.
Error Message LIM-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down)
Explanation Interface has been configured to be administratively down
Recommended Action Perform 'no shutdown'
Error Message LIM-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.
Error Message LIM-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 'no shutdown' on the PortChannel interface that it belongs to
Error Message LIM-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
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not present)
Explanation The FCOT has been removed
Recommended Action Insert an FCOT
Error Message LIM-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
Error Message LIM-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)
Explanation The module's hardware has failed
Recommended Action Collect more information about failed module using command 'show module internal all module'
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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'
Error Message LIM-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'
Error Message LIM-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
Error Message LIM-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
Error Message LIM-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)
Explanation Interface removed
Recommended Action No action is required.
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down)
Explanation Parent interface is down
Recommended Action No action is required.
Error Message LIM-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
Error Message LIM-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
Error Message LIM-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down (No operational members)
Explanation This is a PortChannel interface and all its members are operationally down
Recommended Action Enable at least one of the PortChannel's members
Error Message LIM-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 'no shutdown'
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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 PortChannel
Error Message LIM-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed)
Explanation This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel
Recommended Action Change the speed of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error Message LIM-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
Error Message LIM-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
Error Message LIM-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:traceroute ipaddr
Error Message LIM-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:traceroute ipaddr
Error Message LIM-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:traceroute ipaddr
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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.
Error Message LIM-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
Error Message LIM-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up
Explanation Interface [chars] is trunking, VLANs [chars] are up
Recommended Action No action is required.
Error Message LIM-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.
Error Message LIM-5-IF_UP: Interface [chars] is up [chars]
Explanation Interface is up in mode specified, if applicable
Recommended Action No action is required.
Error Message LIM-5-SPEED: Interface [chars], operational speed changed to [chars]
Explanation Operational speed has changed when link came up
Recommended Action No action is required.
Error Message LIM-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
Error Message LIM-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.
This section contains the LLDP messages.
Error Message LLDP-3-DETECT_MULTIPLE_PEERS: Multiple peers detected on [chars]
Explanation Multiple peers detected on an interface
Recommended Action No action is required.
Error Message LLDP-3-INVALID_DCBXP_RECEIVED: Received an invalid DCBXP on [chars]
Explanation Received an invalid DCBXP on an interface
Recommended Action No action is required.
Error Message LLDP-3-INVALID_LLDP_RECEIVED: Received an invalid LLDP on [chars]
Explanation Received an invalid LLDP on an interface
Recommended Action No action is required.
Error Message LLDP-3-LLDP_INTERNAL_ERROR: LLDP internal error: [chars]
Explanation Internal error is encountered
Recommended Action No action is required.
Error Message LLDP-5-LLDP_DISABLED: LLDP Disabled
Explanation LLDP Service Disabled
Recommended Action No action is required.
Error Message LLDP-5-LLDP_ENABLED: LLDP Enabled
Explanation LLDP Service Enabled
Recommended Action No action is required.
Error Message LLDP-5-SERVER_ADDED: Server with Chassis ID [chars] Port ID [chars] management address [chars] discovered on local port [chars] in vlan [dec] with enabled capability [chars]
Explanation A new peer is discovered
Recommended Action No action is required.
Error Message LLDP-5-SERVER_REMOVED: Server with Chassis ID [chars] Port ID [chars] on local port [chars] has been removed
Explanation A peer is removed
Recommended Action No action is required.
Error Message LLDP-6-DETECT_REMOTE_CHANGE: Remote change detected on [chars]
Explanation Remote change detected on an interface
Recommended Action No action is required.
Error Message LLDP-6-DETECT_REMOTE_DCBXP_CHANGE: Remote DCBXP change detected on [chars]
Explanation Remote DCBXP change detected on an interface
Recommended Action No action is required.
This section contains the M2FIB messages.
Error Message M2FIB-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation M2FIB failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message M2FIB-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation M2FIB failed to initialize timer library. This is a fatal error.
Recommended Action No action is required.
Error Message M2FIB-SLOT#-2-M2FIB_MAC_TBL_PRGMING: Failed to program the mac table on FE [dec] for group: FTAG [dec], ([dec] (BD [dec]), *, [chars]). Error: [chars]. To avoid multicast traffic loss, disable OMF using the CLI: "no ip igmp snooping optimise-multicast-flood"
Explanation Failed to program the mac table. This is a critical failure please check m2fib errored transactions
Recommended Action No action is required.
Error Message M2FIB-SLOT#-2-M2FIB_MEM_ALLOC: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No action is required.
Error Message M2FIB-SLOT#-2-VLAN_NOT_FOUND: M2fib recvd invalid vlan!
Explanation M2FIB failed to process the route update as the vlan recvd was invalid
Recommended Action No action is required.
Error Message M2FIB-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation M2FIB has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message M2FIB-SLOT#-6-VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in M2FIB was successful.
Recommended Action No action is required.
Error Message M2FIB-SLOT#-6-VDC_REMOVED: VDC [dec] Removed
Explanation M2FIB has successfully removed VDC [dec] from its databases.
Recommended Action No action is required.
Error Message M2FIB-SLOT#-6-VDC_VLAN_CREATED: VLAN [dec] created in VDC [dec]
Explanation M2FIB has added VLAN [dec] in VDC [dec].
Recommended Action No action is required.
Error Message M2FIB-SLOT#-6-VDC_VLAN_REMOVED: VLAN [dec] removed from VDC [dec]
Explanation M2FIB has successfully removed VLAN [dec] from VDC [dec].
Recommended Action No action is required.
This section contains the M2RIB messages.
Error Message M2RIB-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation M2RIB failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message M2RIB-2-FLOOD_PROG_ERR1: Prev:[chars], Collect console logs and output of show tech-support m2rib
Explanation M2RIB has hit flood prog error. Collect output of show tech-support m2rib for further analysis
Recommended Action No action is required.
Error Message M2RIB-2-FLOOD_PROG_ERR2: Curr:[chars], Collect console logs and output of show tech-support m2rib
Explanation M2RIB has hit flood prog error. Collect output of show tech-support m2rib for further analysis
Recommended Action No action is required.
Error Message M2RIB-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode = [dec], Error code = [hex]
Explanation M2RIB encountered an error in processing an MTS message. The error and message are specified in the error message
Recommended Action No action is required.
Error Message M2RIB-2-M2RIB_INIT: M2RIB initialization of [chars] [chars]
Explanation M2RIB 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.
Error Message M2RIB-2-MFDM_API_ERROR: ERROR PROG FLOOD ROUTES: Status:[chars] Msg_Ref_State:[hex] Prev_Count:[dec] Curr_Count:[dec] Prev_Msg:[hex] Curr_Msg:[hex], Collect output of show tech-support m2rib
Explanation MFDM returned Failure for flood programming. Collect output of show tech-support m2rib for further analysis
Recommended Action No action is required.
Error Message M2RIB-2-MFDM_TIMEOUT_ERR: M2RIB timed out waiting for MFDM: Transaction: %p, Transaction entry: [chars]
Explanation Transaction timer for the message sent from M2RIB to MFDM has expired. Ack not received from MFDM.
Recommended Action No action is required.
Error Message M2RIB-6-INITIALIZED: Internal state created [chars]
Explanation M2RIB has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message M2RIB-6-SERVICE_UP: Initialized [chars]
Explanation M2RIB line 2.
Recommended Action No action is required.
This section contains the MCAST messages.
Error Message MCAST-2-SHUTDOWN: Process shutting down: [chars]
Explanation Mcast is shutting down
Recommended Action The action depends on the situation. The multicast process can shut down gracefully because of a system restart (in which case no action needs to take place) or because of a failure. The message associated with the syslog should be self explanatory to understand the reason for the shutdown. If the process is able to restart properly, there is no immediate harm for the system stability and the suggested action is to report the syslog event together with an explanation of the operations most recently performed on the system.
Error Message MCAST-4-ERROR: [chars]
Explanation Mcast encountered a generic error
Recommended Action No action is required.
Error Message MCAST-5-BAD_MSG: Received bad message: [chars]
Explanation Mcast has received a malformed/unrecognized message
Recommended Action No action is required.
Error Message MCAST-5-START: Process has been started
Explanation Mcast has been started
Recommended Action No action is required.
This section contains the MCECTEST messages.
Error Message MCECTEST-3-ASSERTION_FAILED: [chars]
Explanation MCECTEST has hit an assert condition at file [chars]
Recommended Action No action is required.
Error Message MCECTEST-3-INIT_FAIL: [chars]
Explanation MCECTEST Initialization failed. due to [chars]
Recommended Action No action is required.
Error Message MCECTEST-3-INTERNAL_ERR: [chars]
Explanation MCECTEST encountered an internal error due to [chars]
Recommended Action No action is required.
Error Message MCECTEST-3-MTS_ERR: [chars]
Explanation MCECTEST encountered an MTS error due to [chars]
Recommended Action No action is required.
Error Message MCECTEST-5-MCECTEST_DISABLED: MCECTEST Disabled
Explanation MCECTEST Service Disabled
Recommended Action No action is required.
Error Message MCECTEST-5-MCECTEST_ENABLED: MCECTEST Enabled
Explanation MCECTEST Service enabled
Recommended Action No action is required.
Error Message MCECTEST-6-INTERNAL_INFO: [chars]
Explanation MCECTEST got an internal info [chars]
Recommended Action No action is required.
This section contains the MCM messages.
Error Message MCM-2-MCM_CRITICAL_ERROR: Internal Critical Error
Explanation Some critical error
Recommended Action No action is required.
Error Message MCM-2-MCM_REPLICATION_DISABLED: Proxy layer-3 modules are not available for replication. Proxy layer-3 multicast replication is disabled.
Explanation Replication is disabled
Recommended Action No action is required.
Error Message MCM-2-MCM_REQ_RESP_ERROR: Error ([hex]: [chars]) while communicating with component :[chars], opcode: [chars] (for: [chars])
Explanation Error in request-response handshake
Recommended Action No action is required.
Error Message MCM-2-MCM_ROUTING_DISABLED: Proxy layer-3 modules are not available for routing. Proxy layer-3 forwarding is disabled.
Explanation Routing is disabled
Recommended Action No action is required.
Error Message MCM-5-MCM_SDB_UPDATE_FAILED: sdb update failed with ret_val [dec]
Explanation SDB updated failed for MCM
Recommended Action No action is required.
Error Message MCM-6-MCM_REPLICATION_ENABLED: Proxy layer-3 modules are UP and available for replication. Proxy layer-3 multicast replication is enabled.
Explanation Replication is enabled
Recommended Action No action is required.
Error Message MCM-6-MCM_ROUTING_ENABLED: Proxy layer-3 modules are UP and available for routing. Proxy layer-3 forwarding is enabled.
Explanation Routing is enabled
Recommended Action No action is required.
This section contains the MFDM messages.
Error Message MFDM-2-DI_REUSE: LTL node exists with DI [hex] oiflist_index [hex] type [dec] and same DI returned for oiflist_index [hex] type [dec] Please collect show tech-support forwarding multicast and show tech-support pixm.
Explanation PIXM returned duplicate DI.
Recommended Action No action is required.
Error Message MFDM-2-DOWNLOAD_TIMEOUT: Download of L2/L3 route databases timed out : download_in_progress_slots [hex] for database [chars] [chars] [chars]
Explanation Download of L2/L3 route databases timed out. Download triggered by VMM insert request.
Recommended Action No action is required.
Error Message MFDM-2-INTERNAL_ERROR: MFDM-[chars] Internal error : show system internal mfdm errors for more information
Explanation MFDM PD hit a internal error. show system internal mfdm errors for futher analysis.
Recommended Action No action is required.
Error Message MFDM-2-MAX_OIFS_LIMIT_REACHED: A route or more in your system has more than [dec] oifs that is the max currently supported. This may lead to inconsistencies between MRIB and MFIB since the route will not be updated in HW. Plese reduce the scale
Explanation Received route with too many OIFs
Recommended Action No action is required.
Error Message MFDM-2-MFDM_NVE_DSG_VP_LIMIT_REACHED: All available NVE DSG VPs ([dec]) are used. Failed to allocate VP for group [chars], oif [chars]. Please reduce the VxLAN multicast group scale
Explanation There are too many OIFs for VXLAN DSG entries
Recommended Action No action is required.
Error Message MFDM-2-MFDM_UNSUPPORTED_BIDIR_GROUP_AS_DROP_RT: Incorrect bidir group range learnt/configured on the system([chars]/[dec]). 224/4 cannot be configured as bidir grp range. Please change your config accordingly for forwarding to work properly
Explanation Received drop route as bidir group range
Recommended Action No action is required.
Error Message MFDM-2-MFDM_UNSUPPORTED_BIDIR_GROUP_RANGE: Incorrect bidir group range learnt/configured on the system([chars]/[dec]). The shortest supported mask for bidir group ranges on this platform is /[dec]. Please change your config accordingly for forwarding to work properly
Explanation Received bidir group range with mask too short
Recommended Action No action is required.
Error Message MFDM-2-REF_OUTOFSYNC: In Decrement ltl_node ref_count: [dec] is less than count: [dec] passed in for DI: [hex], oiflist_index: [hex], type: [dec]. Possible PI/PD refcount out-of-sync. Please collect show tech-support forwarding multicast and show tech-support pixm.
Explanation MFDM PI/PD refcount out-of-sync
Recommended Action No action is required.
This section contains the MMODE messages.
Error Message MMODE-2-MODE_CHANGED: System changed to "[chars]" mode.
Explanation The system changed to [chars] mode.
Recommended Action No action is required.
Error Message MMODE-2-MODE_CHANGE_WARN: System will be moved to "[chars]" mode in [dec] minutes
Explanation The system will be automatically changed to normal mode.
Recommended Action No action is required.
Error Message MMODE-2-MODE_SNAPSHOT_ERROR: Creation of [chars] snapshot failed. Please check bootflash space.
Explanation Creation of [chars] snapshot failed, check to see if bootflash has enough space to create snapshot.
Recommended Action No action is required.
Error Message MMODE-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec] size [dec]
Explanation Mmode 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.
Error Message MMODE-3-ASSERTION_FAILED: Failed in file:[chars] line:[dec]
Explanation Mmode process assertion failed in File:[chars], at line:[dec]
Recommended Action No action is required.
Error Message MMODE-4-MISSING_COMMAND_NAME: The command "[chars]" does not have command name and may cause mmode to work incorrectly.
Explanation The command does not have command name defined in its command definition file.
Recommended Action If the command is to be configured with mmode, the developer must define its command name.
Error Message MMODE-4-MODE_SNAPSHOT_DONE: The after_maintenance snapshot is complete and available for comparison
Explanation The after_maintenance snapshot done after moving to normal mode is complete and available.
Recommended Action No action is required.
This section contains the MODULE messages.
Error Message MODULE-2-LCM_PRE_UPGRADE_GENERAL_FAIL: Pre upgrade message fails seq [dec]
Explanation Pre upgrade message failed.
Recommended Action No action is required.
Error Message MODULE-2-LCM_UPGRADE_DONE_GENERAL_FAIL: Upgrade done message fails SAP [chars]
Explanation Upgrade ready message failed.
Recommended Action No action is required.
Error Message MODULE-2-LCM_UPGRADE_OVER_FAIL: Upgrade over message returned [dec] [hex] for SAP [chars]
Explanation Upgrade done message failed.
Recommended Action No action is required.
Error Message MODULE-2-LCM_UPGRADE_READY_FAIL: Upgrade ready message returned [dec] [hex] for SAP [chars]
Explanation Upgrade ready message failed.
Recommended Action No action is required.
Error Message MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL: Upgrade ready message fails SAP [chars]
Explanation Upgrade ready message failed.
Recommended Action No action is required.
Error Message MODULE-2-LCM_UPG_DBG_LOG: Sending upgrade [chars] request to service [chars] for slot [dec].
Explanation LCM sent upgrade request for the sap mentioned.
Recommended Action No action is required.
Error Message MODULE-2-MOD_DIAG_FAIL: Module [dec] (Serial number: [chars]) reported failure [chars] due to [chars] in device [chars] (device error [hex])
Explanation The module in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec] (Serial number: [chars])
Explanation Module [decimal digit] failed to download a new image from the supervisor.
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_FAILURE: Re-initializing module [dec] (Serial number: [chars]) failed. Received lc_failed from sap [chars] failure reason [hex]
Explanation Module [decimal digit] reported a failure during the initialization phase and will be rebooted.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all module
Error Message MODULE-2-MOD_FAIL: Initialization of module [dec] (Serial number: [chars]) failed
Explanation Module [decimal digit] reported a failure during the initialization phase and will be powered down.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all module
Error Message MODULE-2-MOD_MAJORSWFAIL: Module [dec] (Serial number: [chars]) reported a critical failure in service [chars]
Explanation A critical failure in service [string] happened at module [decimal digit] is going to reset the module [decimal digit].
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_MINORSWFAIL: Module [dec] (Serial number: [chars]) reported a failure in service [chars]
Explanation A non-critical failure in service [string] happened at module [decimal digit] is not going to reset the module [decimal digit].
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_NOT_ALIVE: Module [dec] not responding... resetting (Serial number: [chars])
Explanation Module [decimal digit] is not replying to the hello message: module manager is then going to reset the module.
Recommended Action No action is required.
Error Message MODULE-2-MOD_REGFAILED: Registration failed for module [dec]
Explanation Module [decimal digit] sent the registration message notifying a failure.
Recommended Action Collect module internal information by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_SOMEPORTS_FAILED: Module [dec] (Serial number: [chars]) reported failure on ports [chars] ([chars]) due to [chars] in device [chars] (device error [hex])
Explanation Module [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-2-MOD_UNKNOWN: Module type [[dec]] in slot [dec] is not supported
Explanation The software card id of module [decimal digit] is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the commands 'show module internal all module [decimal digit]'
Error Message MODULE-2-XBAR_DIAG_FAIL: Xbar [dec] (Serial number: [chars]) reported failure [chars] due to [chars] in device [chars] (device error [hex])
Explanation The xbar in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.
Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'.
Error Message MODULE-2-XBAR_FAILURE: Re-initializing xbar [dec] (Serial number: [chars]) failed. Received lc_failed from sap [chars] failure reason [hex]
Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all xbar
Error Message MODULE-2-XBAR_FAIL: Initialization of xbar [dec] (Serial number: [chars]) failed
Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be powered down.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all xbar
Error Message MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (Serial number: [chars]) reported failure on ports [chars] ([chars]) due to [chars] in device [chars] (error [hex])
Explanation Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.
Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'.
Error Message MODULE-2-XBAR_UNKNOWN: Xbar type [[dec]] in slot [dec] is not supported
Explanation The software card id of xbar [decimal digit] is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the commands 'show module internal all xbar [decimal digit]'
Error Message MODULE-3-LCM_SEQ_ERROR: Error ([chars]) for slot:[dec] while communicating with component [chars] opcode:[chars] (for:[dec])
Explanation LCM encountered an error while executing a sequence for a module.
Recommended Action No action is required.
Error Message MODULE-3-LCM_SYSLOG_ERR: [chars]
Explanation LCM encountered an error while processing a message for module.
Recommended Action No action is required.
Error Message MODULE-3-MOD_SRG_NOT_COMPATIBLE: Module [dec] (Serial number: [chars]) firmware is not compatible with supervisor, downloading new image
Explanation The software version of module [decimal digit] is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-4-MOD_IMG_VER_MISMATCH: Module [dec] (Serial number: [chars]) image version mismatch with supervisor, mage version in the linecard is [chars] Image version in the sup is [chars] download image with same version as supervisor
Explanation The software version of module [decimal digit] should match the software version in supervisor.
Recommended Action Download image in module with the same version as supervisor
Error Message MODULE-4-MOD_WARNING: Module [dec] (Serial number: [chars]) reported warning [chars] due to [chars] in device [chars] (device error [hex])
Explanation Module [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.
Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.
Error Message MODULE-4-XBAR_WARNING: Xbar [dec] (Serial number: [chars]) reported warning [chars] due to [chars] in device [chars] (device error [hex])
Explanation Xbar [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.
Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'.
Error Message MODULE-5-ACTIVE_SUP_OK: Supervisor [dec] is active (Serial number: [chars])
Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.
Recommended Action No action is required.
Error Message MODULE-5-LCM_MODULE_UPGRADE_END: Upgrade of module [dec] ended
Explanation Upgrade of the module has ended.
Recommended Action No action is required.
Error Message MODULE-5-LCM_MODULE_UPGRADE_START: Upgrade of module [dec] started
Explanation Upgrade of the module has been started by installer
Recommended Action No action is required.
Error Message MODULE-5-MOD_OK: Module [dec] is online (Serial number: [chars])
Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.
Recommended Action No action is required.
Error Message MODULE-5-MOD_REINIT: Re-initializing module [dec] (Serial number: [chars])
Explanation Module [decimal digit] reported a failure during the initialization phase and will be rebooted.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all module
Error Message MODULE-5-MOD_RESTART: Module [dec] is restarting after image download
Explanation Module [decimal digit] completed image download and is restarting.
Recommended Action No action is required.
Error Message MODULE-5-MOD_STARTUP_CFG_MISMATCH: The startup configuration cannot be applied to a different module type for module [dec] (Serial number: [chars]). [chars] module is replacing [chars].
Explanation The startup configuration for module [decimal digit] contains information about a different type of module instead of containing information about the current one.
Recommended Action No action is required.
Error Message MODULE-5-STANDBY_SUP_OK: Supervisor [dec] is standby
Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.
Recommended Action No action is required.
Error Message MODULE-5-XBAR_OK: Xbar [dec] is online (Serial number: [chars])
Explanation Xbar [decimal digit] is ready to be configured and be able to switch traffic.
Recommended Action No action is required.
Error Message MODULE-5-XBAR_REINIT: Re-initializing xbar [dec] (Serial number: [chars])
Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.
Recommended Action Collect information about the module by issuing the commands 'show module_internal all xbar
Error Message MODULE-6-MOD_PURGE_CONFIG: Purging the configuration for module [dec]
Explanation Notification is being sent to remove the module configurations.
Recommended Action No action is required.
Error Message MODULE-6-MOD_REG_OK: Registration succeeded for module [dec]
Explanation Module [decimal digit] sent a successful registration message.
Recommended Action No action is required.
This section contains the MONITORC messages.
Error Message MONITORC-SLOT#-3-MONITORC_FAILED: MONITORC failure: [chars]
Explanation Span session programming failed with no H/W resource
Recommended Action No DDTS.
This section contains the MONITOR messages.
Error Message MONITOR-5-ETH_SPAN_INBAND_RES: Inband resource allocation error for VDC: [dec]
Explanation Inband resouce not allocated to VDC
Recommended Action No action is required.
Error Message MONITOR-5-ETH_SPAN_SESSION_CREATED: Session [dec] created
Explanation A new span session has been created.
Recommended Action No action is required.
Error Message MONITOR-5-ETH_SPAN_SESSION_DELETED: Session [dec] deleted
Explanation Session has been deleted.
Recommended Action No action is required.
Error Message MONITOR-5-ETH_SPAN_SESSION_DOWN: Session [dec] is down. Reason "[chars]"
Explanation Session is down, no further traffic will be spanned.
Recommended Action No action is required.
Error Message MONITOR-5-ETH_SPAN_SESSION_ERROR: Session [dec] is having error. Reason "[chars]"
Explanation The session is experiencing a problem.
Recommended Action Delete the session and try to reconfigure it
Error Message MONITOR-5-ETH_SPAN_SESSION_UP: Session [dec] is up.
Explanation Session is up now. You can monitor Spanned traffic at the destination ports
Recommended Action No action is required.
This section contains the MPLS_OAM messages.
Error Message MPLS_OAM-5-INITFAIL: MPLS OAM Daemon Initialization failed: [chars]
Explanation MPLS OAM Daemon Initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message MPLS_OAM-5-LSPV_DISABLED: LSPV Disabled
Explanation MPLS_LSPV Service Disabled
Recommended Action No action is required.
Error Message MPLS_OAM-5-LSPV_ENABLED: LSPV Enabled
Explanation MPLS_LSPV Service nabled
Recommended Action No action is required.
This section contains the MPLS_STATIC messages.
Error Message MPLS_STATIC-5-MPLS_STATIC_DISABLED: MPLS_STATIC Disabled
Explanation MPLS_STATIC Service Disabled
Recommended Action No action is required.
Error Message MPLS_STATIC-5-MPLS_STATIC_ENABLED: MPLS_STATIC Enabled
Explanation MPLS_STATIC Service enabled
Recommended Action No action is required.
This section contains the MRIB messages.
Error Message MRIB-4-NBM_TOKEN_ALLOCATION_FAILED: No tokens available for new group [chars]
Explanation No tokens available for new group [chars]
Recommended Action No action is required.
This section contains the MTM messages.
Error Message MTM-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation MTM failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message MTM-SLOT#-0-FE_TIMER_EXPIRED: FE timer expired for fe [dec]!
Explanation Driver has failed to respond to MTM request within MTM_FE_TO_TIMER_INTERVAL.This is a fatal error.
Recommended Action No action is required.
Error Message MTM-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation MTM failed to initialize timer library. This is a fatal error.
Recommended Action No action is required.
Error Message MTM-SLOT#-1-L2_USD_REQ_FAILED: Failed to send request to the L2 ASIC driver.
Explanation Failed to send request to L2 ASIC driver.
Recommended Action No action is required.
Error Message MTM-SLOT#-2-FE_MAC_TABLE_LINE_FULL: Failed to insert static mac as MAC table line is full for FE [dec]!
Explanation Static mac insert failed due to line full condition.
Recommended Action No action is required.
Error Message MTM-SLOT#-2-HWIDX_TO_IF_FAILED_SUMMARY: Failed to get interface for hardware index for [dec] entries
Explanation Failed to get interface for hardware Index for [dec] entries
Recommended Action No action is required.
Error Message MTM-SLOT#-2-IF_TO_HWIDX_FAILED_SUMMARY: Failed to get hardware index for interface Index for [dec] entries.
Explanation Failed to get hardware index for interface Index for [dec] entries.
Recommended Action No action is required.
Error Message MTM-SLOT#-2-MTM_BUFFERS_FULL: MTM buffers are full for unit [dec]. MAC tables might be inconsistent. Pls use l2 consistency-checker to verify.
Explanation MTM buffers are full. So some hardware notifications might not be synced to L2FM. Pls use l2 consistency-checker to verify.
Recommended Action No action is required.
Error Message MTM-SLOT#-2-MTM_MEM_ALLOC: Memory allocation failed. [chars]
Explanation Memory allocation failed. This is a critical failure
Recommended Action No action is required.
Error Message MTM-SLOT#-2-MULTICAST_SOURCE_MAC_LEARNT: Inserted dynamically learnt multicast source mac [chars] in vlan [dec]!. Please issue 'show hardware mac address table' to observe them and 'clear mac address-table dynamic multicast-entries' to delete the same
Explanation Multicast mac address: [hex] sent as source mac in a packet and was learnt in the Mac Table. Please execute: clear mac address-table dynamic multicast-entries
Recommended Action No action is required.
Error Message MTM-SLOT#-2-STATIC_MATCH: Failed to program static match registers for [chars].
Explanation Failed to program the required registers in L2 ASIC for [chars].
Recommended Action No action is required.
Error Message MTM-SLOT#-2-STP_BPDU_MATCH: Failed to program static match registers for BPDU matching.
Explanation Failed to program the required registers in L2 ASIC for BPDU matching. BPDUs will not be received by Spanning tree.
Recommended Action No action is required.
Error Message MTM-SLOT#-2-VLAN_NOT_FOUND: VLAN [dec] not found in MTM database!
Explanation MTM failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.
Recommended Action No action is required.
Error Message MTM-SLOT#-3-L2_TABLE_FULL: L2 Table FULL. MAC Insert might fail.
Explanation L2 Table is FULL. The mac might not be inserted into hardware.
Recommended Action No action is required.
Error Message MTM-SLOT#-3-MAC_INSERT_FAILURE: MAC Insert Failed for [chars] in vlan [dec].
Explanation MAC INSERT Failed the specified MAC/vlan.
Recommended Action No action is required.
Error Message MTM-SLOT#-3-MTM_L2_TABLE_FULL: L2 Table FULL. MAC Insert Failed for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in vlan [dec].
Explanation MAC INSERT Failed because L2 Table is FULL. Check SDK errors in MTM INFO.
Recommended Action No action is required.
Error Message MTM-SLOT#-3-MTM_STATION_TBL_FULL: Resource GWMAC tbl is full in Hardware. Unable to install GWMAC [chars] on vlan [dec]
Explanation Number of GWMACs configured is more than Hardware limit. Check MTM global info for HW limits.
Recommended Action No action is required.
Error Message MTM-SLOT#-4-MTM_NS_CACHE_FULL: Forwarding cache entries for EOQs is full, some flows will not use EOQ buffers.
Explanation Cache entries needed for EOQ operation have reached its system limits.
Recommended Action No action is required.
Error Message MTM-SLOT#-5-AGEGRP_ALLOC_FAILED: Age group allocation for age [dec] failed.
Explanation Age group allocation for age [dec] failed. The total number of allocated age group has reached system limits.
Recommended Action No action is required.
Error Message MTM-SLOT#-5-ALL0_LRN_DISABLE_FAIL: Failed to program static match register to disable learning all 0 MAC.
Explanation Failed to program the required registers in L2 ASIC to disable learning all 0 MAC.
Recommended Action No action is required.
Error Message MTM-SLOT#-5-FE_LEARN_DISABLE: Disabling learning on all L2 ports in unit [dec].
Explanation Disabling learning on all L2 ports of the unit.
Recommended Action No action is required.
Error Message MTM-SLOT#-5-FE_LEARN_ENABLE: Re-enabling learning on all L2 ports in unit [dec].
Explanation Re-enabling learning on all L2 ports of the unit.
Recommended Action No action is required.
Error Message MTM-SLOT#-5-L2_TABLE_TCAM_NEAR_FULL: L2 Overflow TCAM Table nearly FULL.
Explanation The L2 overflow TCAM table for the specified unit is 90\% FULL
Recommended Action No action is required.
Error Message MTM-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation MTM has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in MTM was successful.
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VDC_REMOVED: VDC [dec] Removed
Explanation MTM has successfully removed VDC [dec] from its databases.
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VDC_VLAN_CREATED: VLAN [dec] created in VDC [dec]
Explanation MTM has added VLAN [dec] in VDC [dec].
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VDC_VLAN_REMOVED: VLAN [dec] removed from VDC [dec]
Explanation MTM has successfully removed VLAN [dec] from VDC [dec].
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VMAC_ADD: Installing VMAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in vlan [dec].
Explanation Installing VMAC in the hardware because of FHRP protocol state change.
Recommended Action No action is required.
Error Message MTM-SLOT#-6-VMAC_DEL: Remvoing VMAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in vlan [dec].
Explanation Removing VMAC in the hardware because of FHRP protocol state change.
Recommended Action No action is required.
This section contains the NAT messages.
Error Message NAT-2-HW_PROG_FAILED: Hardware programming for NAT failed:[chars]([dec])
Explanation NAT software encountered an error while programming the hardware to do NAT translation
Recommended Action No action is required.
Error Message NAT-2-TEST_ERROR: [chars] :[hex]
Explanation NAT testing error:[string] and error: [hex]
Recommended Action No action is required.
Error Message NAT-5-NAT_LOG_DISABLED: [chars] license not installed or expired
Explanation NAT needs license to run
Recommended Action No action is required.
Error Message NAT-5-NAT_LOG_ENABLED: [chars] license installed
Explanation NAT needs license to run
Recommended Action No action is required.
This section contains the NBM messages.
Error Message NBM-0-PMN_CLI_INITIALIZATION_FAILED: CLI library initialization failed!
Explanation Failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action No action is required.
Error Message NBM-1-PMN_LOG_ERR: NBM error: [chars]
Explanation NBM Error which needs attention
Recommended Action No action is required.
Error Message NBM-1-PMN_WRITE_TO_PSS_FAILED: Failed to write to PSS err [chars]
Explanation Failed to write to PSS err [chars]
Recommended Action No action is required.
Error Message NBM-2-PMN_FLOWS_ACTIVE: Flows are active. Tokens are not recalculated for iod [dec]
Explanation Tokens recalculation is not allowed when flows are active
Recommended Action No action is required.
This section contains the NEUTRON_USD messages.
Error Message NEUTRON_USD-0-I2C_DEV_INIT_FAIL: [chars]
Explanation I2C device initialaisation failure
Recommended Action No action is required.
Error Message NEUTRON_USD-0-RETIMER_INIT_FAIL_SFP: [chars]
Explanation Retimer initialisation failure for SFP
Recommended Action No action is required.
Error Message NEUTRON_USD-0-RETIMER_INIT_FAIL_TRIDENT: [chars]
Explanation Retimer initialisation failure for Trident
Recommended Action No action is required.
Error Message NEUTRON_USD-0-RETIMER_INIT_FAIL: [chars]
Explanation Retimer initialisation failure
Recommended Action No action is required.
Error Message NEUTRON_USD-0-USD_DRV_INIT_FAIL: [chars]
Explanation USD driver init failure
Recommended Action No action is required.
Error Message NEUTRON_USD-2-GET_SFP_INFO_FAIL: front-port [dec], Failed to get SFP installed info
Explanation Failed to get the SFP installed info
Recommended Action No action is required.
Error Message NEUTRON_USD-2-I2C_INIT_FAIL: Failed to initialize I2C device, inst=[hex], device=[hex] reg=[hex] value=[hex]
Explanation Initialisation of the I2C device failed
Recommended Action Please remove and insert the tranciever. If problem persists contact TAC
Error Message NEUTRON_USD-2-I2C_READ_FAIL: i2c read failed bus=[dec], inst=[dec], cmd=[dec], err=[dec]
Explanation I2C read access failure
Recommended Action No action is required.
Error Message NEUTRON_USD-2-I2C_WRITE_FAIL_AT_INIT: Failed to write I2C device,inst=[hex],device=[hex] reg=[hex] value=[hex]
Explanation Write to the I2C device failure
Recommended Action Please remove and insert the tranciever. If problem persists contact TAC
Error Message NEUTRON_USD-2-I2C_WRITE_FAIL: i2c write failed bus=[dec], inst=[dec], cmd=[dec], err=[dec]
Explanation I2C write access failure
Recommended Action No action is required.
Error Message NEUTRON_USD-2-UNKNOWN_INT: unknown interrupt:[dec]
Explanation Unknown interrupt
Recommended Action No action is required.
Error Message NEUTRON_USD-2-USD_ISR_FAIL: usd_init_isr_hdlr failed irq=[dec] error = [dec]
Explanation ISR initialisation failure
Recommended Action No action is required.
Error Message NEUTRON_USD-2-WRONG_MICROCODE: [chars]
Explanation Wrong Neutron microcode version
Recommended Action No action is required.
Error Message NEUTRON_USD-3-I2C_ACCESS_FAIL1: I2C access failed for port [dec]
Explanation I2C access failure
Recommended Action No action is required.
Error Message NEUTRON_USD-3-I2C_ACCESS_FAIL_XCVR_FCOT: I2C access failed port[dec] reg_addr [hex], inst=[hex]
Explanation I2C access failure
Recommended Action No action is required.
Error Message NEUTRON_USD-3-I2C_ACCESS_FAIL: failed to access I2C addr=[hex], inst=[hex], port=[dec], cmd=[dec]
Explanation I2C device access failure
Recommended Action No action is required.
Error Message NEUTRON_USD-3-NULL_PORT_PTR: [chars]
Explanation Null port pointer
Recommended Action No action is required.
Error Message NEUTRON_USD-3-RETIMER_CHANNEL_FAIL: slot_num [dec], front-port [dec]
Explanation Failed to turn on retimer for channel
Recommended Action No action is required.
Error Message NEUTRON_USD-3-RX_RETIMER_FAIL: [chars]
Explanation Setting RX retimer fail
Recommended Action No action is required.
Error Message NEUTRON_USD-3-SFP_INSERT: Port [dec] SFP is inserted
Explanation SFP inserted to port
Recommended Action No action is required.
Error Message NEUTRON_USD-4-I2C_INVALID_PARAM: Invalid bit type [dec] parameter
Explanation Invalid access bit type for I2C device
Recommended Action No action is required.
Error Message NEUTRON_USD-6-BYPASS_NEUTRON: [chars]
Explanation Bypassing Neutron
Recommended Action No action is required.
Error Message NEUTRON_USD-6-NEUTRON_CLN: [chars]
Explanation Set neutron chip for CLN
Recommended Action No action is required.
Error Message NEUTRON_USD-6-NEUTRON_QI: [chars]
Explanation Set neutron chip for QI
Recommended Action No action is required.
Error Message NEUTRON_USD-6-SFP_REMOVE: Port [dec] SFP is removed
Explanation SFP removed from port
Recommended Action No action is required.
Error Message NEUTRON_USD-6-SFP_STATE_CHNG1: port [dec] SFP state change from absent to present
Explanation SFP state change
Recommended Action No action is required.
Error Message NEUTRON_USD-6-SFP_STATE_CHNG2: port [dec] SFP state change from present to absent
Explanation SFP state change
Recommended Action No action is required.
This section contains the NFM messages.
Error Message NFM-2-COMMIT_FAIL: Commit failed: client [hex], [chars]
Explanation The DDB commit failed
Recommended Action No action is required.
Error Message NFM-2-DDB_FAILURE: DDB failure: [chars]
Explanation A DDB generated failure
Recommended Action No action is required.
Error Message NFM-2-EXITING: Exit reason: [chars]
Explanation The NFM service process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message NFM-2-INIT_FAIL: NFM Service Init failed: [chars] error [hex]
Explanation NFM Service initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message NFM-2-MALLOC_ERROR: Function [chars]: Size [dec] bytes
Explanation The NFM service could not allocate memory.
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.
Error Message NFM-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The NFM service encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Error Message NFM-2-VERIFY_FAIL: Verify failed - Client [hex], Reason: [chars], Interface: [chars]
Explanation The DDB Verify failed
Recommended Action No action is required.
Error Message NFM-3-DDB_ERROR: DDB error: [chars]
Explanation The DDB generated error
Recommended Action No action is required.
Error Message NFM-3-FEATURE_MANAGER_ERROR: [chars]: An error occurred processing a Feature Manager msg - error [chars]
Explanation An error occurred while processing a message from FEATURE Manager
Recommended Action No action is required.
Error Message NFM-3-HANDLE_IN_USE: [chars]: name: [chars]
Explanation The NFM service encountered a handle that was in use while reading a persistent storage database.
Recommended Action No action is required.
Error Message NFM-3-INVALID_HANDLE: [chars]: handle =[hex]
Explanation The NFM service encountered an invalid handle in a persistent storage database.
Recommended Action No action is required.
Error Message NFM-3-MONITOR_NOT_FOUND: Monitor with handle [hex] from source [hex]
Explanation An Export Msg from a Linecard contained an invalid Monitor handle
Recommended Action No action is required.
Error Message NFM-3-MTS_ERROR: NFM encountered the following MTS error: [chars]
Explanation NFM Service encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action No action is required.
Error Message NFM-3-NFM_CONFIG_ERROR: [chars]
Explanation L2 Netflow config is applied on Port-channel with F1 Line Cards only - error
Recommended Action No action is required.
Error Message NFM-3-NFM_DDB_ERROR: DDB error: [chars]
Explanation The DDB generated error
Recommended Action No action is required.
Error Message NFM-3-PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The NFM service has detected corruption in one of its persistent information database. The database would be recreated.
Recommended Action No action is required.
Error Message NFM-3-VLAN_PARSE_ERROR: [chars]: An error occurred processing a VLAN Mgr Parse msg [hex]
Explanation An error occurred while processing a message from VLAN Manager
Recommended Action No action is required.
Error Message NFM-4-DDB_WARNING: DDB warning: [chars]
Explanation The DDB generated warning
Recommended Action No action is required.
Error Message NFM-4-LICENSE_EXPIRED: The License has expired.
Explanation The NFM service requires a License to run and exits when the License expires.
Recommended Action No action is required.
Error Message NFM-4-NFM_DDB_WARNING: DDB warning: [chars]
Explanation The DDB generated warning
Recommended Action No action is required.
Error Message NFM-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the NFM service and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error Message NFM-5-FEATURE_DISABLED: Feature '[chars]' is Disabled.
Explanation NetFlow/Analytics Feature is Disabled.
Recommended Action No action is required.
Error Message NFM-5-FEATURE_ENABLED: Feature '[chars]' is Enabled.
Explanation NetFlow/Analytics Feature is Enabled.
Recommended Action No action is required.
Error Message NFM-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The NFM service on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Error Message NFM-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The NFM service became standby from active mode.
Recommended Action No action is required.
Error Message NFM-6-DDB_NOTIF: DDB notification: [chars]
Explanation The DDB generated notification
Recommended Action No action is required.
Error Message NFM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]
Explanation The NFM service was unable to send heartbeat to the system manger
Recommended Action No action is required.
Error Message NFM-6-NFM_DDB_NOTIF: DDB notification: [chars]
Explanation The DDB generated notification
Recommended Action No action is required.
Error Message NFM-6-SERVICE_UP: Initialized [chars]
Explanation The NFM service is up and ready The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message NFM-6-SRV_EXIT: NFM Service shutting down gracefully
Explanation NFM Service is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message NFM-6-SWITCH_OVER: Switching Over to other Sup.
Explanation The NFM service has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Error Message NFM-7-DEBUG: [chars]
Explanation Debug information is being sent to syslog
Recommended Action No action is required.
This section contains the NFP messages.
Error Message NFP-SLOT#-2-NF_ACL_ERR: [chars]([dec]): acl error. [chars]
Explanation Acl error
Recommended Action No DDTS.
Error Message NFP-SLOT#-2-NF_DDB_ERR: [chars]([dec]): ddb error.[chars] [hex]
Explanation Ddb 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.
Error Message NFP-SLOT#-2-NF_ERR: [chars]([dec]): nfp error. [chars]
Explanation Nfp error occured
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.
Error Message NFP-SLOT#-2-NF_FIB_ERR: [chars]([dec]): fib error. [chars]
Explanation Fib error
Recommended Action No DDTS.
Error Message NFP-SLOT#-2-NF_NDE_ERR: [chars]([dec]): nde error. [chars]
Explanation Nde error
Recommended Action No DDTS.
Error Message NFP-SLOT#-2-NF_NFM_ERR: [chars]([dec]): nfm error. [chars]
Explanation Nfm error
Recommended Action No DDTS.
Error Message NFP-SLOT#-2-NF_QOS_ERR: [chars]([dec]): qos error. [chars]
Explanation Qos error
Recommended Action No DDTS.
Error Message NFP-SLOT#-5-NF_INFO: [chars]
Explanation Info
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.
This section contains the NGOAM messages.
Error Message NGOAM-3-EVENT_ASYNC_LOOPBACK_CONN_LOST: Connectivity Lost for session [dec]
Explanation Last async request failed for the specified session
Recommended Action No action is required.
Error Message NGOAM-3-EVENT_DEST_UNREACH: Received Destination Unreachable notification message from switch id [dec] for switch id [dec].
Explanation Notification received that destination is unreachable
Recommended Action No action is required.
Error Message NGOAM-3-EVENT_LOOPBACK_MTU_ERROR: MTU exceeded msg received from [chars]
Explanation Received an ICMP error msg indicating MTU exceeded
Recommended Action No action is required.
Error Message NGOAM-3-EVENT_PT_TR_MTU_ERROR: MTU exceeded msg for TR/PT received from [chars]
Explanation Received an ICMP error msg indicating MTU exceeded
Recommended Action No action is required.
Error Message NGOAM-3-NVE_ACL_INSTALL_FAIL: ACL couldn't be installed for request [dec].
Explanation ACL install failed
Recommended Action No action is required.
Error Message NGOAM-4-ENTER_SESSION: [chars]
Explanation Notification of Looback response received for a session.
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_ASYNC_LOOPBACK_RESP: Received Loopback Response from [chars] for sender handle [dec]
Explanation Received a response for the async loopback request
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_INVALID_TLV: Received invalid TLV notification message from switch id [dec] for switch id [dec]
Explanation Notification received of packet with invalid TLV
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_PARAMETER_PROB: Received Parameter problem notification message from switch id [dec] for switch id [dec]
Explanation Notification received of packet with parameter problem
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_TEST_CRC_FAIL: Received test crc failure notification message from switch id [dec] for switch id [dec]
Explanation Notification received of packet with test crc failure
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_TTL_EXPIRY: Received Fabricpath TTL Expiry notification message from switch id [dec] for switch id [dec].
Explanation Notification received packet with TTL expiry
Recommended Action No action is required.
Error Message NGOAM-4-EVENT_VLAN_UNKNOWN: Received Fabricpath VLAN unknown notification message from switch id [dec] for switch id [dec].
Explanation Notification received packet with VLAN unknown
Recommended Action No action is required.
Error Message NGOAM-4-EXIT_SESSION: [chars]
Explanation Notification of connectivity loss for a Looback session.
Recommended Action No action is required.
Error Message NGOAM-4-MTRACE_ACL_INSTALL_FAIL: ACL couldn't be installed for request [dec].
Explanation ACL install failed
Recommended Action No action is required.
Error Message NGOAM-4-MTS_SEND_FAILED: MTS send to NGOAM failed
Explanation MTS send to NGOAM failed
Recommended Action No action is required.
Error Message NGOAM-4-PKT_TOO_LARGE: Packet being sent to NGOAM too large, size = [dec].
Explanation Packet being sent too large
Recommended Action No action is required.
Error Message NGOAM-4-SESSION_ERROR: [chars]
Explanation Notification of connectiviy issue for oam packet
Recommended Action No action is required.
Error Message NGOAM-4-U6RIB_INIT_FAIL: U6rib init failed - V6 functionality will be disabled
Explanation U6rib init failed
Recommended Action No action is required.
Error Message NGOAM-6-HMAC_AUTH_FAILED: Pathtrace requesting ifstats has HMAC check failed
Explanation Pathtrace HMAC check failed
Recommended Action No action is required.
This section contains the NPV messages.
Error Message NPV-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars] was lost in the middle of an active CFS session. Abort the CFS session and re-enter the configuration changes
Explanation Due to port flaps, link outages, switch restart etc. a CFS peer switch of NPV was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. It is recommended that the user abort this CFS session using ivr abort command and then re-enter the configuration changes.
Recommended Action No action is required.
Error Message NPV-2-NPV_DISABLE_FAILED: NPV could not disabled : [chars] [chars]
Explanation NPM could not disabled due to the reason specified. Please try again.
Recommended Action No action is required.
Error Message NPV-2-NPV_ENABLE_FAILED: NPV could not enabled : [chars] [chars]
Explanation NPM could not enabled due to the reason specified. Please try again.
Recommended Action No action is required.
Error Message NPV-2-NPV_EXITED: NPV process exited in file [chars] at Line [chars]:[chars]
Explanation NPM process encountered a critical error as specified, and so NPV process cannot continue.
Recommended Action No action is required.
Error Message NPV-3-ACL_UPDATE_FAILED: [chars]
Explanation ACL update request initiated by the NPV process has failed
Recommended Action No action is required.
Error Message NPV-3-CFS_INVALID_PAYLOAD_RECEIVED: NPV received invalid payload from CFS
Explanation NPV process received invalid payload from CFS.
Recommended Action No action is required.
Error Message NPV-3-CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the lock. The reason for the failure : [chars]
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.
Error Message NPV-3-COMMIT_FAILED: [chars]
Explanation An error occurred while committing configuration. The reason for the failure : [chars]
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.
Error Message NPV-3-COMMIT_PARTIALLY_FAILED: [chars]
Explanation An error occurred while committing configuration. Configuration could not be committed on some switches. The reason for the failure : [chars]. Configuration can be inconsistent in the fabric.
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.
Error Message NPV-3-COMMIT_REJECTED: [chars]
Explanation Commit request received from remote switch is rejected. The reason for the failure: [chars]
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.
Error Message NPV-3-FC2_SEND_FAILED: [chars]
Explanation NPV process could send an FC2 message.
Recommended Action No action is required.
Error Message NPV-3-F_RJT_SENT: [chars]
Explanation NPV process sent an F_RJT frame.
Recommended Action No action is required.
Error Message NPV-3-INTERNAL_ERROR: Internal error: [chars]
Explanation NPV process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.
Recommended Action No action is required.
Error Message NPV-3-LCP_PROGRAMMING_FAILED: [chars]
Explanation LCP programming request initiated by the NPV process has failed
Recommended Action No action is required.
Error Message NPV-3-LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the lock. The reason for the failure : [chars]
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.
Error Message NPV-3-LS_RJT_RCVD: [chars]
Explanation NPV process received an LS_RJT frame.
Recommended Action No action is required.
Error Message NPV-3-LS_RJT_SENT: [chars]
Explanation NPV process sent an LS_RJT frame.
Recommended Action No action is required.
Error Message NPV-3-MALLOC_FAILED: [chars]
Explanation NPV process could not allocate memory
Recommended Action No action is required.
Error Message NPV-3-MERGE_ACTIVATION_FAILED: [chars]
Explanation An error occurred while activating merged configuration. The reason for the failure : [chars]
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.
Error Message NPV-3-MERGE_FAILED: [chars]
Explanation An error occurred while merging configuration. The reason for the failure : [chars]
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.
Error Message NPV-3-MTS_SEND_FAILED: [chars]
Explanation NPV process could not send an MTS message.
Recommended Action No action is required.
Error Message NPV-3-NPIV_DISABLE_FAILED: [chars]
Explanation NPIV feature could not be disabled.
Recommended Action No action is required.
Error Message NPV-3-NPIV_NOT_SUPPORTED: [chars]
Explanation Nexus 9000 platform supports FCOE-NPV only. So, NPIV feature has no meaning in this platform
Recommended Action No action is required.
Error Message NPV-3-NPV_CFS_IPV4_ENABLE_FAILED: CFS IPv4 distribution enable failed because [chars]
Explanation NPV CFS distribution might not work. Try enabling it again on the command line. Make sure cfs distribution is enabled.
Recommended Action No action is required.
Error Message NPV-3-NPV_UPLINK_UNSTABLE: [chars]
Explanation Atleast one of the external interface is unstable. Loadbalancing across uplink requires stable links
Recommended Action No action is required.
Error Message NPV-3-PORT_BRINGUP_FAILED: [chars]
Explanation NPV process has failed to bringup the port
Recommended Action No action is required.
Error Message NPV-3-PORT_REINIT_FAILED: [chars]
Explanation Port reinit request initiated by the NPV process has failed
Recommended Action No action is required.
Error Message NPV-3-UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the lock. The reason for the failure : [chars]
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.
Error Message NPV-4-NPV_NPIV_NOT_ENABLED_ON_UPSTREAM_SWITCH: [chars]
Explanation This syslog is printed when the external interface fails to come up due to NPIV feature not enabled on the upstream switch.
Recommended Action Verify and enable NPIV feature in upstream switch.
Error Message NPV-4-NPV_PORT_VSAN_MISMATCH_ON_UPSTREAM_LINK: [chars]
Explanation This syslog is printed when the external interface fails to come up due to upstream port VSAN mis-match with the upstream switch.
Recommended Action Make sure port VSAN is same on both sides of this external link
Error Message NPV-5-ASSERTION_FAILED: Unexpected assertion failure in File [chars] at Line [dec]
Explanation An assertion failed in NPV code
Recommended Action No action is required.
Error Message NPV-5-FLEXATTACH_VPWWN_AUTO_ASSIGNED: A virtual port WWN [chars] has been automatically assigned to interface [chars]
Explanation The virtual port WWN will be used as port WWN for devices logging in on this interface.
Recommended Action No action is required.
Error Message NPV-5-FLEXATTACH_VPWWN_MANUALLY_ASSIGNED: A virtual port WWN [chars] has been manually assigned to interface [chars]
Explanation The virtual port WWN will be used as port WWN for devices logging in on this interface.
Recommended Action No action is required.
Error Message NPV-5-FLEXATTACH_VPWWN_UNASSIGNED: The virtual port WWN has been unassigned from interface [chars]
Explanation The physical port WWN will be used as port WWN for devices logging in on this interface.
Recommended Action No action is required.
Error Message NPV-5-FRAME_DISCARDED: [chars]
Explanation NPV process discarded an FC2 frame.
Recommended Action No action is required.
Error Message NPV-5-NPV_LOAD_BALANCE_REINIT: Server ports reinitialized : [chars]
Explanation Server ports are reinitialized to balance the loads on the external interfaces.
Recommended Action No action is required.
Error Message NPV-5-UNEXPECTED_EVENT: [chars]
Explanation NPV process has received an unexpected event in the current state.
Recommended Action No action is required.
Error Message NPV-6-ABTS_SENT: [chars]
Explanation NPV process sent an ABTS frame.
Recommended Action No action is required.
Error Message NPV-6-ELS_CMD_SENT_TO_CORE: [chars]
Explanation NPV process sent an ELS frame to the core switch.
Recommended Action No action is required.
Error Message NPV-6-ELS_CMD_SENT_TO_SRV: [chars]
Explanation NPV process sent an ELS frame to the server.
Recommended Action No action is required.
Error Message NPV-6-EXT_IF_SELECTED: [chars]
Explanation NPV process has selected an external interface to forward either all frames received on a server interface or frames received from a specific port WWN.
Recommended Action No action is required.
Error Message NPV-6-FABRIC_PROXY_LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame to the device as the corresponding external interface went down.
Recommended Action No action is required.
Error Message NPV-6-FDISC_RCVD: [chars]
Explanation NPV process received an FDISC frame.
Recommended Action No action is required.
Error Message NPV-6-FDISC_SENT: [chars]
Explanation NPV process sent an FDISC frame to the core switch.
Recommended Action No action is required.
Error Message NPV-6-FLOGI_RCVD: [chars]
Explanation NPV process received an FLOGI frame.
Recommended Action No action is required.
Error Message NPV-6-INTERNAL_FLOGI_SENT: [chars]
Explanation NPV process sent an internal FLOGI frame to the core switch on an external interface.
Recommended Action No action is required.
Error Message NPV-6-LOGO_RCVD: [chars]
Explanation NPV process received a LOGO frame.
Recommended Action No action is required.
Error Message NPV-6-LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame.
Recommended Action No action is required.
Error Message NPV-6-LS_ACC_RCVD: [chars]
Explanation NPV process received an LS_ACC frame.
Recommended Action No action is required.
Error Message NPV-6-LS_ACC_SENT: [chars]
Explanation NPV process sent an LS_ACC frame.
Recommended Action No action is required.
Error Message NPV-6-MTS_NOTIF_RCVD: [chars]
Explanation NPV process received an MTS notification.
Recommended Action No action is required.
Error Message NPV-6-MTS_NOTIF_SENT: [chars]
Explanation NPV process sent an MTS notification.
Recommended Action No action is required.
Error Message NPV-6-MTS_REQ_RCVD: [chars]
Explanation NPV process received an MTS request.
Recommended Action No action is required.
Error Message NPV-6-MTS_REQ_SENT: [chars]
Explanation NPV process sent an MTS request.
Recommended Action No action is required.
Error Message NPV-6-MTS_RESP_RCVD: [chars]
Explanation NPV process received an MTS response.
Recommended Action No action is required.
Error Message NPV-6-MTS_RESP_SENT: [chars]
Explanation NPV process sent an MTS response.
Recommended Action No action is required.
Error Message NPV-6-NPIV_DISABLED: [chars]
Explanation NPIV feature has been disabled.
Recommended Action No action is required.
Error Message NPV-6-NPIV_ENABLED: [chars]
Explanation NPIV feature has been enabled.
Recommended Action No action is required.
Error Message NPV-6-NPV_ENABLE_DISABLE_IN_PROGRESS: [chars]
Explanation NPV feature enable/disable is in progress. This syslog is printed at the beginning of various significant phases.
Recommended Action No action is required.
Error Message NPV-6-NPV_LOAD_BALANCE_TIMER_START: (Re)starting automatic load balancing timer for [dec] seconds
Explanation Timer started for upon external interface up or server interface down. When the timer goes off some of the server interfaces may be reinitialized to evenly distribute the server interfaces amongst the eligible external interfaces.
Recommended Action No action is required.
Error Message NPV-6-SERVER_PROXY_LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame to the core switch as the server interface went down.
Recommended Action No action is required.
Error Message NPV-7-CFS_REQ_RCVD: [chars]
Explanation CFS request is received. The WWN of the switch originated this request and the rr-token of the request are provided in the syslog message.
Recommended Action No action is required.
Error Message NPV-7-CFS_RESP_SENT: [chars]
Explanation CFS response is sent. The rr-token of the corresponding request and the status are provided in the syslog message
Recommended Action No action is required.
This section contains the NSUSD messages.
Error Message NSUSD-6-NSAUSD_DEBUG_MSG: [chars]
Explanation Debug log message
Recommended Action No action is required.
This section contains the NTP messages.
Error Message NTP-2-NTP_SYSLOG_CRIT_ERR: : [chars]
Explanation NTP syslog Critial Error : [chars].
Recommended Action No action is required.
Error Message NTP-2-NTP_SYSLOG_INIT_FAIL: : [chars] [chars]
Explanation NTP Initialization Failed: [chars] [chars].
Recommended Action No action is required.
Error Message NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC[dec] for [chars]
Explanation NTP did not receive response from the linecard for the request sent.
Recommended Action No action is required.
Error Message NTP-3-NTP_SYSLOG_ALLOC_FAIL: : [chars]
Explanation NTP syslog allocation failed : [chars].
Recommended Action No action is required.
Error Message NTP-3-NTP_SYSLOG_ERR_EXT: : [chars] [chars]
Explanation NTP syslog Error Exit : [chars] [dec].
Recommended Action No action is required.
Error Message NTP-3-NTP_SYSLOG_ERR: : [chars]
Explanation NTP syslog Error : [chars].
Recommended Action No action is required.
Error Message NTP-3-NTP_SYSLOG_MTS_ERR: : [chars]
Explanation NTP MTS Error : [chars].
Recommended Action No action is required.
Error Message NTP-6-NTP_SYSLOG_CREATED: : [chars]; Slot No: [dec]
Explanation NTP syslog created : [chars] [chars].
Recommended Action No action is required.
Error Message NTP-6-NTP_SYSLOG_EXIT: : [chars]
Explanation NTP syslog Exit : [chars].
Recommended Action No action is required.
Error Message NTP-6-NTP_SYSLOG_LOGGING: : [chars]
Explanation NTP logging : [chars].
Recommended Action No action is required.
Error Message NTP-6-NTP_SYSLOG_WARN: : [chars]
Explanation NTP syslog Warning : [chars].
Recommended Action No action is required.
This section contains the NVE messages.
Error Message NVE-5-BFD_CC_STATE_CHANGE: BFD CC [chars] for bfd-neighbor [chars]
Explanation A bfd cc state change has happened. This is most likely due to a configuration change.
Recommended Action No action is required.
Error Message NVE-5-VDC_MAC_G_STATUS: [chars] to get router-mac, current value [chars]
Explanation Information on events related to getting router-mac
Recommended Action No action is required.
This section contains the OBFL messages.
Error Message OBFL-3-ERROR: [chars]
Explanation Obfl_encountered an error
Recommended Action No action is required.
This section contains the ONEP messages.
Error Message ONEP-2-GET_BUFFER: Onepsync ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
Error Message ONEP-2-INIT: Onepsync ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Onepsync ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action LOG_STD_ACTION
Error Message ONEP-2-NE_PSS_32_ERR: ONEP [chars] configuration mismatch: Network Element([dec]) / PSS([dec])
Explanation The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.
Recommended Action LOG_STD_SH_CMD_ACTION( Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesn't take. The 'show running-config' command should be used to see if this error persists.)
Error Message ONEP-2-NE_PSS_STRING_ERR: ONEP [chars] configuration mismatch: Network Element([chars]) / PSS([chars])
Explanation The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.
Recommended Action LOG_STD_SH_CMD_ACTION( Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesn't take. The 'show running-config' command should be used to see if this error persists.)
Error Message ONEP-2-SEND_NEGO_FAILED: Onepsync ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
Error Message ONEP-2-SESSION_NEGO_FAIL_START: Failed to start Onepsync ISSU session negotiation. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session
Error Message ONEP-2-SESSION_REGISTRY: Onepsync ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries
Error Message ONEP-3-AUTHEN_ERR: [[chars]]: Authentication/authorization failed. [chars]
Explanation The session authentication has failed
Recommended Action LOG_STD_SH_CMD_ACTION( Check user's credentials are matched against the AAA/local users configured on the Netwk Element.)
Error Message ONEP-3-BUSY_ERR: [[chars]]: The requested resource is currently busy. [chars].
Explanation The usage of the resource has exceeded the configured threshold value
Recommended Action LOG_STD_SH_CMD_ACTION( Check the current resource usage and configured resource threshold. cpu threshold rising
Error Message ONEP-3-DISABLED_ERR: [[chars]]: [chars] is disabled.
Explanation The requested service set is in disabled state. All the service requests for that service set will be rejected.
Recommended Action LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. connectedapps service set
Error Message ONEP-3-DUPLICATE_ERR: [[chars]]: Requested entity [chars] already exists.
Explanation The connection request to the network element already exists
Recommended Action LOG_STD_SH_CMD_ACTION( Make sure the uniqueness of the application name. One session per application is allowed on a network element.)
Error Message ONEP-3-INVALID_SESSION: Onepsync ISSU client does not have a valid registered session.
Explanation The Onepsync ISSU client does not have a valid registered session.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries
Error Message ONEP-3-LISP_DISABLED_ERR: [[chars]]: [chars] is disabled.
Explanation The requested service set is in disabled state. All the service requests for that service set will be rejected.
Recommended Action LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. connectedapps service set lisp)
Error Message ONEP-3-MSG_NOT_OK: Onepsync ISSU client 'Message Type [dec]' is not compatible
Explanation The Onepsync ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group
Error Message ONEP-3-MSG_SIZE: Onepsync ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to calculate the MTU for the specified message. The Onepsync ISSU client is not able to send the message to the standby device.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group
Error Message ONEP-3-SESSION_UNREGISTRY: Onepsync ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Onepsync ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session
Error Message ONEP-3-VERSION_ERR: [[chars]]: ONE-P version incompatible between client and network element. [chars]
Explanation The ONE-P client service set version is incompatible with the one installed on the network element
Recommended Action LOG_STD_SH_CMD_ACTION( Make sure the version running on the client side is compatible with the one installed on the network element )
Error Message ONEP-4-CLEAR_TEXT_TRANSPORT_WARN: [[chars]]: Clear text transport being enabled. This is not recommended for production environment. [chars]
Explanation Clear text transport being enabled. This is not recommended for production environment.
Recommended Action LOG_STD_SH_CMD_ACTION( Please configure secure transport, such as TLS.)
Error Message ONEP-4-ONEP_DISABLED: ONEP feature is administratively disabled, terminated [[dec]] connected application(s)
Explanation Administrator has disabled ONEP feature while application sessions were active. All active sessions have been terminated. To enable ONEP again use \'feature onep\' command in configuration mode.
Recommended Action LOG_STD_SH_CMD_ACTION( No action is required if this was deliberate operation. To enable ONEP again use \'feature onep\' command in configuration mode.)
Error Message ONEP-6-CONNECT: [[chars]]: ONEP session [chars] has connected.
Explanation A new ONEP session has been established with network element.
Recommended Action LOG_STD_SH_CMD_ACTION( No action is required if this is an authorized session.)
Error Message ONEP-6-DISCONNECT: [[chars]]: ONEP session [chars]
Explanation ONEP session has been disconnected. A disconnect can happen when application has finished execution or there was a problem during execution including issue with network transport. If reconnect timer is configured, Network Element will wait for application to reconnect within configured time before cleaning up session resources.
Recommended Action LOG_STD_SH_CMD_ACTION( No action is required if it is a expected disconnected. Use show tech-support onep to collect logs from Network Element)
Error Message ONEP-6-HISTORY: [chars]
Explanation This syslog message is used to display onePK history messages when the 'history syslog' onep command is enabled.
Recommended Action LOG_STD_SH_CMD_ACTION( No action is required. Use 'no history syslog' at the onep configuration prompt to turn off this logging if desired.)
Error Message ONEP-6-RECONNECT: [[chars]]: ONEP session [chars] has reconnected.
Explanation ONEP session has been reconnected after being disconnected temporarly. This disconnect can happen due to intermittent network connectivity issues.
Recommended Action LOG_STD_SH_CMD_ACTION( No action is required if this is an authorized session.)
Error Message ONEP-6-SS_DISABLED: ONEP: [chars]
Explanation The service set has been set to a disabled state. All service requests for that service set will be rejected.
Recommended Action LOG_STD_SH_CMD_ACTION( If the disablement was intentional, no action is required. If not, then enable the service set: onep service set
Error Message ONEP-6-SS_ENABLED: ONEP: [chars]
Explanation The service set has been set to an enabled state. The features of the service set will be available for use.
Recommended Action LOG_STD_SH_CMD_ACTION( If the enablement was intentional, no action is required.)
This section contains the OTM messages.
Error Message OTM-2-OTM_EEM_FAIL: OTM failed to register with EEM
Explanation OTM process failed to register with eem, exiting now
Recommended Action No action is required.
Error Message OTM-3-OTM_ERROR: [chars] [chars]
Explanation [chars1][chars2]
Recommended Action No action is required.
Error Message OTM-5-OTM_OBJECT_STATUS: Status of tracking object [dec] changed to [chars]
Explanation Status of tracking object [dec] changed to [chars]
Recommended Action No action is required.
Error Message OTM-5-OTM_OBJ_ADD: : Tracking object [dec] configured, status of the object [chars]
Explanation Tracking Object [dec] configured, status of the object [chars]
Recommended Action No action is required.
Error Message OTM-6-OTM_EXITED: OTM process exited
Explanation OTM process is terminated
Recommended Action No action is required.
Error Message OTM-6-OTM_OBJ_REM: : Tracking object [dec] removed
Explanation Tracking Object [dec] removed
Recommended Action No action is required.
Error Message OTM-6-OTM_STARTED: OTM process started
Explanation OTM process is up and running
Recommended Action No action is required.
Error Message OTM-6-OTM_TRACK_START: Client started tracking object [dec]
Explanation Client has started tracking object [dec]
Recommended Action No action is required.
Error Message OTM-6-OTM_TRACK_STOP: Client stopped tracking object [dec]
Explanation Client has stopped tracking object [dec]
Recommended Action No action is required.
This section contains the PATCH-INSTALLER messages.
Error Message PATCH-INSTALLER-2-LOG_PATCH_INSTALLER_EXIT: Patch Installer exiting: [chars]
Explanation Patch Installer 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.
Error Message PATCH-INSTALLER-3-PATCH_INSTALLER_ID_FILE_ERR: Error opening patch installer id file
Explanation Could not open the file for storing patch installer request ids
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.
Error Message PATCH-INSTALLER-3-PATCH_INSTALLER_IMAGE_FILE_OPEN_ERR: Error opening image name file [chars] for patch installer
Explanation Could not open the file to get the name of the image
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.
Error Message PATCH-INSTALLER-3-PATCH_INSTALLER_IMAGE_FILE_READ_ERR: Error reading image name file [chars] for patch installer
Explanation Could not read the name of the image
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.
Error Message PATCH-INSTALLER-3-PATCH_INSTALLER_LOG_FILE_ERR: Error opening patch installer log file
Explanation Could not open the log file for logging \show install\ commands
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.
Error Message PATCH-INSTALLER-3-PATCH_INSTALLER_OP_FAILED: Package Install operation: [chars] , operation ID: [dec], failed with error: [dec] ([chars]) at: [chars]
Explanation 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.
Recommended Action Patch_installer
Error Message PATCH-INSTALLER-3-PATCH_SUPERCEDED: The following patches will get superceded: [chars]
Explanation List of superceded patches
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.
This section contains the PHY_USD messages.
Error Message PHY_USD-SLOT#-4-LOG_PHY_FW_UPGRADE: Extended firware upgrade started
Explanation Extended line card firmware upgrade started.
Recommended Action No action is required.
Error Message PHY_USD-SLOT#-4-LOG_PHY_ISSU_LINK_ST_CHNG: Port [dec]: link state during ISSU
Explanation Port Link status changed while perfoming an In Service System Upgrade. Disabling the port.
Recommended Action No action is required.
This section contains the PIM messages.
Error Message PIM-4-NBM_TOKEN_ALLOCATION_FAILED: No tokens available for new group [chars]
Explanation No tokens available for new group [chars]
Recommended Action No action is required.
This section contains the PIXM messages.
Error Message PIXM-2-PIXM_SYSLOG_MESSAGE_TYPE_CRIT: [chars]
Explanation PIXM has encountered a critical error
Recommended Action Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
Error Message PIXM-3-PIXM_SYSLOG_MESSAGE_TYPE_ERR: [chars]
Explanation PIXM has encountered a error
Recommended Action Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
Error Message PIXM-4-PIXM_SYSLOG_MESSAGE_TYPE_WARNING: [chars]
Explanation PIXM has encountered a warning-level error
Recommended Action Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
Error Message PIXM-7-PIXM_SYSLOG_MESSAGE_TYPE_DEBUG: [chars]
Explanation This is a debug output from PIXM
Recommended Action Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
This section contains the PLATFORM messages.
Error Message PLATFORM-0-CHASSIS_CLKSWITCH: Hardware clock switched to redundant clock-[dec]
Explanation Clock module on chassis deteted a failure and switched to redundant clock module.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch
Explanation Chassis clock source has failed and system will be reset. System will automatically start using redundant clock module.
Recommended Action Please refer to the platform document on clock modules.
Error Message PLATFORM-0-CHASSIS_CLKSW_MODULE_RESET: Modules reset due to clock switch
Explanation Chassis clock source has switched and all Vegas line cards will be reset. System will automatically continue using redundant clock module.
Recommended Action Please refer to the platform document on clock modules.
Error Message PLATFORM-0-FAIL_REMOVED: Fan module removed. Fan[dec] has been absent for [dec] seconds
Explanation Fan module is removed. This could lead to temperature alarms.
Recommended Action Replace the fan module ASAP.
Error Message PLATFORM-0-MOD_TEMPMAJALRM: [chars] reported Major temperature alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]
Explanation Module in slot [decimal digit] exceeded major temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-0-MOD_TEMPSHUTDOWN: [chars] powered down due to major temperature alarm for Sensor [dec].
Explanation Module in slot [decimal digit] shutdown due to temperature exceeding major threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-0-MOD_TEMPWARMALRM: [chars] reported Warm temperature alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] exceeded warm temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-0-PFM_EMERGENCY: [chars]
Explanation Platform Emergency
Recommended Action No action is required.
Error Message PLATFORM-0-SUP_SPROM_ERROR: Unable to read SPROM for Sup in slot [dec]
Explanation The supervisor in slot [decimal digit] was not able to read its SPROM.
Recommended Action No action is required.
Error Message PLATFORM-0-SUP_WRONGSLOTNUM: Supervisor powered up in WRONG SLOT:[dec] (Serial number [chars])
Explanation The supervisor is comming up in wrong slot [decimal digit].
Recommended Action No action is required.
Error Message PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED: Failed to load linecard module drivers
Explanation Failed to load drivers.
Recommended Action Image is possibly corrupt. Try to load a different image.
Error Message PLATFORM-0-SYS_NO_SHUTDOWN_FAN_DIR_MISMATCH: PS/Fan-Tray Fan dir mismatch is detected - System auto shutdown is disabled. Rectify mismatch to avoid system malfunction.
Explanation Mismatch in direction between fan and ps module. System will not shutdown
Recommended Action Please perform a 'show env fan' to collect more information.
Error Message PLATFORM-0-SYS_RESET: [chars] System shutdown in [dec] seconds
Explanation System shutdown in [decimal digit] seconds.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-0-SYS_SHUTDOWN_FAN_DIR_MISMATCH: PS/Fan-Tray Fan dir mismatch is detected - System will shutdown in [dec] minutes if mismatch is not rectified
Explanation System shutdown in [decimal digit] seconds due to mismatch in direction between fan and ps module.
Recommended Action Please perform a 'show env fan' to collect more information.
Error Message PLATFORM-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in [dec] seconds due to fan removal
Explanation System shutdown in [decimal digit] seconds due to removal of fan module.
Recommended Action Please perform a 'show env fan' to collect more information.
Error Message PLATFORM-0-SYS_SHUTDOWN_MDS9124_FAN_FAIL: System shutdown in [dec] seconds due to less than 4 fans operating.
Explanation System shutdown in [decimal digit] seconds due to less than 4 fans operating.
Recommended Action Please perform a 'show env fan' to collect more information.
Error Message PLATFORM-0-SYS_SHUTDOWN: System shutdown in [dec] seconds due to major temperature alarm
Explanation System shutdown in [decimal digit] seconds due to temperature exceeding major threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-0-SYS_SUP_DRIVER_LOAD_FAILED: Failed to load supervisor module drivers
Explanation Failed to load drivers.
Recommended Action Image is possibly corrupt. Try to load a different image
Error Message PLATFORM-0-XBAR_CARD_CLK_FAIL: Xbar card in slot:[dec] (Serial number [chars]) encountered clock failure
Explanation The xbar in slot [decimal digit] encountered clock failure.
Recommended Action No action is required.
Error Message PLATFORM-0-XBAR_CARD_INCOMPAT_CHASSIS: Xbar card in slot:[dec] (Part number [chars]) Incompatible with backplane chassis Part Num:[chars]
Explanation The xbar in slot [decimal digit] is incompatible with backplane chassis.
Recommended Action No action is required.
Error Message PLATFORM-0-XBAR_WRONGSLOTNUM: Xbar powered up in WRONG SLOT:[dec] (Serial number [chars])
Explanation The xbar in slot [decimal digit] powered up in wrong slot.
Recommended Action No action is required.
Error Message PLATFORM-1-FABRIC_SWITCH_FAN_FAIL: Less than 4 required fans operating.
Explanation Fan module has failed leaving less than 4 total fans operating. Fan needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-1-FAN_FAIL: Fan module Failed
Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-1-PFM_ALERT: [chars]
Explanation Platform Alert
Recommended Action No action is required.
Error Message PLATFORM-1-PS_SINGLE_INPUT: Both power inputs are connected for Power supplies, remove single-input configuration for optimal power usage
Explanation Current power supply redundancy mode may not be optimal
Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-1-XBAR_PWRDENY: Xbar [dec] can not be powered up due to insufficient power (Serial number [chars])
Explanation Available power in power supplies is not sufficient to power up the xbar
Recommended Action You can verify available power and current usage using command 'show env power'. Please refer to power supply document on how to increase power supply capacity.
Error Message PLATFORM-2-9134_FAN_FAIL: Fan module [dec] Failed
Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-2-9134_FAN_OK: Fan module [dec] ok
Explanation Fan module is ok
Recommended Action No action is required.
Error Message PLATFORM-2-ACTIVE_SUP_LESS_MEMORY: Active is Sup-A & Standby is Sup-B, replace Sup-A in slot [dec] with Sup-B for continued redundancy post switchover
Explanation Supervisor memory mismatch
Recommended Action No action is required.
Error Message PLATFORM-2-CASA_FAN_FAIL: Fan module [dec] Failed
Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-2-CASA_FAN_OK: Fan module [dec] ok
Explanation Fan module is ok
Recommended Action No action is required.
Error Message PLATFORM-2-CHASSIS_CLKMODFAULTY: Chassis clock module [dec] faulty
Explanation Clock module on chassis is faulty or has been removed.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module [dec] ok
Explanation Clock module on chassis is functioning properly.
Recommended Action No action is required.
Error Message PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is clock-[dec]
Explanation The current chassis clock source is [decimal digit].
Recommended Action No action is required.
Error Message PLATFORM-2-FANLET_FAN_FAIL: Failed Fanlets for Fan [dec] ([chars] fan) : [chars]
Explanation The specified fanlets have failed. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-2-FANMOD_FAN_FAIL: Fan module [dec] ([chars] fan) Failed/Removed
Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.
Recommended Action Please perform a 'show platform internal info' to collect more information.
Error Message PLATFORM-2-FANMOD_FAN_OK: Fan module [dec] ([chars] fan) ok
Explanation Fan module is ok
Recommended Action No action is required.
Error Message PLATFORM-2-FAN_OK: Fan module ok
Explanation Fan module is ok
Recommended Action No action is required.
Error Message PLATFORM-2-FAN_REMOVED: Fan module [dec] (Serial number [chars]) [chars] removed
Explanation Fan module is removed
Recommended Action No action is required.
Error Message PLATFORM-2-INSUFFICIENT_MAC: Ran out of Mac address to program management port on all the non-default VDCs
Explanation Could not program the mac address for the management port of all the VDCs
Recommended Action No action is required.
Error Message PLATFORM-2-MEMORY_ALERT_RECOVERED: Memory Status Alert : [chars]
Explanation Memory alert event received
Recommended Action None
Error Message PLATFORM-2-MEMORY_ALERT: Memory Status Alert : [chars]. Usage [chars]% of Available Memory
Explanation Memory alert event received
Recommended Action None
Error Message PLATFORM-2-MODULE_EJECTOR_POLICY_DISABLED: Ejector based shutdown disabled for Module [dec] [chars]. Please close all the ejectors to enable ejector based shutdown
Explanation Ejector based shutdown has been disabled
Recommended Action Close all the ejectors to enable ejector based shutdown
Error Message PLATFORM-2-MODULE_EJECTOR_POLICY_ENABLED: All Ejectors closed for module [dec]. Ejector based shutdown enabled
Explanation Ejector based shutdown has been enabled
Recommended Action None
Error Message PLATFORM-2-MOD_ALL_PARTIAL_LC_PWRDN_FABRIC_MODE: Partially connected line-card modules powered down due to configured fabric mode
Explanation Partially line-card modules in switch are powered down because of configured fabric mode
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' , 'show system fabric-mode' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. Atleast one partially connected fabric module has to be online for partially connected line-card modules to function
Error Message PLATFORM-2-MOD_ALL_PARTIAL_LC_PWRDN_NOFM: Partially connected line-card modules powered down due to no connectivity with existing fabric modules
Explanation Partially line-card modules in switch are powered down because of no connectivity to exisiting fabric modules
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. Atleast one partially connected fabric module has to be online for partially connected line-card modules to function
Error Message PLATFORM-2-MOD_ALL_PWRDN_NOFM: All line-card modules powered down due to non-availability of fabric modules
Explanation All line-card modules in switch are powered down because all fabric modules are offline
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. Atleast one fabric module has to be online for line-card modules to function
Error Message PLATFORM-2-MOD_ALL_PWRDN_NOSC: All fabric, line-card modules powered down due to non-availability of system controller modules
Explanation All fabric, line-card modules in switch are powered down because all system controller modules are offline
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. Atleast one system-controller module has to be online for fabric, line-card modules to function
Error Message PLATFORM-2-MOD_ALL_PWRDN_NOXBAR: All modules powered down due to non-availability of xbar modules
Explanation All modules in switch are powered down because all xbar modules are offline
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. Atleast one xbar module has to be for modules to function
Error Message PLATFORM-2-MOD_DETECT: Module [dec] detected (Serial number [chars]) Module-Type [chars] Model [chars]
Explanation A new module in slot [decimal digit] is detected.
Recommended Action No action is required.
Error Message PLATFORM-2-MOD_PRESENT: Detected the presence of Module [dec]
Explanation A new module in slot [decimal digit] is inserted.
Recommended Action No action is required.
Error Message PLATFORM-2-MOD_PWRDENY: Module [dec] can not be powered up due to insufficient power (Serial number [chars])
Explanation Available power in power supplies is not sufficient to power up the module
Recommended Action You can verify available power and current usage using command 'show env power'. Please refer to power supply document on how to increase power supply capacity.
Error Message PLATFORM-2-MOD_PWRDN: Module [dec] powered down (Serial number [chars])
Explanation The module in slot [decimal digit] is powered down.
Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors.
Error Message PLATFORM-2-MOD_PWRFAIL_EJECTORS_OPEN: All ejectors open, Module [dec] will not be powered up (Serial number [chars])
Explanation The module can not be powered up because all the ejectors are open
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-2-MOD_PWRFAIL: Module [dec] failed to power up (Serial number [chars])
Explanation The module in slot [decimal digit] failed to power up
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and to collect more information.
Error Message PLATFORM-2-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to IDPROM read error
Explanation The module can not be powered up due to IDPROM read error
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom module [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-2-MOD_PWRIDPROM_SW_CARD_ID_UNKNOWN: Module [dec] failed to power up. (Unknown card. Could not get software-card-id)
Explanation The module can not be powered up due to missing SWID in core-plugin for this CARDID
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom module [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-2-MOD_PWRUP_FM: Modules powered up due to fabric-module availability
Explanation Modules powered up because atleast one fabric module is online
Recommended Action No action needed
Error Message PLATFORM-2-MOD_PWRUP_PARTIAL_FM: Partially connected line-card modules powered up due to available connectivity with fabric-modules
Explanation Partially connected line-card modules powered up because atleast one fabric module is online
Recommended Action No action needed
Error Message PLATFORM-2-MOD_PWRUP_SC: Modules powered up due to system-controller module availability
Explanation Modules powered up because atleast one system-controller module is online
Recommended Action No action needed
Error Message PLATFORM-2-MOD_PWRUP_XBAR: Modules powered up due to xbar availability
Explanation Modules powered up because atleast one xbar module is online
Recommended Action No action needed
Error Message PLATFORM-2-MOD_PWRUP: Module [dec] powered up (Serial number [chars])
Explanation The module in slot [decimal digit] is powered up.
Recommended Action No action is required.
Error Message PLATFORM-2-MOD_REMOVE: Module [dec] removed (Serial number [chars])
Explanation The module in slot [decimal digit] has been removed.
Recommended Action No action is required.
Error Message PLATFORM-2-MOD_TEMPMAJOR2WARM: [chars] recovered from minor temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec] MajTheshold=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] warm temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPMAJOR_OK: [chars] recovered from major temperature alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]
Explanation Module in slot [decimal digit] major temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPMINALRM: [chars] reported minor temperature alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]
Explanation Module in slot [decimal digit] has exceeded minor temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPMINOR2WARM: [chars] recovered from minor temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec] MinTheshold=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] warm temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPOK: [chars] recovered from minor temperature alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]
Explanation Module in slot [decimal digit] minor temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPRECOVER: [chars] recovered from major temperature alarm. Minor temperature alarm pending. Sensor=[dec] Temperature=[dec] MajThreshold=[dec] MinThresh=[dec]
Explanation Module in slot [decimal digit] recovered from major temperature threshold. Minor threshold still exceeded.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-MOD_TEMPWARM_OK: [chars] recovered from warm temperature alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] warm temperature threshold.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-2-PFM_CRITICAL: [chars]
Explanation Platform Critical
Recommended Action No action is required.
Error Message PLATFORM-2-PFM_FATW_BUS_SWITCH_FAIL: Backplane two wire [chars] bus connection fault detected but failed to perform bus switchover(BUS_A to BUS_B)
Explanation Could not access some modules using BUS_A, but can access using BUS_B
Recommended Action Please perform a 'show platform internal err'
Error Message PLATFORM-2-PFM_FATW_BUS_SWITCH: Backplane two wire [chars] bus connection or device fault caused bus switchover(BUS_A to BUS_B)
Explanation Could not access some modules using BUS_A, but can access using BUS_B
Recommended Action Please perform a 'show platform internal err'
Error Message PLATFORM-2-PFM_IMG_CMPT_FAIL: Image version is not supported in this chassis.
Explanation This image version is not supported in this chassis.
Recommended Action Sup-platform
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_ABSENT: No bootflash found in Module [dec]
Explanation No bootflash found.
Recommended Action Try to put in a bootflash in the module and try again.
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: Bootflash access error in Module [dec]
Explanation Bad bootflash/corrupted filesystem.
Recommended Action Try to put in a known good bootflash in the module and try again.
Error Message PLATFORM-2-PFM_LC_MOD_POWERED_DOWN: Module [dec] Powered Down. Module is not supported in this chassis. (Chassis Incompatible card)
Explanation Module Powered Down, because Module is not supported in this chassis. (Chassis Incompatible card)
Recommended Action Please perform a 'show module' to see the Power Down reason.
Error Message PLATFORM-2-PFM_LC_NETBOOT_FAIL: Netboot for Module [dec] failed
Explanation Netboot failed.
Recommended Action Try to replace the BIOS in the module.
Error Message PLATFORM-2-PFM_LC_REGISTRATION_FAIL: Could not register with Module [dec]
Explanation Module registration failed.
Recommended Action Try to replace the module.
Error Message PLATFORM-2-PFM_LC_STATUS: Module [dec] powered up with [dec] status
Explanation Status for the module that failed registration.
Recommended Action Try to replace the module.
Error Message PLATFORM-2-PFM_LOW_MEMORY_CONDITION: Module [dec] is running low on memory. %ld percent used
Explanation Supervisor is running low on memory
Recommended Action Switchover
Error Message PLATFORM-2-PFM_MODULE_POWER_OFF_TRIGGER: Power-off [chars] due to [chars] policy trigger
Explanation Policy trigger initiated a module poweroff
Recommended Action None
Error Message PLATFORM-2-PFM_MODULE_POWER_OFF: Manual power-off of [chars] from Command Line Interface
Explanation User initiated a module power-off from the CLI
Recommended Action None
Error Message PLATFORM-2-PFM_MODULE_POWER_ON: Manual power-on of [chars] from Command Line Interface
Explanation User initiated a module power-on from the CLI
Recommended Action None
Error Message PLATFORM-2-PFM_MODULE_RESET: Manual restart of Module [dec] from Command Line Interface
Explanation User initiated a module reload from the CLI
Recommended Action None
Error Message PLATFORM-2-PFM_NETBOOT_DISABLE: Netboot for supervisor module in slot [dec] is disabled due to incompatible platform
Explanation Standby supervisor failed to powerup.
Recommended Action Try to replace the standby supervisor.
Error Message PLATFORM-2-PFM_PREP_DEEP_SLEEP: Supervisor module in slot [dec] preparing to enter deep sleep mode
Explanation Deep sleep mode initiated by the Connectivity Management Processor (CMP) for this supervisor
Recommended Action No action is required.
Error Message PLATFORM-2-PFM_PWR_MGMT_EPLD_VER_MISMATCH: Module [dec] Pwr Mgmt Epld (Version-[dec]) needs to be upgraded
Explanation Using a wrong version of Epld version can result in unexplainable behaviour
Recommended Action Upgrade Power Managment EPLD
Error Message PLATFORM-2-PFM_STDBY_POWERUP_FAIL: standby supervisor failed to powerup
Explanation Standby supervisor failed to powerup.
Recommended Action Try to replace the standby supervisor.
Error Message PLATFORM-2-PFM_SYSTEM_RESET_TRIGGER: System restart due to [chars] policy trigger
Explanation Policy/trigger initiated a system reload
Recommended Action None
Error Message PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line Interface
Explanation User initiated a system reload from the CLI
Recommended Action None
Error Message PLATFORM-2-PFM_SYSTEM_SHUTDOWN_TRIGGER: System shutdown due to [chars] policy trigger
Explanation Policy/trigger initiated a system shutdown
Recommended Action None
Error Message PLATFORM-2-PFM_SYS_RESET_IMG_CMPT_FAIL: *********ERROR:System reset due to unsupported image version********
Explanation System reset is triggered because of unsupported image version in this chassis.
Recommended Action Sup-platform
Error Message PLATFORM-2-PFM_XBAR_RESET: Manual restart of Xbar [dec] from Command Line Interface
Explanation User initiated a xbar reload from the CLI
Recommended Action None
Error Message PLATFORM-2-PLUGIN_ABSENT: Module in slot[dec] (sw_card_id=[dec]) has missing plugin
Explanation Plugin not loaded, The LC cannot be poweredup
Recommended Action Load the associated plugin
Error Message PLATFORM-2-PS_ABSENT: Power supply [dec] is absent/shutdown, ps-redundancy might be affected
Explanation Power Supply is absent.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_CAPACITY_CHANGE: Power supply PS[dec] changed its capacity. possibly due to On/Off or power cable removal/insertion (Serial number [chars])
Explanation Detected power supply capacity change.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_CAPACITY_DIFFER: Detected power supplies with differing capacity. It is recommended to have same capacity for both powersupplies otherwise it may cause service disruptions
Explanation Detected a power supply that has differing capacity than an the otherpower supply.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_DETECT: Power supply [dec] detected but shutdown (Serial number [chars])
Explanation Power Supply is detected but shutdown.
Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_FAIL: Power supply [dec] failed or shut down (Serial number [chars])
Explanation Power Supply has failed or has been shutdown
Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information. Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.
Error Message PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed
Explanation Fan module in the Power Supply has failed
Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_FANOK: Fan in Power supply [dec] ok
Explanation Fan module in the Power Supply is ok.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_MISMATCH: Detected power supply [chars]. This reduces the redundant power available to the system and can cause service disruptions (Serial number [chars])
Explanation Detected a new power supply that has reduced capacity than an existing power supply.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_OK: Power supply [dec] ok (Serial number [chars])
Explanation Power Supply is ok.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_PWR_INPUT_MISSING: Power supply [dec] present but all AC/DC inputs are not connected, power redundancy might be affected
Explanation Power Supply is present but not at full capacity.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_RED_MODE_CHG: Power supply operational redundancy mode changed to [chars]
Explanation Power supply redundancy mode changed notification
Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.
Error Message PLATFORM-2-PS_RED_MODE_RESTORED: Power redundancy operational mode changed to configured mode
Explanation Power Supply redundancy mode changes.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_REMOVE_LAST: Unexpected removal of last power supply [dec]. (Serial number [chars])
Explanation Unexpected removal the only power supply in the system.
Recommended Action Power supply unit may be faulty. Contact CISCO to replace the unit.
Error Message PLATFORM-2-PS_REMOVE: Power supply [dec] removed (Serial number [chars])
Explanation Power Supply is removed.
Recommended Action No action is required.
Error Message PLATFORM-2-PS_UNKNOWN: Detected an unknown power supply [dec] for CISCO Multilayer Switch (Serial number [chars])
Explanation Unable to determine power supply type. Default power supply types will be assumed.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.
Error Message PLATFORM-2-PS_UNSUPPORTED: Detected an unsupported power supply [dec] [chars] for CISCO Multilayer Switch (Serial number [chars])
Explanation This power supply is not supported for the CISCO Multilayer Switches.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.
Error Message PLATFORM-2-SUP_UNSUPPORTED: Unsupported card detected in supervisor slot [dec] powered down
Explanation The module in slot [decimal digit] has been powered down.
Recommended Action No action is required.
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_FAIL: Chassis IDPROM [dec] data re-initialization Un-successful. Data is invalid
Explanation Chassis IDPROM [decimal digit] re-initialization was unsuccessful. Data is invalid.
Recommended Action Please perform a 'show sprom module [decimal digit] 1' to read module IDPROM contents and collect more information.
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_PASS: Chassis IDPROM [dec] data re-initialized successfully
Explanation Chassis IDPROM [decimal digit] invalid data was succesfully re-initialized to valid.
Recommended Action Please perform a 'show sprom module [decimal digit] 1' to read module IDPROM contents and verify the information.
Error Message PLATFORM-2-SYS_IDPROMBAD: Chassis IDPROM [dec] data invalid
Explanation Chassis IDPROM [decimal digit] contains invalid data.
Recommended Action Please perform a 'show sprom module [decimal digit] 1' to read module IDPROM contents and collect more information.
Error Message PLATFORM-2-XBAR_DETECT: Xbar [dec] detected (Serial number [chars])
Explanation A new xbar in slot [decimal digit] is detected.
Recommended Action No action is required.
Error Message PLATFORM-2-XBAR_EJECTOR_POLICY_DISABLED: Ejector based shutdown disabled for Xbar [dec][chars]. Please close all the ejectors to enable ejector based shutdown
Explanation Ejector based shutdown has been disabled
Recommended Action Close all the ejectors to enable ejector based shutdown
Error Message PLATFORM-2-XBAR_EJECTOR_POLICY_ENABLED: All Ejectors closed for Xbar [dec]. Ejector based shutdown enabled
Explanation Ejector based shutdown has been enabled
Recommended Action None
Error Message PLATFORM-2-XBAR_PWRFAIL_EJECTORS_OPEN: All ejectors open, Xbar [dec] will not be powered up (Serial number [chars])
Explanation The xbar can not be powered up because all the ejectors are open
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-2-XBAR_REMOVE: Xbar [dec] removed (Serial number [chars])
Explanation The xbar in slot [decimal digit] has been removed.
Recommended Action No action is required.
Error Message PLATFORM-3-EJECTOR_STAT_CHANGED: Ejectors' status in slot [dec] has changed, [chars] Ejector is [chars], [chars] Ejector is [chars]
Explanation Ejector status has changed
Recommended Action None
Error Message PLATFORM-3-MOD_BRINGUP_MULTI_LIMIT: Giving up after multiple attempts were made to bring up the Module [dec], (Serial number [chars])
Explanation The module can not be powered up even after three attempts
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-3-MOD_PWRFAIL_MULTI: Module [dec] failed to power up multiple times (Serial number [chars])
Explanation The module can not be powered up even after three attempts
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-3-PFM_ERROR: [chars]
Explanation Platform Error
Recommended Action No action is required.
Error Message PLATFORM-3-SINGLE_EJECTOR_STAT_CHANGED: Ejectors' status in slot [dec] has changed, Ejector is [chars]
Explanation Ejector status has changed
Recommended Action None
Error Message PLATFORM-3-XBAR_BRINGUP_MULTI_LIMIT: Giving up after multiple attempts were made to bring up the Xbar [dec], (Serial number [chars])
Explanation The module can not be powered up even after three attempts
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contXBA ents to collect more information.
Error Message PLATFORM-3-XBAR_PWRFAIL_MULTI: Xbar [dec] failed to power up multiple times (Serial number [chars])
Explanation The xbar can not be powered up even after three attempts
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-3-XBAR_PWRFAIL: Xbar [dec] failed to power up (Serial number [chars])
Explanation The xbar in slot [decimal digit] failed to power up
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and to collect more information.
Error Message PLATFORM-3-XBAR_PWRIDPROMFAIL: Xbar [dec] failed to power up due to IDPROM read error
Explanation The xbar can not be powered up due to IDPROM read error
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-3-XBAR_PWRIDPROM_SW_CARD_ID_UNKNOWN: Xbar [dec] failed to power up. (Unknown card. Could not get software-card-id)
Explanation The xbar can not be powered up due to missing SWID in core-plugin for this CARDID
Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.
Error Message PLATFORM-4-MOD_TEMPACCESSFAIL: [chars] temperature sensor [dec] access failed
Explanation Module in slot [decimal digit] unable to access temperature sensor.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-4-MOD_TEMPFAIL: [chars] temperature sensor [dec] failed
Explanation Module in slot [decimal digit] contains a faulty temperature sensor.
Recommended Action Please perform a 'show env temperature' to collect more information.
Error Message PLATFORM-4-PFM_FAN_FLTR_STATUS: Fan Filter status: [chars]
Explanation Fan Filter status: Present/Absent
Recommended Action Please perform a 'show platform internal info.
Error Message PLATFORM-4-PFM_PS_RED_MODE_CHG: Power redundancy configured mode changed to [chars]
Explanation Power redundancy mode changed
Recommended Action Please perform a 'show platform internal info.
Error Message PLATFORM-4-PFM_WARNING: [chars]
Explanation Platform Warning
Recommended Action No action is required.
Error Message PLATFORM-5-FAN_DETECT: Fan module [dec] (Serial number [chars]) [chars] detected
Explanation Fan module is detected
Recommended Action No action is required.
Error Message PLATFORM-5-FAN_STATUS: Fan module [dec] (Serial number [chars]) [chars] current-status is [chars]
Explanation Fan module changed status
Recommended Action No action is required.
Error Message PLATFORM-5-FEX_FAN_DETECT: Fex [dec] Fan Module [dec] detected
Explanation Fex Fan module is detected
Recommended Action No action is required.
Error Message PLATFORM-5-FEX_FAN_REMOVE: Fex [dec] Fan Module [dec] removed
Explanation Fex Fan module is removed
Recommended Action No action is required.
Error Message PLATFORM-5-FEX_PS_FOUND: Fex [dec] Power Supply [dec] found (Serial number [chars])
Explanation Fex power supply is found
Recommended Action No action is required.
Error Message PLATFORM-5-FEX_PS_REMOVE: Fex [dec] Power Supply [dec] removed (Serial number [chars])
Explanation Fex power supply is removed
Recommended Action No action is required.
Error Message PLATFORM-5-MOD_STATUS: [chars] current-status is [chars]
Explanation Module in slot [decimal digit] changed status.
Recommended Action No action is required.
Error Message PLATFORM-5-PFM_NOTICE: [chars]
Explanation Platform Notice
Recommended Action No action is required.
Error Message PLATFORM-5-PS_FOUND: Power supply [dec] found (Serial number [chars])
Explanation Power Supply is detected.
Recommended Action No action is required.
Error Message PLATFORM-5-PS_STATUS: PowerSupply [dec] current-status is [chars] [chars]
Explanation Module in slot [decimal digit] changed status.
Recommended Action No action is required.
Error Message PLATFORM-5-XBAR_PWRDN: Xbar [dec] powered down (Serial number [chars])
Explanation The xbar in slot [decimal digit] is powered down.
Recommended Action Please perform a 'show module xbar', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors.
Error Message PLATFORM-5-XBAR_PWRUP: Xbar [dec] powered up (Serial number [chars])
Explanation The xbar in slot [decimal digit] is powered up.
Recommended Action No action is required.
Error Message PLATFORM-6-PFM_FAN_SPEED: [chars]
Explanation Fan Speed: For Zones
Recommended Action Please perform a 'show platform internal info.
Error Message PLATFORM-6-PFM_INFO: [chars]
Explanation Platform Info
Recommended Action No action is required.
Error Message PLATFORM-7-PFM_CLOCK_UPD_FAIL: Clock update failed due to context-switch delay of [dec] msec
Explanation System shutdown in [decimal digit] seconds.
Recommended Action Please perform a 'show env temperature' to collect more information.
This section contains the PLOG_SUP messages.
Error Message PLOG_SUP-4-PLOG_SUP_EXIT: Persistent Logger encountered an error [dec].
Explanation Persistent Logger encountered an error
Recommended Action No action is required.
This section contains the PLOG messages.
Error Message PLOG-4-PLOG_LC_EXIT: Persistent Logger encountered an error [dec]
Explanation Persistent Logger encountered an error
Recommended Action No action is required.
This section contains the PLSM messages.
Error Message PLSM-3-EDP_ERR: Interface [chars] in Error Disabled Policy(EDP) state Check : show interface status error policy [detail]
Explanation Error Disabled Policy State for a interface.
Recommended Action None
Error Message PLSM-6-SEQ_INFO: EDP State Cleared for interface [chars] vlans [chars]
Explanation EDP State cleared for a interface.
Recommended Action None
This section contains the PLTFM_CONFIG messages.
Error Message PLTFM_CONFIG-2-PC_ACL_TCAM_REGION_CARVING_NOT_SUPPORTED: Carving of TCAM region [chars] not supported on this platform. Please remove any unsupported region carving from startup config.
Explanation [chars] Carving of tcam region not supported on switch
Recommended Action No action is required.
Error Message PLTFM_CONFIG-2-PC_ACL_TCAM_REGION_NO_CARVING_NOT_SUPPORTED: Negation of TCAM region [chars] carving not allowed in startup config. Please remove any such carving configs from startup.
Explanation [chars] Negation of TCAM region carving not allowed in startup
Recommended Action No action is required.
Error Message PLTFM_CONFIG-2-PC_ACL_TCAM_REGION_VALIDATION_FAILED: Validation of TCAM region carving failed with reason: [chars]. Please ensure tcam carving config is valid in startup config
Explanation [chars] Validation of TCAM region carving failed
Recommended Action No action is required.
Error Message PLTFM_CONFIG-2-PC_FAILED: PLTFM_CONFIG failure: [chars]
Explanation PLTFM_CONFIG operation failed in pltfm_config
Recommended Action No DDTS.
Error Message PLTFM_CONFIG-3-PC_ACL_LOU_COMMIT_RESPONSE_FAIL_LOG: LOU threshold commit failed.
Explanation LOU threshold response to commit failed.
Recommended Action No action is required.
Error Message PLTFM_CONFIG-3-PC_ACL_LOU_COMMIT_TIMEOUT_LOG: LOU threshold commit timed out.
Explanation LOU threshold response to commit timed out.
Recommended Action No action is required.
Error Message PLTFM_CONFIG-3-PC_ACL_LOU_VERIFY_RESPONSE_FAIL_LOG: LOU threshold verification failed, aborting operation.
Explanation LOU threshold response to verify failed, so sending abort msg to all LC aclqos.
Recommended Action No action is required.
Error Message PLTFM_CONFIG-3-PC_ACL_LOU_VERIFY_TIMEOUT_LOG: LOU threshold verification timed out, aborting operation.
Explanation LOU threshold response to verify timed out, so sending abort msg to all LC aclqos.
Recommended Action No action is required.
Error Message PLTFM_CONFIG-3-PC_HW_QOS_VERIFY_RESPONSE_FAIL_LOG: hardware qos verification failed, aborting operation.
Explanation Hardware qos response to verify failed, so sending abort msg to all LC aclqos.
Recommended Action No action is required.
Error Message PLTFM_CONFIG-4-PC_ACL_TCAM_REGION_CARVE_BIG_SLICE: TCAM region of big slice [[dec]] allocated for tcam region [[chars]]. TCAM region of small slice is not available
Explanation [chars] Tcam region of big slice allocated
Recommended Action No action is required.
Error Message PLTFM_CONFIG-4-PC_ACL_TCAM_REGION_CARVING_WARNING: [chars].
Explanation [chars] TCAM region carving warning
Recommended Action No action is required.
Error Message PLTFM_CONFIG-4-PC_ACL_TCAM_TEMPLATE_INCOMP: TCAM template [[chars]] does not match the card type of [[dec]]. Using default tcam region settings for card [[dec]]
Explanation [chars] Tcam template incompatible with card
Recommended Action No action is required.
Error Message PLTFM_CONFIG-4-PC_MODULE_SE_RL_RESET: span-egress rate-limit: [chars]
Explanation Span-egress rate-limit value per module reset to system span-egress rate-limit
Recommended Action No DDTS.
Error Message PLTFM_CONFIG-4-XL_LICENSE_MIX_NOTIFY: Mixed use of non-XL with XL modules in the same VDC may limit common resources to non-XL capacity.
Explanation This is a reminder that mixing non-XL and XL modules in the same VDC may limit XL modules to the capacity of non-XL modules.
Recommended Action No action is required.
This section contains the PLUGIN messages.
Error Message PLUGIN-2-LOAD_REQUEST_FAILED_ON_STANDBY: Load request failed on standby. rc ([hex])
Explanation Load request failed on standby
Recommended Action No action is required.
Error Message PLUGIN-2-NOTIFY_MSG_FAILURE: Plugin notify message ([chars]) returned failure (rc [hex])
Explanation Plugin notify message returned failure.
Recommended Action No action is required.
Error Message PLUGIN-2-NO_MEMORY: Memory allocation failed (size [dec])
Explanation The service failed to allocate memory.
Recommended Action No action is required.
Error Message PLUGIN-2-PLUGIN_EXTRACT_FAILED_ON_STANDBY: Plugin extraction failed on standby. rc ([hex])
Explanation Plugin extraction failed on standby
Recommended Action No action is required.
Error Message PLUGIN-2-PLUGIN_LOAD_INTERNAL_ERROR: Plugin has internal error during load operation. Reason: [chars]
Explanation Plugin has internal error
Recommended Action No action is required.
Error Message PLUGIN-2-PLUGIN_UNLOAD_INTERNAL_ERROR: Plugin has internal error during unload operation. Reason: [chars]
Explanation Plugin has internal error
Recommended Action No action is required.
Error Message PLUGIN-2-SEND_NOTIFY_MSG_FAILED: Failed to send plugin notify message ([chars]). Reason: [chars]
Explanation Failed to send plugin notify message
Recommended Action No action is required.
Error Message PLUGIN-2-UNEXPECTED_LOAD_SYNC: Received unexpected plugin load sync. Current plugin request ([dec])
Explanation Standby received load sync and current standby does not have an outstanding load request
Recommended Action No action is required.
Error Message PLUGIN-2-UNEXPECTED_UNLOAD_SYNC: Received unexpected plugin unload sync. Current plugin request ([dec])
Explanation Standby received unload sync and current standby does not have an outstanding unload request
Recommended Action No action is required.
Error Message PLUGIN-2-UNLOAD_REQUEST_FAILED_ON_STANDBY: Unload request failed on standby. rc ([hex])
Explanation Unload request failed on standby
Recommended Action No action is required.
Error Message PLUGIN-2-UPDATE_SYS_INFO_FAILED: Failed to update system information ([chars])
Explanation Failed to update system information
Recommended Action No action is required.
Error Message PLUGIN-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]/[dec]: [chars]
Explanation Failed to send a message
Recommended Action No action is required.
This section contains the POAP messages.
Error Message POAP-2-POAP_DHCP_DISCOVER_RECVD_NAK: [chars] - Received DHCP NAK
Explanation Received DHCP NAK
Recommended Action No action is required.
Error Message POAP-2-POAP_DHCP_DISCOVER_START: [chars] - POAP DHCP Discover phase started
Explanation POAP DHCP Discover phase started
Recommended Action No action is required.
Error Message POAP-2-POAP_FAILURE_READ_MODINFO: [chars] - Failure to read module info
Explanation POAP failure to read module info
Recommended Action No action is required.
Error Message POAP-2-POAP_FAILURE: [chars] - [chars]
Explanation POAP failure
Recommended Action No action is required.
Error Message POAP-2-POAP_INFO: [chars] - [chars]
Explanation POAP Info
Recommended Action No action is required.
Error Message POAP-2-POAP_INITED: [chars] - POAP process initialized
Explanation POAP process initialized
Recommended Action No action is required.
Error Message POAP-2-POAP_RELOAD_DEVICE: [chars] - Reload device
Explanation POAP reload device.
Recommended Action No action is required.
Error Message POAP-2-POAP_SCRIPT_DOWNLOADED: [chars] - Successfully downloaded POAP script file
Explanation Successfully downloaded POAP script file
Recommended Action No action is required.
Error Message POAP-2-POAP_SCRIPT_EXEC_SUCCESS: [chars] - POAP script execution success
Explanation POAP script execution success
Recommended Action No action is required.
Error Message POAP-2-POAP_SCRIPT_STARTED_MD5_NOT_VALIDATED: [chars] - POAP script execution started(MD5 not validated)
Explanation POAP script execution started(MD5 not validated)
Recommended Action No action is required.
Error Message POAP-2-POAP_SCRIPT_STARTED_MD5_VALIDATED: [chars] - POAP script execution started(MD5 validated)
Explanation POAP script execution started(MD5 validated)
Recommended Action No action is required.
Error Message POAP-2-POAP_SCRIPT_STARTED_MD5_VALIDATION_FAIL: [chars] - POAP boot file validation failed
Explanation POAP boot file validation failed.
Recommended Action No action is required.
Error Message POAP-5-POAP_DISABLED: [chars] - POAP Disabled
Explanation POAP Service Disabled
Recommended Action No action is required.
Error Message POAP-5-POAP_ENABLED: [chars] - POAP Enabled
Explanation POAP Service nabled
Recommended Action No action is required.
This section contains the PONG messages.
Error Message PONG-5-PONG_DISABLED: Pong Manager disabled
Explanation Pong Service Enabled
Recommended Action No action is required.
Error Message PONG-5-PONG_ENABLED: Pong Manager enabled
Explanation Pong Service Enabled
Recommended Action No action is required.
Error Message PONG-5-PONG_INJECTED: Pong packet injected
Explanation Pong packet injected
Recommended Action No action is required.
This section contains the PORT-CHANNEL messages.
Error Message PORT-CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed [[chars]]
Explanation Module configuration failed
Recommended Action Module will be automatically reset
Error Message PORT-CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec])
Explanation No enough memory
Recommended Action No action is required.
Error Message PORT-CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for [chars] [[chars]]
Explanation Parameter mapping failed
Recommended Action Specified service is misbehaving; check its status
Error Message PORT-CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [chars]: [chars]
Explanation Failed to send a multicast message to all modules, usually because some module went down
Recommended Action Run show port-channel consistency to check consistency
Error Message PORT-CHANNEL-1-PC_BUNDLE_ID_NOT_CORRECT: [chars] : PC Bundle ([dec]) not equal to expected value ([dec]). Flapping the port-channel
Explanation Bundle of pc is not equal to port-channel id minus one, flap of the port-channel is performed
Recommended Action Flap of the port-channel was done since bundle was not equal to expected value. Check is PC traffic is restored fine.
Error Message PORT-CHANNEL-2-AUTO_CREATE_DISABLED: [chars] has been deprecated; [chars] [chars]
Explanation Auto create port-channel is deprecated and disabled
Recommended Action Convert the auto created channel to presistent by doing port-channel
Error Message PORT-CHANNEL-2-RESET_MODULE: reset module [dec] for not responding or returning error
Explanation A module is reset for not responding or returning error
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible
Explanation Compatibility check failed when adding ports to port-channel
Recommended Action Make sure the compatibility parameters are consistent while adding ports to port-channel, or use force option
Error Message PORT-CHANNEL-3-GENERAL_ERROR: [chars]
Explanation General error
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-LC_CFG_TIMEOUT_ENTRY_PORT_ERR_DISABLE: Failed to send LC config due to timeout, Port [chars] Err disabled
Explanation Failed to send a lc_config message
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-LC_CFG_UCAST_FAILED_PORT_ERR_DISABLE: Failed to send LC config unicast msg, Port [chars] Err disabled
Explanation Failed to send a lc_config unicast message
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-LC_CFG_UCAST_SEND_FAILURE: Failed to send LC config Unicast msg to slot [dec] node [hex] sap [dec]: [chars]. Resetting LineCard
Explanation Failed to send a lc_config unicast message
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Explanation Failed to send a message
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found
Explanation Cannot find port-channel in its database, which indicates an inconsistency with an external component
Recommended Action No action is required.
Error Message PORT-CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], state [chars]]
Explanation Some operation timed out
Recommended Action Run show port-channel consistency to check all module connectivity and consistency
Error Message PORT-CHANNEL-4-PORT_CFG_DELETED: [chars] removed from [chars]
Explanation Port is removed from a port-channel because different module was inserted or module config purged
Recommended Action You lost some ports from port-channel, check if you want to add ports in the new module to the same port-channel.
Error Message PORT-CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally individual
Explanation The port is operating as an individual link even though it is locally or remotely configured to be part of a port channel
Recommended Action Check the configuration of the port locally and remotely to ensure that it can operate as part of a port channel
Error Message PORT-CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of port-channel
Explanation Cannot find the port in port-channel database, which indicates an inconsistency with an external component
Recommended Action No action is required.
Error Message PORT-CHANNEL-4-RACE_WARN: [chars]
Explanation Warning of possible race condition
Recommended Action No action is required.
Error Message PORT-CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from [chars]
Explanation Received an unexpected response and discarded
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Explanation Auto create process on the port failed
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-CREATED: [chars] created
Explanation A port-channel is created
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-DELETED: [chars] deleted
Explanation A port-channel is deleted
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-FOP_CHANGED: [chars]: first operational port changed from [chars] to [chars]
Explanation The first operational port in a port-channel is changed
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come online because port channel interface
Explanation The port-channel number configured on the switch is larger than 128
Recommended Action Delete the set of port channel interface
Error Message PORT-CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Explanation Ports are added to a port-channel
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Explanation Port goes down in a port-channel
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Explanation Ports are removed from a port-channel
Recommended Action No action is required.
Error Message PORT-CHANNEL-5-PORT_UP: [chars]: [chars] is up
Explanation Port comes up in a port-channel
Recommended Action No action is required.
Error Message PORT-CHANNEL-6-RESYNC: resyncing [chars] with all modules
Explanation Resync modules with sup after an error or switchover
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-GSYNC_DONE: global synchronization is done
Explanation Port-channel manager finished global synchronization
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-GSYNC_REQ: requesting global synchronization
Explanation Port-channel manager requested a global synchronization from active sup
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-START_ACTIVE: started in active mode
Explanation Port-channel manager started in active mode
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-START_DEFAULT: started with default configuration
Explanation Port-channel manager started with default configuration
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-START_STANDBY: started in standby mode
Explanation Port-channel manager started in standby mode
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-START_STATEFUL: started statefully
Explanation Port-channel manager started with running configuration
Recommended Action No action is required.
Error Message PORT-CHANNEL-7-START_STATELESS: started statelessly
Explanation Port-channel manager started with startup configuration
Recommended Action No action is required.
This section contains the PORT-PROFILE messages.
Error Message PORT-PROFILE-2-IF_REFRESH_FAILED: Interface Database Refresh failed for [chars]
Explanation Interface Database Refresh failed
Recommended Action No action is required.
Error Message PORT-PROFILE-2-INTERFACE_CMD_FAILURE: Inherit of port-profile [chars] on [chars] has failed with reason: [chars]
Explanation Executing specific cmd on interface failed
Recommended Action No action is required.
Error Message PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface [chars] has been quarantined due to [chars]
Explanation Interface has been quarantined
Recommended Action No action is required.
Error Message PORT-PROFILE-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
Explanation PPM Process assertion failed in File:[chars], at line:[dec]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-CREATE_IF_FAILED: Running-config collection Failed for intf range [chars]
Explanation Running-config collection failed for :[chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-IF_APPLY_FAILED: Config Apply Failed
Explanation Config Apply Failed
Recommended Action No action is required.
Error Message PORT-PROFILE-3-INTERFACE_NO_SHUTDOWN_FAILED: Interface no shutdown failed for [chars] after profile re-inherit
Explanation Interface could not be unshut after profile re-inherit
Recommended Action No action is required.
Error Message PORT-PROFILE-3-INTERFACE_SHUTDOWN_FAILED: Interface shutdown failed for [chars] after failure to apply commands
Explanation Interface could not be shutdown after failure to apply commands
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PPM_ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec] size [dec]
Explanation SDM 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.
Error Message PORT-PROFILE-3-PROFILE_CREATE_FAILED: Port-profile [chars] creattion failed with error "[chars]"
Explanation Port-profile:[chars] creation failed with [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PROFILE_DEINHERIT_FAILED: Port-profile [chars] de-inherit failed with error "[chars]" on [chars]
Explanation Port-profile:[chars] de-inherit failed with [:chars] on [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PROFILE_DELETE_FAILED: Port-profile [chars] is deletion failed with error "[chars]"
Explanation Port-profile:[chars] deletion failed with [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PROFILE_DISABLE_FAILED: Port-profile [chars] disable failed with error "[chars]"
Explanation Port-profile:[chars] disable failed with [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PROFILE_ENABLE_FAILED: Port-profile [chars] enable failed with error "[chars]"
Explanation Port-profile:[chars] enable failed with [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-3-PROFILE_INHERIT_FAILED: Port-profile [chars] inherit failed with error "[chars]" on [chars]
Explanation Port-profile:[chars] inherit failed with [:chars] on [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-6-KEY_STRING_EMPTY: A command '[chars]' with no command name defined in the definition file can cause PPM to handle it incorrectly
Explanation Parsing null key as part of 'show running-config' is not correct
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_CREATED: Port-profile [chars] is created successfully
Explanation Port-profile:[chars] is created
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_DEINHERITED: Port-profile [chars] is de-inherited successfully on [chars]
Explanation Port-profile:[chars] is de-inherited on [:chars]
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_DELETED: Port-profile [chars] is deleted successfully
Explanation Port-profile:[chars] is deleted
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_DISABLED: Port-profile [chars] is disabled successfully
Explanation Port-profile:[chars] is disabled
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_ENABLED: Port-profile [chars] is enabled successfully
Explanation Port-profile:[chars] is enabled
Recommended Action No action is required.
Error Message PORT-PROFILE-6-PROFILE_INHERITED: Port-profile [chars] is inherited successfully on [chars]
Explanation Port-profile:[chars] is inherited on [:chars]
Recommended Action No action is required.
This section contains the PORT-RESOURCES messages.
Error Message PORT-RESOURCES-3-PRM_MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Explanation Failed to send a message
Recommended Action No action is required.
Error Message PORT-RESOURCES-5-INVALID_PORT_ACTIV_PKG_LICENSE_FILE_INSTALLED: Invalid on demand port activation license file is installed for module [dec] (number of port licenses = [dec])
Explanation Interfaces may not acquire port activation licenes during installation
Recommended Action Install a valid port activation license file
This section contains the PORT-SECURITY messages.
Error Message PORT-SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for [chars]
Explanation Memory allocation failed for size [dec] for [chars]
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.
Error Message PORT-SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to [chars]
Explanation Feature [chars] is unavailable and will be disabled now
Recommended Action Please install the correct license and reenable
Error Message PORT-SECURITY-2-INIT_FAILURE: : [chars]
Explanation FC Management initialisation has failed due to [chars].
Recommended Action No action is required.
Error Message PORT-SECURITY-3-BINDING_CONFLICT: [chars]
Explanation An already logged in device is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface
Recommended Action For port-security, the auto-learn feature can be used with activation to prevent this. This violating device or switch will be logged out
Error Message PORT-SECURITY-3-BINDING_VIOLATION: [chars]
Explanation A login happend that violates PSM binding configurations [chars] indicates the WWN of the login entity
Recommended Action Only entries in the activated database of PSM can login. Change the config and activate it again
Error Message PORT-SECURITY-3-CFS_NOTIF_ERR: [chars]
Explanation An error occurred during the processing of a CFS notification. [chars] indicates the actual cause for the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-DB_ERR: [chars]
Explanation An error occurred during an PSM database operation. [chars] indicates the reason for the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-EFMD_FC2_OPER_FAILED: [chars]
Explanation EFMD fc2 operation 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.
Error Message PORT-SECURITY-3-EFMD_INIT_FAILED: [chars]
Explanation EFMD init 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.
Error Message PORT-SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars]
Explanation Received a corrupted EFMD Request Packet
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.
Error Message PORT-SECURITY-3-FCID_CONV_ERR: : [chars]
Explanation FC Management pwwn to fcid conversion has failed due to [chars].
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.
Error Message PORT-SECURITY-3-INIT_FAIL: [chars]
Explanation An error happened during PSM Initialization. [chars] indicates the reason for 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.
Error Message PORT-SECURITY-3-LEARNT_BINDING_CONFLICT: [chars]
Explanation An already logged in device that is learnt during activation is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface
Recommended Action Copy the active-db to config-db and reactivate. Not doing so could result in unexpected login rejects later on that interface.
Error Message PORT-SECURITY-3-MAX_LIMIT_CROSSED: [chars]
Explanation MGMT_SEC: Max Limit for the config has exceeded.[chars]
Recommended Action No action is required.
Error Message PORT-SECURITY-3-MS_DB_ERR: : [chars]
Explanation FC Management db operation has failed due to [chars].
Recommended Action No action is required.
Error Message PORT-SECURITY-3-MS_DISABLE_ERR: [chars]
Explanation An error occurred during an FC Management disable operation. [chars] indicates the operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-MS_ENABLE_ERR: [chars]
Explanation An error occurred during an FC Management enable operation. [chars] indicates the operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-MTS_ERR: [chars]
Explanation An error occurred in processing of an MTS message. [chars] indicates the error that occurred
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.
Error Message PORT-SECURITY-3-PSS_ERR: [chars]
Explanation An error occurred during an PSM PSS operation. [chars] indicates the PSS operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version
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.
Error Message PORT-SECURITY-3-SDB_ERR: [chars]
Explanation An error occurred during an FC Management sdb operation. [chars] indicates the operation that caused the error
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message PORT-SECURITY-3-SDB_UPDATE_ERR: : [chars]
Explanation FC Management update has failed due to [chars].
Recommended Action No action is required.
Error Message PORT-SECURITY-4-ACTIVATION_FAIL: [chars]
Explanation Activation of bindings failed due to [chars]
Recommended Action Correct the error and reactivate it again
Error Message PORT-SECURITY-4-MAX_LIMIT_REACHED: [chars]
Explanation MGMT_SEC: Max Limit for the config has reached.[chars]
Recommended Action No action is required.
Error Message PORT-SECURITY-4-PSS_WARN: [chars]
Explanation A failure occurred during a PSM PSS operation. [chars] indicates the PSS operation that caused the error
Recommended Action No action is required.
Error Message PORT-SECURITY-6-INFO: [chars]
Explanation An event happend that affects PSM. [chars] indicates the event
Recommended Action No action is required.
Error Message PORT-SECURITY-6-MGMT_SEC_INFO: [chars]
Explanation An event happend that affects FC Management. [chars] indicates the event
Recommended Action No action is required.
This section contains the PORT messages.
Error Message PORT-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error disabled) [chars] [chars]
Explanation The interface encountered an error while configuring it. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Collect more information about failed interface using command 'show port internal all interface [char]'. In most cases, you can recover using following commands 'config terminal', 'interface [char]', 'shutdown', 'no shutdown' on the interface or removing and re-inserting the fibre optic cable
Error Message PORT-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
Error Message PORT-3-IF_SFP_ALARM: Interface [chars], [chars] [chars] [chars]
Explanation There was an alarm on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please do show interface transceiver details to obtain more information
Error Message PORT-3-IF_TRANSCEIVER_READ_ERROR: Transceiver read error for interface [chars] [chars] [chars]
Explanation Transceiver eeprom read failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Remove and insert the SFP back again. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition
Error Message PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported
Explanation Transceiver is not from an authorized vendor
Recommended Action This command will determine the transceiver being used: show interface transceiver. Please contact customer support for a list of authorized transceiver vendors
Error Message PORT-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
Error Message PORT-4-IF_SFP_CLK_RATE_ERROR: SFP clock rate error for interface [chars] [chars] [chars]
Explanation SFP clock rate mismatch/failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Remove the SFP and insert a new one with a different frequency type. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition
Error Message PORT-4-IF_SFP_WARNING: Interface [chars], [chars] [chars] [chars]
Explanation There was an warning on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please do show interface transceiver details to obtain more information
Error Message PORT-4-IF_TRUSTSEC_VIOLATION: Interface [chars] encountered port security violation [chars] [chars]
Explanation The port has detected port security violation. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check port security configs on interface
Error Message PORT-5-EC_DISABLED_AS_LICENSE_NOT_PRESENT: Extended credit feature has been disabled as Enterprise Package license could not be checked out
Explanation The Enterprise Package license is not available, so the extened credit feature has been disabled even though it was present in startup config
Recommended Action Install the Enterprise Package license and re-enable the extended credit feature
Error Message PORT-5-IF_BRINGUP_ALLOWED_FCOT_CHECKSUM_ERR: Interface [chars] is allowed to come up even with SFP checksum error [chars] [chars]
Explanation SFP checksum on this interface failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Try to replace the SFP on this interface
Error Message PORT-5-IF_BRINGUP_FAILED_ALL_ZERO_PEER_WWN_RCVD: Interface [chars], is not allowed to come up (received as all zeros wwn from peer [chars] [chars]
Explanation Check peer interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_BRINGUP_NOT_ALLOWED_PORT_CONFIG_FAILURE: Interface [chars] is not allowed to be operational due to port config failure for reason: [chars] ([hex]) [chars] [chars]
Explanation Check interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Try to change the configuration on the interface with the current available hardware capability
Error Message PORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down) [chars] [chars]
Explanation Interface has been configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Perform the following commands to bring up the interface: 'config terminal', 'interface [char]', 'no shutdown'
Error Message PORT-5-IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED: Interface [chars] is down (Error disabled - bit error rate too high) [chars] [chars]
Explanation The port has detected too high bit error rate in frames received from attached device. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the attached device; replace it if needed
Error Message PORT-5-IF_DOWN_BUNDLE_MISCFG: Interface [chars] is down (Isolation due to channel mis-configuration on local or remote switch) [chars] [chars]
Explanation One port across a link is part of a PortChannel while the other is not. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action While adding or deleting a member port from a PortChannel, both ports across the link should be added/deleted. No operation should be performed on either ports until they are both added/deleted.
Error Message PORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change) [chars] [chars]
Explanation FCIP interface temporarily down due to reconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down (Channel admin down) [chars] [chars]
Explanation This interface belongs to a PortChannel and the PortChannel is configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Perform the following commands on the PortChannel interface to which it belongs to bring the interface up: 'config terminal', 'interface [char]', 'shutdown', 'no shutdown'
Error Message PORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface [chars] is down (Channel membership update in progress) [chars] [chars]
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. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Retry the configuration again
Error Message PORT-5-IF_DOWN_DENIED_DUE_TO_PORT_BINDING: Interface [chars] is down(Suspended due to port binding) [chars] [chars]
Explanation The F port is suspended due to being denied by port binding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check the port binding database to allow the host port to log in.
Error Message PORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to domain id assignment failure) [chars] [chars]
Explanation Isolated due to a failure while assigning a domain. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DOMAIN_ID_MISMATCH_ISOLATION: Interface [chars] is isolated (configured fcdomain ID is different from runtime config) [chars] [chars]
Explanation The runtime fcdomain ID does not equal the static configured fcdomain ID. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the fcdomain ID configuration matches the runtime config.
Error Message PORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is down (Isolation due to invalid fabric reconfiguration) [chars] [chars]
Explanation Invalid RCF received. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down (Isolation due to domain manager disabled) [chars] [chars]
Explanation Isolated due to domain manager being disabled. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars] is down (Isolation due to domain manager other side not responding) [chars] [chars]
Explanation Remote end domain manager not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DOMAIN_NOT_ALLOWED_ISOLATION: Interface [chars] is isolated (domain not allowed) [chars] [chars]
Explanation There aren't enough allowed domains to merge the VSANs across the link. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that all assigned domain id's are in the configured allowed domains on both sides of the link.
Error Message PORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars] is down (Isolation due to domain other side eport isolated) [chars] [chars]
Explanation Isolating this interface due to the remote end being isolated. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to domain overlap) [chars] [chars]
Explanation Isolated due to domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_DPVM_VSAN_NOT_FOUND: Interface [chars] is down (dynamic vsan not present) [chars] [chars]
Explanation The specified dynamic vsan is not configured on this switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the dynamic vsan.
Error Message PORT-5-IF_DOWN_DPVM_VSAN_SUSPENDED: Interface [chars] is down (dynamic vsan in suspended state) [chars] [chars]
Explanation The specified dynamic vsan is in suspended state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Un-suspend the dynamic vsan.
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSF_PARAM_ERR: Interface [chars] is down (Isolation due to ELP failure: class F param error) [chars] [chars]
Explanation ELP failed on the interface due to class F param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSN_PARAM_ERR: Interface [chars] is down (Isolation due to ELP failure: class N param error) [chars] [chars]
Explanation ELP failed on the interface due to class N param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PAYLOAD_SIZE: Interface [chars] is down (Isolation due to ELP failure: invalid payload size)
Explanation ELP failed on the interface due to invalid payload size
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PORT_NAME: Interface [chars] is down (Isolation due to ELP failure: invalid port name) [chars] [chars]
Explanation ELP failed on the interface due to invalid port name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_SWITCH_NAME: Interface [chars] is down (Isolation due to ELP failure: invalid switch name) [chars] [chars]
Explanation ELP failed on the interface due to invalid switch name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_TX_BBCREDIT: Interface [chars] is down (Isolation due to ELP failure: loopback detected) [chars] [chars]
Explanation ELP failed on the interface due to loopback connection detected. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Connect to a port on another switch and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_LOOPBACK_DETECTED: Interface [chars] is down (Isolation due to ELP failure: invalid transmit B2B credit) [chars] [chars]
Explanation ELP failed on the interface due to invalid transmit B2B credit. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_RATOV_EDTOV_MISMATCH: Interface [chars] is down (Isolation due to ELP failure: R_A_TOV or E_D_TOV mismatch) [chars] [chars]
Explanation ELP failed on the interface due to R_A_TOV or E_D_TOV mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure R_A_TOV and E_D_TOV values correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_REVISION_MISMATCH: Interface [chars] is down (Isolation due to ELP failure: revision mismatch) [chars] [chars]
Explanation ELP failed on the interface due to revision mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_CODE: Interface [chars] is down (Isolation due to ELP failure: invalid flow control code) [chars] [chars]
Explanation ELP failed on the interface due to invalid flow control code. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_PARAM: Interface [chars] is down (Isolation due to ELP failure: invalid flow control param) [chars] [chars]
Explanation ELP failed on the interface due to invalid flow control param. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ELP failure) [chars] [chars]
Explanation ELP failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the output of 'show port internal info' in the 'ELP failure reason' field
Error Message PORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error Disabled - EPP Failure) [chars] [chars]
Explanation Trunk protocol failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action 'show port internal event-history msgs' will indicate the trunk protocol exchanges to determine why it failed
Error Message PORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ESC failure) [chars] [chars]
Explanation ESC failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the output of 'show port internal event-history' to determine the ESC protocol exchanges to determine how it failed
Error Message PORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port src interface down) [chars] [chars]
Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the ethernet cable is connected, the interface is administratively enabled
Error Message PORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port src interface link down) [chars] [chars]
Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the ethernet cable is connected and the remote end is also active
Error Message PORT-5-IF_DOWN_FABRIC_BIND_FAILURE: Interface [chars] is down(Isolation due to fabric bind failure) [chars] [chars]
Explanation Fabric binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check the fabric binding database to ensure that the remote port is allowed to connect to this port
Error Message PORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not present) [chars] [chars]
Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Insert an FCOT
Error Message PORT-5-IF_DOWN_FCOT_REMOVED: Interface [chars] is down (FCOT has been removed) [chars] [chars]
Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Insert an FCOT
Error Message PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down (Error disabled - FCOT vendor not supported) [chars] [chars]
Explanation FCOT inserted is not a supported one. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please contact customer support for a list of authorized transceiver vendors
Error Message PORT-5-IF_DOWN_FCSP_AUTHENT_FAILURE: Interface [chars] is down (FC-SP authentication failure) [chars] [chars]
Explanation The port failed FC-SP authentication with its peer. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check the FC-SP configuration.
Error Message PORT-5-IF_DOWN_FICON_BEING_ENABLED: Interface [chars] is down(FICON being enabled) [chars] [chars]
Explanation FICON is being enabled on the port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please wait. This might take a while
Error Message PORT-5-IF_DOWN_FICON_NOT_ENABLED: Interface [chars] is down(Error disabled - FICON not enabled) [chars] [chars]
Explanation FICON not enabled on port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please enable FICON on port
Error Message PORT-5-IF_DOWN_FICON_VSAN_DOWN: Interface [chars] is down(FICON vsan down) [chars] [chars]
Explanation FICON is being enabled on the port VSAN of this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action This is an intermediary state, whereby the port VSAN of the port is being enabled to be a FICON VSAN.
Error Message PORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure) [chars] [chars]
Explanation The module's hardware has failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Collect more information about failed module using command 'show module internal all module'
Error Message PORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive) [chars] [chars]
Explanation The port VSAN has been suspended or deleted. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Assign a new active port VSAN to the interface
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down (Error disabled - Incompatible admin port mode) [chars] [chars]
Explanation The configured mode is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Perform a 'show port internal info' to determine the list of modes supported on this interface
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit) [chars] [chars]
Explanation The configured receive B2B credit size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Get the allowed receive B2B credit size from 'show port internal info'
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize) [chars] [chars]
Explanation The configured receive buffer size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Get the allowed receive buffer size from 'show port internal info'
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down (Error disabled - Incompatible admin port speed) [chars] [chars]
Explanation The configured speed is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Perform a 'show port internal info' to determine the range of speed supported on this interface
Error Message PORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down (Initializing) [chars] [chars]
Explanation The interface is in the process of coming up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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
Error Message PORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed) [chars] [chars]
Explanation Interface removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_INVALID_ATTACHMENT: Interface [chars] is down(Invalid attachment) [chars] [chars]
Explanation The peer port does not have the compatible security attributes. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please ensure that the peer port has compatible security attributes as the local port.
Error Message PORT-5-IF_DOWN_INVALID_CONFIG: Interface [chars] is down(Error disabled - Possible PortChannel misconfiguration) [chars] [chars]
Explanation The local and peer port have a PortChannel membership misconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that both the local and peer ports are either both members of the same PortChannel or are not both part of PortChannel
Error Message PORT-5-IF_DOWN_INVALID_FABRIC_BINDING: Interface [chars] is down(Invalid fabric binding exchange) [chars] [chars]
Explanation Fabric binding failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check fabric binding database
Error Message PORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link failure [chars]) [chars] [chars]
Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the cable is connected and the remote end is not shut down
Error Message PORT-5-IF_DOWN_LOCALLY_DISRUPTIVE_RECONFIGURATION: Interface [chars] is down (fcdomain applied a locally disruptive reconfiguration) [chars] [chars]
Explanation Fcdomain applied a locally disruptive reconfiguration (local domain became invalid. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure) [chars] [chars]
Explanation Diag failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Collect more information about failed interface using command 'attach module' to connect to module
Error Message PORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down (Isolation due to port loopback to same switch) [chars] [chars]
Explanation The interface is looped back to another interface on the same switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch
Error Message PORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module removed) [chars] [chars]
Explanation Interface is down because the module was removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_NONE: Interface [chars] is down (None) [chars] [chars]
Explanation There is no apparent reason the interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Collect more information about port using command 'show port internal all interface [char]' to determine why it went down
Error Message PORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non participating) [chars] [chars]
Explanation The loop port has been put into non participating mode. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_NOS_RCVD: Interface [chars] is down (NOS received) [chars] [chars]
Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the cable is connected and the remote end is not shut down
Error Message PORT-5-IF_DOWN_NO_TRUNK_OPER_VSANS_ISOLATION: Interface [chars] is down(Isolation due to no common vsans with peer on trunk) [chars] [chars]
Explanation The trunk port is isolated as there are no common VSANs to be brought up with the peer port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check that there are common VSANs configured and allowed to come up between the ports.
Error Message PORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline) [chars] [chars]
Explanation The interface has been placed into the offline state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_OHMS_EXTERNAL_LB_TEST: Interface [chars] is down(Loopback test) [chars] [chars]
Explanation Loopback tests. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please wait. This might take a while
Error Message PORT-5-IF_DOWN_OLS_RCVD: Interface [chars] is down (OLS received) [chars] [chars]
Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the cable is connected and the remote end is not shut down
Error Message PORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down) [chars] [chars]
Explanation Parent interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn. closed by peer) [chars] [chars]
Explanation The FCIP peer connected to this interface closed the TCP connection. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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
Error Message PORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. reset by peer) [chars] [chars]
Explanation TCP connection to the FCIP peer got reset. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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
Error Message PORT-5-IF_DOWN_PORT_ACT_LICENSE_NOT_AVAILABLE: Interface [chars] is not allowed to come up (port activation license not available [chars] [chars]
Explanation Assign a port activation license to this port or install additional port activation licenses as needed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_PORT_BIND_FAILURE: Interface [chars] is down(Isolation due to port bind failure) [chars] [chars]
Explanation Port binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check the port binding database to ensure that the remote port is allowed to connect to this port
Error Message PORT-5-IF_DOWN_PORT_BLOCKED: Interface [chars] is down(Port blocked due to FICON) [chars] [chars]
Explanation The port has been blocked by FICON configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please unblock the port in FICON configuration.
Error Message PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down (No operational members) [chars] [chars]
Explanation This is a PortChannel interface and all its members are operationally down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Enable at least one of the PortChannel's members
Error Message PORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to port VSAN mismatch) [chars] [chars]
Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and perform a 'shutdown' and a 'no shutdown'
Error Message PORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in progress) [chars] [chars]
Explanation There is an RCF in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port software failure) [chars] [chars]
Explanation The software servicing the data path on the port has failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is down(Tunnel source module not online) [chars] [chars]
Explanation Module that has the tunnel source port of this FCIP interface is not fully online. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action The module that has the tunnel src port is coming online. Please use show mod to find module status
Error Message PORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down (Tunnel port src interface unbound) [chars] [chars]
Explanation Tunnel port source interface unbound. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel src port removed) [chars] [chars]
Explanation Tunnel source port of this FCIP interface has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode) [chars] [chars]
Explanation This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Change the mode and the trunking mode of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down (Suspended due to incompatible speed) [chars] [chars]
Explanation This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Change the speed of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down (Suspended due to incompatible remote switch WWN) [chars] [chars]
Explanation This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel
Error Message PORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended) [chars] [chars]
Explanation This interface belongs to a PortChannel and has been suspended to to an error while bringing it up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action In most cases, you can recover using following commands 'config terminal', 'interface [char]', 'shutdown', 'no shutdown' on the interface. If this happens again obtain output of 'show port internal all interface [char]' on the interface
Error Message PORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is down(TCP conn. closed - Keep alive expired) [chars] [chars]
Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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:traceroute ipaddr
Error Message PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP conn. closed - retransmit failure) [chars] [chars]
Explanation Interface is down due to maximum retransmission failure. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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:traceroute ipaddr
Error Message PORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is down(TCP conn. closed - Persist timer expired) [chars] [chars]
Explanation TCP session to the FCIP peer closed because TCP persist timer expired. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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:traceroute ipaddr
Error Message PORT-5-IF_DOWN_TOO_MANY_INTR: Interface [chars] is down (Error disabled - too many interrupts) [chars] [chars]
Explanation The port has received too many interrupts in the hardware. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the attached device; replace it if needed
Error Message PORT-5-IF_DOWN_TOO_MANY_INVALID_FLOGIS: Interface [chars] is down(Suspended due to too many invalid flogis [chars] [chars]
Explanation The port is suspended due to receiving a large number of invalid FLOGI's. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Please check the HBA and perform a shut, followed by no shut on the port.
Error Message PORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down (Linecard upgrade in progress) [chars] [chars]
Explanation Upgrade of the linecard software is in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_VIRTUAL_IVR_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to virtual IVR domain overlap) [chars] [chars]
Explanation Isolated due to virtual IVR domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down (Isolation due to vsan mismatch) [chars] [chars]
Explanation This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the VSANs configured on the local end with the remote end
Error Message PORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to zone merge failure) [chars] [chars]
Explanation Isolated due to a failure during zone merge. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is down (Isolation due to remote zone server not responding) [chars] [chars]
Explanation Isolated due to remote zone server not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_PORT_GUARD_DOWN: Interface [chars] is down ([chars]) [chars] [chars]
Explanation The interface is down due to port guard configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Perform a shut followed by no shut to bring up the interface
Error Message PORT-5-IF_PORT_QUIESCE_FAILED: Interface [chars] port quiesce failed due to failure reason: [chars] ([hex])
Explanation There may be few packet drops due to this failure
Recommended Action No action is required.
Error Message PORT-5-IF_PSS_DUPLICATE_KEY: Duplicate key found for Interface [chars]
Explanation Duplicate pss key detected
Recommended Action No action is required.
Error Message PORT-5-IF_TRUNK_DOWN: Interface [chars], vsan [chars] is down ([chars]) [chars] [chars]
Explanation Interface [chars] is trunking, VSAN [chars] is down with reason in (). [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
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
Error Message PORT-5-IF_TRUNK_UP: Interface [chars], vsan [chars] is up [chars] [chars]
Explanation Interface [chars] is trunking, VSAN [chars] is up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-IF_UP: Interface [chars] is up [chars] [chars] [chars]
Explanation Interface is up in mode specified, if applicable. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action No action is required.
Error Message PORT-5-MODULE_BRINGUP_NOT_ALLOWED: Not allowing module [dec] to come up for reason: [chars] ([hex])
Explanation Module is not allowed to be operational due to the current system state
Recommended Action Use command "show module
Error Message PORT-5-MODULE_INDEX_RESTORE_ERROR: Error in restoring indices for module [dec]: reason [chars] ([hex])
Explanation Restore of module index may fail due to overlap of indices
Recommended Action No action is required.
Error Message PORT-5-MODULE_UNLIMITED_OSM_SEQ_FAILED: Enable/Disable of unlimited oversubscription failed for module [dec]
Explanation Interfaces of the module may be in indeterminate state
Recommended Action Reload the module
This section contains the PRIVATE_VLAN messages.
Error Message PRIVATE_VLAN-2-PVLAN_ASSOC_DOWN_FAILED: Failed to bring down the association between [dec] & [dec]
Explanation Association bringdown failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_ASSOC_UP_FAILED: Failed to bring up the association between [dec] & [dec]
Explanation Association bringup failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_MTS_SEND_FAILED: MTS send failed while communicating with ELTM.
Explanation ELTM MTS send failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_TIMED_OUT: ELTM timed out while configuring hardware.
Explanation ELTM timed out
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_ETHPM_TIMED_OUT: ETHPM timed out while configuring/unconfiguring hardware
Explanation ETHPM timed out
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_FAIL_TO_ASSOCIATE_PRIMARY_WITH_SECONDARY_VLAN: Failed to bring up the association between [dec] & [dec]
Explanation Association between primary and secondary vlan failed due to an error returned by vlan manager
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_FAIL_TO_COMMUNICATE_REMOVE_VLAN_ASSOCIATION_TO_ELTM: Failed to bring down the association between [dec] & [dec]
Explanation Fail to remove association between primary and secondary vlan due to an error returned by eltm manager
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_FAIL_TO_COMMUNICATE_VLAN_ASSOCIATION_TO_ELTM: Failed to bring up the association between [dec] & [dec]
Explanation Failed to associate primary and secondary vlan due to an error returned by eltm manager
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_FAIL_TO_REMOVE_ASSOCIATION_BETWEEN_PRIMARY_AND_SECONDARY_VLAN: Failed to bring down the association between [dec] & [dec]
Explanation Removing association between primary and secondary vlan failed due to an error returned by vlan manager
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_HW_ERROR: Error [hex] occurred for ifindex [hex] while programming hardware: [chars]
Explanation Hardware Configuration Error
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_MTS_SEND_FAILED: MTS send failed while communicating with PIXM
Explanation PIXM MTS send failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_TIMED_OUT: PIXM timed out while configuring hardware.
Explanation PIXM timed out
Recommended Action No action is required.
Error Message PRIVATE_VLAN-3-PVLAN_ASSOC_SDB_UPDATE_FAILED: Failed to update SDB while [chars] association for vlan [dec]
Explanation SDB Update failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-3-PVLAN_IN_USE: PVLAN [dec] in use by interface [chars], please do "no switchport access vlan" or "no switchport private-vlan host-association"
Explanation PVLAN in use
Recommended Action No action is required.
Error Message PRIVATE_VLAN-3-PVLAN_VLANMGR_FAILURE: Cannot restore association operational state. Failed to communicate with VLAN manager
Explanation Restoring association operational status failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-5-PVLAN_DISABLED: PVLAN Disabled
Explanation PVLAN Service Disabled
Recommended Action No action is required.
Error Message PRIVATE_VLAN-5-PVLAN_DISABLE_FAILED: Disabling of private-vlan failed. Either shutdown these ports or remove the ports that are in switchport mode private-vlan: [chars]
Explanation Disabling of private-vlan failed
Recommended Action No action is required.
Error Message PRIVATE_VLAN-5-PVLAN_ENABLED: PVLAN Enabled
Explanation PVLAN Service Enabled
Recommended Action No action is required.
Error Message PRIVATE_VLAN-5-PVLAN_VTP_DISABLE_FAILED: Either remove all private-vlans from VTP domain or change VTP to transparent mode
Explanation Disabling of private-vlan failed
Recommended Action No action is required.
This section contains the PROFILER messages.
Error Message PROFILER-0-EMERGENCY_MSG: [chars]
Explanation Profiler Emergency Message
Recommended Action Please file the bug for Profiler Library Component thro' CDETS
Error Message PROFILER-1-ALERT_MSG: [chars]
Explanation Profiler Alert Message
Recommended Action Profiler Internal Operation Alert
Error Message PROFILER-2-CRITICAL_MSG: [chars]
Explanation Profiler Critical Message
Recommended Action No action is required.
Error Message PROFILER-3-ERROR_MSG: [chars]
Explanation Profiler Error Message
Recommended Action No action is required.
Error Message PROFILER-4-WARN_MSG: [chars]
Explanation Profiler Warning Message
Recommended Action No action is required.
Error Message PROFILER-5-NOTIF_MSG: [chars]
Explanation Profiler Notification Message
Recommended Action No action is required.
Error Message PROFILER-6-INFO_MSG: [chars]
Explanation Profiler Informational Message
Recommended Action No action is required.
Error Message PROFILER-7-DEBUG_MSG: [chars]
Explanation Profiler Debug Message
Recommended Action No action is required.
This section contains the PSSHELPER_GSVC messages.
Error Message PSSHELPER_GSVC-2-PSS_HELPER_MTS_FAIL: Failed to do MTS operation: [chars].
Explanation Failed to do MTS operation. [chars] is the reason.
Recommended Action Reload module to recover
Error Message PSSHELPER_GSVC-7-PSS_HELPER_BADFLAG: PSS Helper: [chars]
Explanation PSSHelper received a bad flag for bind/unbind request
Recommended Action No action is required.
This section contains the PSS messages.
Error Message PSS-0-PSS_NO_MORE_PAGES: [chars]: needs more working pages
Explanation Service needs more working page buffers
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.
Error Message PSS-0-PSS_NO_MORE_RSM_PAGES: [chars]: needs more rsm pages
Explanation Service needs more rsm page buffers
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.
Error Message PSS-0-PSS_READ_DATA_FAILURE: [chars]: failed to read data to [chars] block [dec]: [chars]
Explanation PSS cannot read data
Recommended Action No action is required.
Error Message PSS-0-PSS_SYNC_DATA_FAILURE: [chars]: failed to sync data to [chars]: [chars]
Explanation PSS cannot sync data due to filesystem or disk error
Recommended Action No action is required.
Error Message PSS-0-PSS_SYNC_LOG_FAILURE: [chars]: failed to sync log: [chars]
Explanation PSS cannot sync log due to filesystem or disk error
Recommended Action No action is required.
Error Message PSS-0-PSS_UNKNOWN_LOG: [chars]: unknown log type [hex] at offset [dec]
Explanation Unknown logging entry found
Recommended Action No action is required.
Error Message PSS-0-PSS_WRITE_DATA_FAILURE: [chars]: failed to write data to [chars] block [dec]: [chars]
Explanation PSS cannot write data due to filesystem or disk error
Recommended Action No action is required.
Error Message PSS-0-PSS_WRITE_FAILURE: [chars]: failed to write data: [chars]
Explanation PSS cannot write data due to filesystem or disk error
Recommended Action No action is required.
Error Message PSS-0-PSS_WRITE_LOG_FAILURE: [chars]: failed to write log: [chars]
Explanation PSS cannot write log due to filesystem or disk error
Recommended Action No action is required.
Error Message PSS-1-PSS_INVALID_MAGIC: [chars]: database [chars] has invalid magic number [hex]
Explanation PSS found a corrupted database with invalid magic number
Recommended Action No action is required.
Error Message PSS-1-PSS_META_READ_ERROR: [chars]: cannot read meta page from [chars]: [chars]
Explanation PSS cannot read meta page of a database
Recommended Action No action is required.
Error Message PSS-1-PSS_STAT_ERROR: [chars]: cannot stat [chars]: [chars]
Explanation PSS cannot do fstat on a database
Recommended Action No action is required.
Error Message PSS-1-PSS_VERSION_MISMATCH: [chars]: found version mismatch in [chars]
Explanation PSS found a database whose format it cannot interpret due to version mismatch
Recommended Action The image upgrade was not done properly; write erase should cure it as a last step
Error Message PSS-2-PSS_ERROR: [chars]
Explanation PSS error log
Recommended Action No action is required.
Error Message PSS-2-PSS_INFRACONVERT: [chars]
Explanation Error in libinfraconvert during pss conversion
Recommended Action No action is required.
Error Message PSS-2-PSS_INVALID_SIZE: [chars]: database [chars] ([chars]) has invalid size %ld (block size [dec])
Explanation PSS found a database with invalid size - probably due to a crash
Recommended Action No action is required.
Error Message PSS-2-PSS_MISSING_FILE: [chars]: database [chars] missing [chars] file
Explanation PSS database is incomplete; probably due to a crash
Recommended Action No action is required.
Error Message PSS-2-PSS_RECOVERY_FAILED: [chars]: failed to recover [chars]
Explanation PSS recovery failed
Recommended Action No action is required.
Error Message PSS-4-PSS_CLEANUP: [chars]: cleaning up [chars]
Explanation PSS removed a leftover or corrupted file
Recommended Action No action is required.
Error Message PSS-4-PSS_RECOVERY_ENDED: [chars]: recovered [chars] successfully
Explanation PSS recovery finished
Recommended Action No action is required.
Error Message PSS-4-PSS_RECOVERY_STARTED: [chars]: recovering [chars]: [dec] valid transactional records
Explanation PSS started recovery of previous aborted transaction
Recommended Action No action is required.
Error Message PSS-5-PSS_CONVERT_FORMAT: [chars]: converting pss format: [chars]
Explanation PSS format is being converted
Recommended Action No action is required.
Error Message PSS-5-PSS_CONVERT_LAYOUT: [chars]: converting pss layout: [chars] (params [dec]/[dec]/[dec] -> [dec]/[dec]/[dec])
Explanation PSS layout is being converted
Recommended Action No action is required.
Error Message PSS-5-PSS_SHRINK: [chars]: shrinking pss: [chars]
Explanation PSS is being shrunk to remove free space
Recommended Action No action is required.
Error Message PSS-5-SDB_CLOSED_AT_COMMIT: [chars]: sdb [chars] is closed: token [dec] is not committed
Explanation Publisher received SDB commit but sdb was already closed
Recommended Action No action is required.
This section contains the PTPLC messages.
Error Message PTPLC-3-PTPLC_PORT_CFG_FAILED: Configuration failed on port [hex], [chars]: [hex], [chars]
Explanation PTP interface configuration error
Recommended Action No action is required.
Error Message PTPLC-3-PTPLC_PTP_INTF_CONFIG_ERROR: Failed to configure PTP/PONG on port [dec]: [hex], [chars]
Explanation PTP interface configuration error
Recommended Action No action is required.
This section contains the PTP messages.
Error Message PTP-5-PTP_DISABLED: PTP disabled
Explanation PTP Service Enabled
Recommended Action No action is required.
Error Message PTP-5-PTP_DOMAIN_CHANGE: PTP domain changed to [dec]
Explanation PTP domain changed
Recommended Action No action is required.
Error Message PTP-5-PTP_ENABLED: PTP enabled
Explanation PTP Service Enabled
Recommended Action No action is required.
Error Message PTP-6-PTP_ANNOUNCE_INTERVAL_CHANGE: PTP announce interval for [hex] changed to [dec]
Explanation PTP announce interval for [chars] changed
Recommended Action No action is required.
Error Message PTP-6-PTP_ANNOUNCE_TIMEOUT_CHANGE: PTP announce timeout interval for [hex] changed to [dec]
Explanation PTP announce timeout interval for [chars] changed
Recommended Action No action is required.
Error Message PTP-6-PTP_DELAY_REQ_INTERVAL_CHANGE: PTP delay-req interval for [hex] changed to [dec]
Explanation PTP delay-req interval for [chars] changed
Recommended Action No action is required.
Error Message PTP-6-PTP_PRIORITY1_CHANGE: PTP priority1 changed to [dec]
Explanation PTP priority1 changed
Recommended Action No action is required.
Error Message PTP-6-PTP_PRIORITY2_CHANGE: PTP priority2 changed to [dec]
Explanation PTP priority2 changed
Recommended Action No action is required.
Error Message PTP-6-PTP_SYNC_INTERVAL_CHANGE: PTP sync interval for [hex] changed to [dec]
Explanation PTP sync interval for [chars] changed
Recommended Action No action is required.
Error Message PTP-6-PTP_TIMESYNC_REG_CHANGE: PTP time-sync register changed
Explanation PTP time-sync reg change
Recommended Action No action is required.
Error Message PTP-6-PTP_VLAN_CHANGE: PTP vlan for [hex] changed to [dec]
Explanation PTP vlan for [chars] changed
Recommended Action No action is required.
This section contains the PULSE messages.
Error Message PULSE-0-EMERGENCY_MSG: [chars]
Explanation Pulse Emergency Message
Recommended Action Please file the bug for Pulse Library Component thro' CDETS
Error Message PULSE-1-ALERT_MSG: [chars]
Explanation Pulse Alert Message
Recommended Action Pulse Internal Operation Alert
Error Message PULSE-2-CRITICAL_MSG: [chars]
Explanation Pulse Critical Message
Recommended Action No action is required.
Error Message PULSE-3-ERROR_MSG: [chars]
Explanation Pulse Error Message
Recommended Action No action is required.
Error Message PULSE-4-WARN_MSG: [chars]
Explanation Pulse Warning Message
Recommended Action No action is required.
Error Message PULSE-5-NOTIF_MSG: [chars]
Explanation Pulse Notification Message
Recommended Action No action is required.
Error Message PULSE-6-INFO_MSG: [chars]
Explanation Pulse Informational Message
Recommended Action No action is required.
Error Message PULSE-7-DEBUG_MSG: [chars]
Explanation Pulse Debug Message
Recommended Action No action is required.
This section contains the QOS messages.
Error Message QOS-2-EXITING: Exit reason: [chars]
Explanation The QOS Manager process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message QOS-2-GENERAL_ERROR: [chars]
Explanation The QOS Manager has encountered an critical error. The description of error is [str.].
Recommended Action No action is required.
Error Message QOS-2-INITFAIL: QoS Manager Initialization failed: [chars]
Explanation QoS Manager initialization failed. [chars] explains the reason for the failure.
Recommended Action No action is required.
Error Message QOS-2-MALLOC_ERROR: Size [dec] bytes
Explanation The QOS Manager could not allocate memory.
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.
Error Message QOS-2-PSS_ERROR: [chars]: PSS returned value=[dec]
Explanation The QOS Manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Error Message QOS-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars]
Explanation The QOS Manager has failed to rotate its current stdout file with filename [str.]. The file size could grow beyond its maximum limit.
Recommended Action No action is required.
Error Message QOS-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation QoS Manager is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message QOS-3-DBERROR: [chars]
Explanation QoS Manager encountered a database error. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message QOS-3-E_PORT_ACL_FAILURE: Failed to [chars] QOS ACL for interface [chars] (ACL return code=[hex])
Explanation The QOS Manager has failed to program or erase QoS related ACL when an E-Port came up or went down for interface [str.]. The error code returned by ACL module is [int.].
Recommended Action No action is required.
Error Message QOS-3-FAILURE_RESPONSE: [chars] [hex]
Explanation QoS Manager failed to get response [chars][hex] specify the context where the failure occurred.
Recommended Action No action is required.
Error Message QOS-3-GENERROR: [chars]
Explanation QoS 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.
Error Message QOS-3-LICERR: [chars]
Explanation QoS Manager failed to get license.
Recommended Action No action is required.
Error Message QOS-3-MTSERROR: [chars]
Explanation QoS Manager encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action No action is required.
Error Message QOS-3-PSSERROR: [chars]
Explanation QoS Manager encountered a PSS error. [chars] specifies the context where the failure occurred.
Recommended Action No action is required.
Error Message QOS-3-QOS_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The QOS Manager has detected corruption in one of its persistent information database. The database would be recreated.
Recommended Action No action is required.
Error Message QOS-3-TIMEOUT_ERROR: [chars] [hex]
Explanation QoS Manager encountered a timeout [chars][hex] specify the context where the failure occurred.
Recommended Action No action is required.
Error Message QOS-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec]
Explanation The QOS Manager has received an unknown message from [dec]].[dec]. This information is for debugging only.
Recommended Action No action is required.
Error Message QOS-4-LICEXP: [chars]
Explanation QoS Manager license is going to expire. [chars] gives the expected time of expiry.
Recommended Action No action is required.
Error Message QOS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the QOS Manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error Message QOS-6-BECAME_ACTIVE: Became ACTIVE from standby mode.
Explanation The QOS Manager on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Error Message QOS-6-BECAME_STDBY: Became STANDBY from active mode.
Explanation The QOS Manager became standby from active mode.
Recommended Action No action is required.
Error Message QOS-6-DISABLED_UP_MARKING: [chars]
Explanation The QoS Manager has disabled marking of time-critical control traffic as high-priority traffic. Priority of such traffic is now not altered by QoS Manager.
Recommended Action No action is required.
Error Message QOS-6-ENABLED_UP_MARKING: [chars]
Explanation The QoS Manager has enabled marking of time-critical control traffic as high-priority traffic.
Recommended Action No action is required.
Error Message QOS-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.].
Recommended Action No action is required.
Error Message QOS-6-E_PORT_ACL_SUCCESS: Successfully [chars] QOS ACL for interface [chars]
Explanation The QOS Manager has successfully programmed or erased QoS related ACL when an E-Port came up or went down for interface [str.].
Recommended Action No action is required.
Error Message QOS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]
Explanation The QOS Manager was unable to send heartbeat to the system manager.
Recommended Action No action is required.
Error Message QOS-6-GENERAL_EVENT: [chars]
Explanation The QOS Manager has generated an important event. The description of the event is [str.].
Recommended Action No action is required.
Error Message QOS-6-MGRCREATED: QoS Manager created
Explanation QoS Manager was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Error Message QOS-6-MGREXIT: QoS Manager shutting down gracefully
Explanation QoS Manager is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message QOS-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of QOS Manager has been recreated.
Recommended Action No action is required.
Error Message QOS-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases of QoS Manager has been intentionally destroyed and would be recreated.
Recommended Action No action is required.
Error Message QOS-6-SERVICE_UP: Initialized [chars]
Explanation The QOS Manager is up and ready to accept client requests The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message QOS-6-SWITCHOVER: Switching Over to other Supervisor.
Explanation The QOS Manager has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Error Message QOS-6-UNKNOWNMTS: QoS Manager received an unexpected message
Explanation QoS Manager received an unexpected message.
Recommended Action No action is required.
This section contains the QUACK_SMC messages.
Error Message QUACK_SMC-6-QUACK_LIB_DEBUG_MSG: [chars]
Explanation Debug log message
Recommended Action No action is required.
This section contains the RADIUS messages.
Error Message RADIUS-2-RADIUS_NO_AUTHEN_INFO: ASCII authentication not supported
Explanation ASCII authentication not supported.
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error Message RADIUS-2-RADIUS_PROGRAM_EXIT: RADIUS daemon exiting: [chars]
Explanation RADIUS 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.
Error Message RADIUS-3-RADIUS_ERROR_MESSAGE: [chars]
Explanation RADIUS Error Message
Recommended Action No action is required.
Error Message RADIUS-4-RADIUS_WARNING: [chars]
Explanation RADIUS Warning
Recommended Action No action is required.
Error Message RADIUS-5-RADIUS_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Radius server monitor status change
Recommended Action No action is required.
Error Message RADIUS-5-RADIUS_NOTIFICATION: [chars]
Explanation RADIUS Notification
Recommended Action No action is required.
Error Message RADIUS-5-RADIUS_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 Radius server status change
Recommended Action No action is required.
Error Message RADIUS-6-RADIUS_ACCOUNTING_MESSAGE: [chars]
Explanation Accounting Message
Recommended Action No action is required.
Error Message RADIUS-6-RADIUS_MESSAGE: [chars]
Explanation RADIUS Message
Recommended Action No action is required.
This section contains the RES_MGR messages.
Error Message RES_MGR-1-RES_MGR_HA_ERR: RES_MGR Error: HA sync message received for resource [dec] which does not exist
Explanation RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover
Recommended Action No action is required.
Error Message RES_MGR-2-RES_MGR_CONFLICTING_RESOURCE_KEYS: RES_MGR Critical Error: The [chars] resource key [dec] from node [dec] is conflicting with other nodes.
Explanation The user should try and release the conflicting resource.
Recommended Action No action is required.
Error Message RES_MGR-2-RES_MGR_CRIT: RES_MGR Critical: [chars]
Explanation RES_MGR generic critical condition
Recommended Action No action is required.
Error Message RES_MGR-2-RES_MGR_HA_PSS_ERR: RES_MGR Error: HA sync message received for resource [dec] with wrong pss type [dec]
Explanation RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover
Recommended Action No action is required.
Error Message RES_MGR-3-RES_MGR_RES_ALREADY_EXCEEDED: RES_MGR Error: The VDC [dec] is currently already using more [chars] resources (total: [dec]) than the desired new maximum limit ([dec])
Explanation A \limit-resource\ command was issued such that a VDC would be a forbidden state if we obeyed, having already allocated more resources than the new maximum limit
Recommended Action No action is required.
Error Message RES_MGR-3-RES_MGR_RES_MAX_LOWER_THAN_MIN: RES_MGR Error: The maximum limit for [chars] resources is not allowed to be less than the minimum limit
Explanation A \limit-resource\ command was issued such that the desired maximum limit was lower than the desired minimum limit
Recommended Action No action is required.
Error Message RES_MGR-3-RES_MGR_RES_TOO_HIGH: RES_MGR Error: Limits for [chars] resources are not allowed to be set as high
Explanation A \limit-resource\ command was issued such that a desired limit couldn't be satisfied because of static policies
Recommended Action No action is required.
Error Message RES_MGR-3-RES_MGR_RES_UNAVAIL: RES_MGR Error: Missing [dec] [chars] resources currently available to satisfy the minimum limit requested for vdc [dec]
Explanation A \limit-resource\ command was issued such that the desired minimum limit couldn't be satisfied with the currently available resources
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_MAX_ALLOWED_VDCS_HAS_DECREASED: RES_MGR Warning: The maximum number of allowed VDCs has decreased from [dec] to [dec] since binary config was saved.
Explanation When startup config was saved, more VDCs were allowed in the system.
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_RES_ALREADY_EXCEEDED_BUT_NOT_ENFORCED: RES_MGR Warning: The VDC [dec] is currently already using more [chars] resources (total: [dec]) than the desired new maximum limit ([dec]) You may experience some route loss upon switchover, when the new limits will actually take effect.
Explanation A \limit-resource\ command was issued such that a VDC may not have enough memory for holding the current amount of routing entries when the new limits will be enforced upon switchover
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_SC_PSS_PCW_NETADMIN: RES_MGR Notification: Performing partial config write for resource [chars] in vdc [dec]
Explanation A \copy running-config startup-config\ command was issued from a local admin resource limits for the specified resource in the specified vdc had to be saved as a side-effect of it
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_SC_PSS_PCW: RES_MGR Notification: Performing partial config write for resource [chars]
Explanation A \copy running-config startup-config\ command was issued from another VDC resource limits for the specified resource had to be saved as part of it
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_UNEXPECTED_MSG_LEN: RES_MGR Warning: The size of this message was expected to be [dec] ([dec] keys of [dec] size with a [dec] bytes header) and instead was [dec].
Explanation A message of unexpected length was received.
Recommended Action No action is required.
Error Message RES_MGR-4-RES_MGR_VLAN_RESERVED_RANGE_UNAVAILABLE: RES_MGR Warning: System is running with limited functionality due to restricted reserved vlan range 3968-4047 should be 3968-4096.
Explanation User should delete VLANS in range 4048-4093 and use following command: system vlan 3968 reserve
Recommended Action No action is required.
Error Message RES_MGR-5-RES_MGR_DISABLED: RES_MGR Disabled
Explanation RES_MGR Service Disabled
Recommended Action No action is required.
Error Message RES_MGR-5-RES_MGR_ENABLED: RES_MGR Enabled
Explanation RES_MGR Service Enabled
Recommended Action No action is required.
Error Message RES_MGR-6-RES_MGR_CONDITION_VERIFIED: RES_MGR info: error [hex] [[chars]] during sysmgrcb_vdc_handshake_done() for vdc [dec]
Explanation RES_MGR is spotting some issue when VDC got created
Recommended Action No action is required.
This section contains the RIB messages.
Error Message RIB-0-EMERG: [chars]
Explanation Rib caused a system 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.
Error Message RIB-1-ALERT: [chars]
Explanation Rib caused failures in other 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.
Error Message RIB-1-LCM_FIB_ERR: RIB failed LC insertion
Explanation RIB stopped linecard from coming online due to error received from FIB during merge operation
Recommended Action Check RIB error logs to see error received from FIB
Error Message RIB-2-CRIT: [chars]
Explanation Rib encountered a catastrophic 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.
Error Message RIB-3-ERR: [chars]
Explanation Rib 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.
Error Message RIB-3-FIB_EXIT: fib exited
Explanation Fib had exited and may not continue operation
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.
Error Message RIB-3-MISS_APPS: Missing response from service
Explanation Service not responding to rib
Recommended Action Please perform 'debug rib error', then recreate the operation scenario, to find out more details.
Error Message RIB-3-NO_MEM: Out of memory
Explanation Rib does not have enough memory to continue proper operation.
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.
Error Message RIB-3-SEND_FIB: Cannot talk to fib
Explanation Rib to fib IPC 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.
Error Message RIB-3-SEND_SNMP: Cannot respond to snmp
Explanation Rib to snmp IPC 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.
Error Message RIB-3-SEND_STANDBY: Cannot talk to standby rib
Explanation Lost a rib-fib transaction log due to IPC 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.
Error Message RIB-4-CPU_HOG: Inactive or busy
Explanation Either rib was not scheduled to run, or rib was busy, and rib did not service the message or timer queue for an extended period.
Recommended Action Please perform 'debug rib error', then recreate the operation scenario, to find out more details.
Error Message RIB-4-DUP_FIB: Duplicate response from fib
Explanation Rib ignored duplicate response from fib
Recommended Action Please perform 'debug rib error', then recreate the operation scenario, to find out more details.
Error Message RIB-4-LATE_FIB: Late response from fib
Explanation Rib ignored late response from fib
Recommended Action Please perform 'debug rib error', then recreate the operation scenario, to find out more details.
Error Message RIB-4-PC_LIMIT: PC number greater than 128 (ignored by RIB)
Explanation Rib ignored pc > 128 for multicast
Recommended Action Please use PC number < 128
Error Message RIB-4-WARN: [chars]
Explanation Rib ignored the unexpected condition
Recommended Action Please perform 'debug rib all', then recreate the operation scenario, to find out more details.
Error Message RIB-5-NOTE: [chars]
Explanation Rib does not support this operation
Recommended Action Please perform 'debug rib all', then recreate the operation scenario, to find out more details.
Error Message RIB-6-INFO: [chars]
Explanation Rib event occurred
Recommended Action No action is required.
This section contains the SAL messages.
Error Message SAL-5-SAL_DISABLED: SAL Disabled
Explanation SAL Service Disabled
Recommended Action No action is required.
Error Message SAL-5-SAL_ENABLED: SAL Enabled
Explanation SAL Service nabled
Recommended Action No action is required.
This section contains the SCHEDULER messages.
Error Message SCHEDULER-2-SCH_SYSLOG_MALLOC_ERR: Out of memory: [chars]
Explanation Process memory exhausted. Possible memory leak.
Recommended Action Contact TAC
Error Message SCHEDULER-2-SCH_SYSLOG_MTS_ERR: MTS error: [chars]
Explanation MTS operation failure
Recommended Action Contact TAC
Error 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
Error Message SCHEDULER-2-SCH_SYSLOG_SDWRAP_ERR: Debug infrastructure initialization failed: [chars]
Explanation Debug infrastructure failed to initialize
Recommended Action Contact TAC
Error Message SCHEDULER-3-SCH_ERR: [chars]
Explanation Scheduler error
Recommended Action No action is required.
Error Message SCHEDULER-3-SCH_SYSLOG_FILE_ERR: [chars] Error:[chars]
Explanation File handling error
Recommended Action No action is required.
Error 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
Error Message SCHEDULER-3-SCH_SYSLOG_USER_ERR: Description: Failed to execute job for user id [chars] Error:[dec]
Explanation Error while attempting to execute job for user. Possibly, the user is removed from the system.
Recommended Action Ensure the user exists. Make sure he is not a remotely authenticated user.
Error Message SCHEDULER-4-SCH_WARN: [chars]
Explanation Scheduler warning
Recommended Action No action is required.
Error Message SCHEDULER-6-SCH_MSG: [chars]
Explanation Scheduler Message
Recommended Action No action is required.
This section contains the SECURITYD messages.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SECURITYD-2-FIPS_POST_ERROR_MSG: [chars]
Explanation Fips post Error Message
Recommended Action No action is required.
Error 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.
Error Message SECURITYD-2-FIPS_POST_TEST_FAILED: FIPS crypto-test failure : [dec]
Explanation FIPS crytpo-test failed [chars]
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SECURITYD-2-INVALID_ADMIN_PASSWD: User admin has NULL password. Copy r s aborted
Explanation User admin has NULL password. Copy r s aborted
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SECURITYD-6-ACCOUNTING_MESSAGE: [chars]
Explanation Accounting Message
Recommended Action No action is required.
Error Message SECURITYD-6-CHANGE_PASSWD: changing passwd for [chars]
Explanation Changing passwd for [chars]
Recommended Action No action is required.
Error 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.
Error Message SECURITYD-6-FIPS_MODE_SET_FAILED: Error when setting FIPS mode : [chars]
Explanation FIPS mode failed [chars]
Recommended Action No action is required.
Error 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.
Error Message SECURITYD-6-FIPS_POST_INFO_MSG: [chars]
Explanation Fips post Information Message
Recommended Action No action is required.
This section contains the SENSOR_USD messages.
Error 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.
Error Message SENSOR_USD-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down: [chars]
Explanation Sensor Manager syslog message
Recommended Action No action is required.
Error Message SENSOR_USD-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation failed
Explanation Sensor Manager syslog message
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SENSOR_USD-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started
Explanation Sensor Manager syslog message
Recommended Action No action is required.
This section contains the SENSOR messages.
Error Message SENSOR-0-DC3_SENSOR_MSG: [chars]
Explanation SENSOR log emergency message
Recommended Action No action is required.
Error Message SENSOR-3-DC3_SENSOR_MSG1: [chars]
Explanation SENSOR log message
Recommended Action No action is required.
This section contains the SESSION-MGR messages.
Error 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.
Error Message SESSION-MGR-3-CSM_CFS_SEND_FAILED: CFS send failed. Error: '[chars]' '([hex])'
Explanation CFS send status
Recommended Action No action is required.
Error Message SESSION-MGR-3-CSM_SP_DEL_FAILED: Switch-profile delete failed: '[chars]'
Explanation Switch-profile deletion
Recommended Action No action is required.
Error Message SESSION-MGR-3-CSM_SP_PEER_TIMEOUT: Peer timed-out in sending next request
Explanation Peer timeout
Recommended Action No action is required.
Error Message SESSION-MGR-3-SSN_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.
Error Message SESSION-MGR-4-CSM_COMMIT_FAILED: Commit failed for switch-profile '[chars]' Session Type: '[chars]'
Explanation Commit failed for the switch-profile
Recommended Action Please identify the cause of the error and fix it
Error Message SESSION-MGR-4-CSM_CREATE_CHECKPOINT_FAILED: Create-checkpoint failed: Name:'[chars]', retval: '[hex]'
Explanation Create-checkpoint status
Recommended Action No action is required.
Error Message SESSION-MGR-4-CSM_DELETE_PROFILE_FAILED: Switch-profile deletion failed switch-profile '[chars]' Session type:'[chars]'
Explanation Switch-profile deletion failed for the switch-profile
Recommended Action Please identify the cause of the error and fix it
Error Message SESSION-MGR-4-CSM_DEL_CHECKPOINT_FAILED: Del-checkpoint failed: Name:'[chars]'
Explanation Del-checkpoint status
Recommended Action No action is required.
Error Message SESSION-MGR-4-CSM_FILE_BASED_ROLLBACK_FAILED: File-based rollback failed: Switch profile:'[chars]'
Explanation File-based rollback status
Recommended Action No action is required.
Error Message SESSION-MGR-4-CSM_PEER_INFO_NOT_FOUND: Peer [chars] is not yet configured in the switch-profile '[chars]'
Explanation This peer is not yet configured in the switch-profile
Recommended Action Please configure the peer in the switch-profile
Error Message SESSION-MGR-4-CSM_ROLLBACK_FAILED: Rollback failed: Switch profile:'[chars]'
Explanation Rollback status
Recommended Action No action is required.
Error Message SESSION-MGR-4-CSM_VERIFY_FAILED: Verification failed for switch-profile '[chars]' Session type: '[chars]'
Explanation Verification failed for the switch-profile
Recommended Action Please identify the cause of the error and fix it
Error 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.
Error Message SESSION-MGR-6-CSM_CREATE_CHECKPOINT_SUCCESS: Create-checkpoint success: Name:'[chars]', checkpoint_id: '[dec]'
Explanation Create-checkpoint status
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_DEL_CHECKPOINT_SUCCESS: Delete-checkpoint successful: Name:'[chars]'
Explanation Del-checkpoint status
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_FILE_BASED_ROLLBACK_SUCCESS: File-based rollback successful: Switch profile:'[chars]'
Explanation File-based rollback status
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_LOCAL_SESSION_COMPLETE: [chars]: Name '[chars]' Type:'[chars]' Subtype:'[chars]' Local status:'[chars]'
Explanation Completed local session info
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_ROLLBACK_SUCCESS: Rollback successful: Switch profile:'[chars]'
Explanation Rollback status
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SESSION_COMPLETE: [chars]: Name '[chars]' Type:'[chars]' Subtype:'[chars]' Local status:'[chars]' Peer:'[chars]' Peer status:'[chars]'
Explanation Completed session info
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SESSION_INIT: Initiating a session. [chars]: Profile name:'[chars]' Type:'[chars]' Subtype:'[chars]' Peer [chars]
Explanation Iniitating a session
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_DELETE_IN_PROGRESS: Switch-profile delete in progress: switch-profile: '[chars]'
Explanation Switch-profile delete status
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_DEL_SUCCESS: Switch-profile delete succeeded: '[chars]'
Explanation Switch-profile deletion
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_LOCAL_DELETE: [chars]: Name '[chars]' Type:'[chars]' Subtype:'[chars]' Peer:'[chars]'
Explanation Received switch-profile delete local-config
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_PEER_ADD: Received peer-add for peer-ip: '[chars]'
Explanation Peer addition
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_PEER_DEL: Received peer-delete for peer-wwn: '[chars]'
Explanation Peer deletion
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_SP_REMOTE_PEER_DELETE: Peer has been unconfigured on remote switch: Peer-ip: '[chars]'
Explanation Received peer delete from remote switch
Recommended Action No action is required.
Error Message SESSION-MGR-6-CSM_UNKNOWN_SESSION_TYPE: Attempt to initiate unknown session. Profile name:'[chars]' Type:'[dec]' Subtype:'[dec]' Peer:'[chars]'
Explanation Iniitating a session
Recommended Action No action is required.
This section contains the SFLOW messages.
Error Message SFLOW-3-NO_MBUF: Failed to allocate mbuf [chars]
Explanation The sFlow process has run out of network buffers
Recommended Action No action is required.
Error Message SFLOW-3-SFLOW_AGENT_LOG_ERR: sFlow agent error: [chars]
Explanation SFlow agent error
Recommended Action No action is required.
Error Message SFLOW-3-SFLOW_LOG_ERR: [chars]
Explanation SFlow error
Recommended Action No action is required.
Error Message SFLOW-4-SFLOW_LOG_WARN: [chars]
Explanation SFlow warning
Recommended Action No action is required.
Error Message SFLOW-5-SFLOW_DISABLED: SFLOW Disabled
Explanation SFLOW Service Disabled
Recommended Action No action is required.
Error Message SFLOW-5-SFLOW_ENABLED: SFLOW Enabled
Explanation SFLOW Service nabled
Recommended Action No action is required.
Error Message SFLOW-6-SFLOW_LOG_INFO: [chars]
Explanation SFlow info
Recommended Action No action is required.
Error Message SFLOW-7-SFLOW_LOG_DEBUG: [chars]
Explanation SFlow debug
Recommended Action No action is required.
This section contains the SIM messages.
Error 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.
Error 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 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 'no shutdown' on the interface or removing and re-inserting the fibre optic cable.
Error 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
Error 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
Error Message SIM-2-SIM_TXN_EVSEQ_TIMER_EXPIRED: evseq [chars] timed out for transaction [chars] sap [chars] opcode [chars]
Explanation Sim evseq timer expired
Recommended Action No action is required.
Error Message SIM-2-SIM_TXN_ROLLBACK_STARTED: from original transaction [chars] to rollback transaction [chars]
Explanation Sim rollback started
Recommended Action No action is required.
Error 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
Error 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 'no shutdown' on the PortChannel interface that it belongs to
Error 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.
Error 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.
Error 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
Error 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
Error Message SIM-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface [chars] is not supported
Explanation The transceiver for the interface specified in the error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error Message SIM-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]
Explanation Interface is admin up
Recommended Action No action is required.
Error 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.
Error 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 'no shutdown'
Error 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.
Error 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 'no shutdown' on the PortChannel interface that it belongs to
Error 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
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error Message SIM-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure)
Explanation The module's hardware has failed
Recommended Action Collect more information about failed module using command 'show module internal all module'
Error 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
Error 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
Error 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'
Error 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'
Error 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
Error 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
Error Message SIM-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down (Interface removed)
Explanation Interface removed
Recommended Action No action is required.
Error 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
Error 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 'attach module' to connect to module
Error 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
Error 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.
Error 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
Error 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.
Error 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.
Error 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.
Error 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
Error 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
Error 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's members
Error 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 'no shutdown'
Error 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.
Error 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.
Error 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
Error 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.
Error 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
Error 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 PortChannel
Error 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 speedode of the interface is different from that of the PortChannel
Recommended Action Change the speed of the PortChannel from 'auto' and check to ensure that the remote end of the interface also belongs to the same PortChannel
Error 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
Error 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 'no shutdown'. If this happens again obtain output of 'show port internal info/event-history' on the interface
Error 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:traceroute ipaddr
Error 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:traceroute ipaddr
Error 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:traceroute ipaddr
Error 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.
Error 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.
Error 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
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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
Error 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.
Error 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.
Error 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.
Error 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.
Error 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
Error 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.
This section contains the SKSD messages.
Error Message SKSD-2-SKSD_CRYPT_SERVICE_CRIT: Encryption-Service: [chars]
Explanation Encryption Service critical errors.
Recommended Action No action is required.
Error Message SKSD-3-SKSD_CRYPT_SERVICE_ERR: Encryption-Service: [chars]
Explanation Encryption Service errors.
Recommended Action No action is required.
Error 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.
Error Message SKSD-3-SKSD_FIPS_MODE_SELFTEST: FIPS POST for [chars] [chars]
Explanation FIPS Selftest Result
Recommended Action No action is required.
Error Message SKSD-4-SKSD_CRYPT_SERVICE_WARN: Encryption-Service: [chars]
Explanation Encryption Service warnings.
Recommended Action No action is required.
Error Message SKSD-5-SKSD_CRYPT_SERVICE_NOTICE: Encryption Service: [chars]
Explanation Encryption Service updates.
Recommended Action No action is required.
Error Message SKSD-5-SKSD_EXIT: Keystore Application Exiting: [chars]
Explanation Keystore Program exiting
Recommended Action No action is required.
Error Message SKSD-5-SKSD_FUNC: Keystore Operation: [chars]
Explanation Keystore Event upon a receiving a request
Recommended Action No action is required.
Error Message SKSD-5-SKSD_HW_INIT: Hardware Keystore Init done
Explanation Hardware Keystore Init completed
Recommended Action No action is required.
Error Message SKSD-5-SKSD_HW_RESET: Hardware Reset :[chars]
Explanation Hardware Reset
Recommended Action No action is required.
Error Message SKSD-5-SKSD_HW: Smartcard :[chars]
Explanation Smartcard Presence
Recommended Action No action is required.
Error Message SKSD-5-SKSD_INIT: Keystore Application Init: [chars]
Explanation Keystore Program Init
Recommended Action No action is required.
Error Message SKSD-5-SKSD_KEY_ADD: Key added
Explanation Key added to keystore
Recommended Action No action is required.
Error Message SKSD-5-SKSD_KEY_DELETE: Key deleted
Explanation Key deleted from keystore
Recommended Action No action is required.
Error 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.
Error Message SKSD-5-SKSD_SUP_STATE: Supervisor card new state: [dec]
Explanation Supervisor state change
Recommended Action No action is required.
Error Message SKSD-5-SKSD_SW_INIT: Software Keystore Init done
Explanation Software Keystore Init completed
Recommended Action No action is required.
Error Message SKSD-6-SKSD_CRYPT_SERVICE_INFO: Encryption Service: [chars]
Explanation Encryption Service informational updates.
Recommended Action No action is required.
This section contains the SME_CPP messages.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SME_CPP-2-LOG_WARN_SME_LICENSE_GRACE: No SME License. Feature will be shut down after a grace period of approximately [dec] days
Explanation SAN Media Encryption feature on grace period. Please acquire actual license.
Recommended Action No action is required.
Error Message SME_CPP-2-SME_INIT_FAILED: Initialization failed for SME: [chars], Reason: [hex]
Explanation Initialization failed for SME
Recommended Action No action is required.
Error 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.
Error Message SME_CPP-3-LOG_ERR_SME_DISK_CAPACITY_NOT_SUPPORTED: The capacity of media for disk DG: [chars] CD NAME: [chars] (0x%Lx) less than signature metadata size [hex]
Explanation Disk size less than sme disk reserved area
Recommended Action No action is required.
Error Message SME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_NOT_FOUND: crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not find cnode ([chars] if_index: [hex])
Explanation The data preparation failed since crypto node assigned for data prepration is not found
Recommended Action No action is required.
Error Message SME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_OVERLOAD: crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not be assgined 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.
Error 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] doesnt match cdisk DG: [chars] and CD NAME: [chars]
Explanation The discovered vendor id information not match the cryptodisk
Recommended Action No action is required.
Error 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.
Error 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 cryptodisk
Recommended Action No action is required.
Error 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.
Error 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.
Error 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] doesnt 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.
Error 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.
Error Message SME_CPP-3-LOG_ERR_SME_DISK_UNEXP_SIG_CHANGE: The signature found on media for disk DG: [chars] CD NAME: [chars] does not match expected signature. Signature changed unexpectedly putting disk in failed state
Explanation Signature on disk has changed unexpectedly
Recommended Action No action is required.
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CLUSTER_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] and security mode [dec], but the DPP has state from a previous instance of a cluster [chars] with ID [chars] and security mode [dec].
Explanation DPP has persistent state about a previous cluster membership incarnation, but the interface is part of a different cluster.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_PARAMS: SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars], but the DPP is identified as [chars].
Explanation DPP has persistent state about a previous cluster membershipon a different switch or module.
Recommended Action No action is required.
Error 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.
Error 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 preperation failed
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SME_CPP-3-SME_DISK_INPUT_KEY_SIGNATURE_MISMATCH: sme input key and signature mismatch dg:[chars] cd:[chars] input guid:[chars] clone guid:[chars] signature guid:[chars] clone guid:[chars]
Explanation Sme input key and signature mismatch
Recommended Action No action is required.
Error Message SME_CPP-3-SME_DISK_UNCFG_LUN_HAS_SIG: An unconfigured lun vpd: [chars] [chars] [chars] has crypto signature. Please configure in SME to manage encryption
Explanation Signature found on a unconfigured lun
Recommended Action No action is required.
Error Message SME_CPP-3-SME_FIPS_MODE_ERROR: SME FIPS error: [chars]
Explanation SME module FIPS mode error
Recommended Action No action is required.
Error 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.
Error Message SME_CPP-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface [chars] exceeded the optimum IT Nexus limit
Explanation Iterface Flow Limit
Recommended Action No action is required.
Error 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.
Error 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.
Error 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 preperation succeeded
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SME_CPP-5-LOG_SME_INTERFACE_DOWN: SME Interface ([chars]) DOWN
Explanation SAN Interface was brought down
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SME_CPP-5-SME_DISABLED: SME Disabled
Explanation SME Service Disabled
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_DISC: crypto disk data preparation (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.
Error Message SME_CPP-5-SME_ENABLED: SME Enabled
Explanation SME Service nabled
Recommended Action No action is required.
Error 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.
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_ITL_MISCONFIG: Different physical LUNs under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:[chars] Serial Num:[chars] Serial Num:[chars]
Explanation Different physical LUNs under same Tape Device
Recommended Action No action is required.
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_LUN_MISCONFIG: Different physical LUNs under same ITL - Old Serial Num:[chars] New Serial Num:[chars]
Explanation Different physical LUNs under same ITL
Recommended Action No action is required.
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_BYPASS_ENC_DISABLED_BY_USER: BYPASS Encryption disabled by USER- WRITES will be FAILED for partly written tape, PLEASE REWIND THE TAPE - Cluster:[chars] BKGRP Name:[chars] Tape Device:[chars] Serial Num:[chars]
Explanation WRITES for this Tape will FAIL, REWIND the TAPE
Recommended Action No action is required.
Error 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] Barcode:[chars]
Explanation This tape is currently not being encrypted
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SME_CPP-SLOT#-3-DISK_WRITE_SIGNATURE_FAILED: [chars] Lun [chars] SigLBA 0x%Lx isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]
Explanation ITL write signature IO failure, please check status
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_LUN_DISCOVERY_FAIL: [chars] - REPORT_LUNS didn't include configured lun, INQUIRY of LUN:%llx FAILED with ScsiSts=[hex] SenseKey=[hex] ASC=[hex] ASCQ=[hex]
Explanation Discovery of CONFIGURED LUN Failed
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SME_CPP-SLOT#-3-READ_CAPACITY_FAILED: [chars] Lun [chars] isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]
Explanation ITL read capacity failure, please check status
Recommended Action No action is required.
Error Message SME_CPP-SLOT#-3-READ_IO_TEST_FAILED: [chars] Lun [chars] isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]
Explanation ITL read io test failure, please check status
Recommended Action No action is required.
Error 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.
Error Message SME_CPP-SLOT#-5-DISK_WRITE_SIGNATURE_SUCCESS: [chars] Lun [chars] SigLBA 0x%Lx Key Guid [chars]
Explanation ITL write signature IO succeeded
Recommended Action No action is required.
Error Message SME_CPP-SLOT#-5-READ_CAPACITY_SUCCESS: [chars] Lun [chars] Max LBA 0x%Lx Block Length [hex]
Explanation ITL read capacity IO succeeded
Recommended Action No action is required.
Error Message SME_CPP-SLOT#-5-READ_IO_TEST_SUCCESS: [chars] Lun [chars] Key Guid [chars]
Explanation ITL read signature IO succeeded
Recommended Action No action is required.
This section contains the SNMPD messages.
Error Message SNMPD-1-ALERT: SNMP log alert : [chars]
Explanation SNMP log alert message.
Recommended Action No action is required.
Error Message SNMPD-2-CRITICAL: SNMP log critical : [chars]
Explanation SNMP log critical message.
Recommended Action No action is required.
Error Message SNMPD-3-ERROR: SNMP log error : [chars]
Explanation SNMP log error message.
Recommended Action No action is required.
Error Message SNMPD-4-WARNING: SNMP log warning : [chars]
Explanation SNMP log warning message.
Recommended Action No action is required.
Error Message SNMPD-5-NOTIFICATION: SNMP log notification : [chars]
Explanation SNMP log notification message.
Recommended Action No action is required.
Error Message SNMPD-6-INFO: SNMP log informational : [chars]
Explanation SNMP log info message.
Recommended Action No action is required.
Error Message SNMPD-7-DEBUG: SNMP log debugging : [chars]
Explanation SNMP log debug message.
Recommended Action No action is required.
This section contains the SPAN messages.
Error 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.
Error Message SPAN-3-IPC_FAIL: IPC Error
Explanation Internal IPC error
Recommended Action No action is required.
Error 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.
Error Message SPAN-5-ATL_VSAN_DEFAULT_ALL: Default to all VSANs for SPAN egress session
Explanation Generation 2 fabric switches support only one VSAN filter for 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.
Error Message SPAN-5-SPAN_CFG_REJECT_SRC_VSAN_FILTER_NOT_SUPPORTED: Source interface [[chars]] in dir [[chars]] removed from session [[dec]].
Explanation Interface level VSAN filters is not supported
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SPAN-5-SPAN_PVLAN_SRC: Private vlan source is not supported in monitor session.
Explanation Private vlan source not supported in span/erspan sessions.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
This section contains the STATSCLIENT messages.
Error 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.
Error 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.
Error 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.
Error 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.
This section contains the STATSINFRA messages.
Error Message STATSINFRA-3-STATS_INFRA_CRIT: [chars]
Explanation StatsInfra 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.
Error Message STATSINFRA-3-STATS_INFRA_ERR: [chars]
Explanation StatsInfra 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.
Error Message STATSINFRA-3-STATS_INFRA_INFO: [chars]
Explanation StatsInfra 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.
This section contains the STP messages.
Error 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 error 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 portfast enabled. After the conflict has been resolved, re-enable the interface by entering the
Error 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
Error 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.
Error 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.
Error 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
Error 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
Error 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
Error 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
Error 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 error message
Recommended Action No action is required.
Error 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
Error 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 advertizing 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
Error 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
Error Message STP-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars].
Explanation The spanning tree loopguard configuration for the listed interface has been changed. If enabled, the interface will be put into blocking state and marked as loopguard 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.
Error 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
Error Message STP-2-PEER_IN_UPGRADE: Peer is going through Upgrade. Can't bring up NON Edge port [hex] in STP
Explanation Peer is going through Upgrade. Can't bring up NON Edge port in STP
Recommended Action LOG_STD_NO_ACTION
Error 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.
Error 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
Error 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.
Error 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.
Error 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.
Error 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
Error 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 ths 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.
Error Message STP-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on [chars].
Explanation The listed interface is no longer receiving BPDUs advertizing 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
Error 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
Error 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
Error 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.
Error 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
Error Message STP-2-STP_MODE_CHANGE_FAIL: STP Mode Change to [chars] failed
Explanation STP mode change 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.
Error Message STP-2-STP_MODE_CONFIG_FAIL: STP Mode config failed,PVRST mode is not supported when there are more than [dec] user VLANs configured
Explanation STP mode config failed
Recommended Action Please remove extra VLANs if you need to change to PVRST mode!
Error Message STP-2-STP_MST_INSTANCE_CONFIG_FAIL: STP MST instance config change failed for [dec]
Explanation STP MST instance config change 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.
Error Message STP-2-STP_VPC_PEER_ISSU_DISRUPTIVE: Possible traffic disruption due to ISSU on VPC peer. [chars]
Explanation This is due to some non VPC ports in Desg FWD state on the device or BA timers enabled. It can be prevented by changing the root for those non vPC port vlans, disabling Bridge Assurance timers on non vPC ports
Recommended Action LOG_STD_NO_ACTION
Error 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
Error 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
Error 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 error message, has exceeded the limit specified in the error 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
Error 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.
Error 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.
Error 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
Error 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 administatively 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
Error 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
Error 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.
Error 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 error message as it is printed and also copy the output of a show interface for the interace listed in the error message.
Error 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.
Error 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 stongly 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
Error 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 stongly 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.
Error 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
Error Message STP-6-FIRST_BPDU_TX: First BPDU transmitted
Explanation First BPDU transmitted.
Recommended Action No action is required.
Error 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
Error 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
Error 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
Error 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
Error 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
Error Message STP-6-PORT_DELETED: Interface [chars], removed from [chars]
Explanation This spanning tree port has been deleted
Recommended Action LOG_STD_NO_ACTION
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error 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
Error Message STP-6-SERVICE_UP: Initialized [chars]
Explanation STP line 2.
Recommended Action No action is required.
Error 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.
This section contains the STRIPCL messages.
Error Message STRIPCL-4-LABEL_FAILED: Label [dec] cannot be added as HW programming failed:[dec]([chars])
Explanation HW API Fail, so new label cannot be added
Recommended Action Correct the error and retry
Error Message STRIPCL-4-LABEL_THRESHOLD: MPLS label count([dec]) has gone [chars] the [dec]% threshold. Last [dec]
Explanation The number of labels in system has crossed a threshold
Recommended Action Adjust the label age or delete entries to prevent hitting the limit
Error Message STRIPCL-5-LABEL_LIMIT: More labels cannot be added as [dec] are already in use. Last [dec]
Explanation HW limit has reached, so new labels cannot be added
Recommended Action Delete the extra labels or wait for aging
This section contains the SYSMGR messages.
Error Message SYSMGR-0-ACTIVE_SUP_LESS_MEMORY: Active is Sup-A & Standby is Sup-B, replace Sup-A in slot [dec] with Sup-B for continued redundancy post switchover
Explanation Supervisor memory mismatch
Recommended Action No action is required.
Error Message SYSMGR-0-STANDBY_SUP_LESS_MEMORY: Active is Sup-B & Standby is Sup-A, replace Sup-A in slot [dec] with Sup-B for continued redundancy post switchover
Explanation Supervisor memory mismatch
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-2-BOOTSCOPE_HANDSHAKE: Service "[chars]" is in the boot scope, but tried a regular handshake. Discarding request.
Explanation A service is trying to take actions that belong to a different class of services.
Recommended Action 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.
Error Message SYSMGR-2-CFGCTRL_SBY_SAVE_FAILED: The cfgctrl process has failed to save the config on the standby supervisor. reason: [chars]
Explanation Configuration control has failed to save the configuration on the standy supervisor.
Recommended Action Please see the reason string
Error 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.
Error 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 'init system' to initialize the configuration partition.
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration snapshot.
Explanation An attempt to copy the startup-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 'init system' to initialize the configuration partition.
Error 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.
Error 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.
Error Message SYSMGR-2-CFGWRITE_ABORTED_CONFELEMENT_RETRIES: Copy R S failed as config-failure retries are ongoing. Type "show nxapi retries" for checking the ongoing retries.
Explanation Copy R S failed as config-failure retries are ongoing.
Recommended Action Please verify the syslog messages printed correct the problem, and try again.
Error 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 'init system' to initialize the configuration partition.
Error Message SYSMGR-2-CFGWRITE_ABORTED_INIT: Unable to initialize the configuration directory (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-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 'init system' to initialize the configuration partition.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LABEL: Unable to label the new configuration (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-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 'init system' to initialize the configuration partition.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOCK: Unable to lock the configuration (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-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.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOG: Unable to open a log file for the new configuration: [chars] (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-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 'init system' to initialize the configuration partition.
Error 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.
Error 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.
Error Message SYSMGR-2-CFGWRITE_USER_ABORT: Configuration copy aborted by the user.
Explanation The user typed CTRL+C while the configuration was being saved, and the operation has been aborted.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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 'init system' to initialize the configuration partition.
Error 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.
Error Message SYSMGR-2-CORE_SAVE_FAILED: [chars]: PID [dec] with message [chars].
Explanation
Recommended Action No action is required.
Error Message SYSMGR-2-CREATE_DONEFILE_FAILED: Creating /var/run/sysmgr.initdone failed with return value: ([dec]).
Explanation The initialization of the system could not complete.
Recommended Action 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.
Error 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 'init system' to initialize the configuration partition.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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
Error Message SYSMGR-2-GSYNC_GET_TIMEOUT: Request for global sync for UUID [hex] not completed in specified time.
Explanation Service failed to complete global sync in specified time. The standby will no longer act as a HA standby.
Recommended Action If the problem persists, please contact customer support.
Error Message SYSMGR-2-GSYNC_READY_SRVFAILED: Service "[chars]" on standby supervisor failed to restore its snapshot (error-id [hex]).
Explanation The initial synchronization of service [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.
Error Message SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service "[chars]" on active supervisor failed to store its snapshot (error-id [hex]).
Explanation The initial synchronization of service [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.
Error 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.
Error Message SYSMGR-2-HAP_FAILURE_SUP_RESET: Service "[chars]" in vdc [dec] has had a hap failure
Explanation One of the services failed HA policy. This module would reset if hap-reset is enabled. Service will not restart if module is not reset
Recommended Action No action is required.
Error 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 switchover.
Error 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 switchover.
Error 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.
Error Message SYSMGR-2-INBAND_START_FAILED: Failure while bringing up inband after ISSU reboot, errno: [dec].
Explanation Sysmgr tried to bring up inband 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.
Error Message SYSMGR-2-INVALID_HANDSHAKE: Invalid secret ([dec]) received from service "[chars]". Expected [dec].
Explanation A service can't 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.
Error Message SYSMGR-2-INVALID_SYSMGRCONF: [chars]: invalid configuration file "[chars]": [chars] (error-id [hex]).
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-INVALID_VERSIONMSG: The remote System Manager ([chars]) declares itself in the same state as this System Manager ([chars]).
Explanation The redundancy state negotiation between the two supervisors failed.
Recommended Action 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.
Error 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.
Error Message SYSMGR-2-LAST_CORE_BASIC_TRACE: [chars]: PID [dec] with message [chars].
Explanation
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-2-MTS_FLUSH_SYNC_QUEUE_FAILURE: flush mts sync queue failed with [chars] (errno [dec])
Explanation Calling mts_flush_sync_queue to guarante 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.
Error 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
Error 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
Error 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 onboard'. If this message continues to persist, please contact TAC.
Error Message SYSMGR-2-PARSEERR_DEPENDCYCLE: Dependency cycle found among [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDCONFIG: [chars]: duplicated definition for service config. Previous definition in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDDEPEND: [chars]: duplicated dependency from "[chars]" for service "[chars]". Previous use in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDNAME: [chars]: short name "[chars]" used by service "[chars]" is also used by service "[chars]" in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDOPTION: [chars]: duplicated definition for option [chars]->[chars] (service "[chars]"). Previous definition in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDSERVICE: [chars]: duplicated definition for service "[chars]". Previous definition in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDVERDB: [chars]: duplicated definition for service version_db. Previous definition in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_DUP_UGRPENTRY: [chars]: service "[chars]" duplicated in the current upgrade group. Previous use in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_FT_SET_ID_PARSEERR: [chars]: ft_set_id ([dec]) out of bound for "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDCONDDEPEND: [chars] (in dependency list of ASAP service "[chars]"): conditional service "[chars]" not allowed.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDDEPEND: [chars] (in dependency list of service "[chars]"): service "[chars]" not defined for scope "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDEXEC: [chars]: invalid executable "[chars]" for service "[chars]": [chars] ([dec]).
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDHANDSHAKEDEPEND: [chars] (in handshake dependency list of service "[chars]"): service "[chars]" is MTS unaware or not defined for scope "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDIDENT: [chars]: [chars] "[chars]" not found for service "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDOPTION: [chars]: option [chars]->[chars] cannot be set to "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALIDSTDBYDEPEND: [chars]: service "[chars]" cannot be dependent on service "[chars]" due to the standby mode wait for that service.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error 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't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_DIR: [chars]: "[chars]" is not a valid [chars]: [chars] ([dec]).
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_GLOBAL_SYNC: [chars]: mts unaware service may not request for a global sync.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_HB: [chars]: "[dec]" is not a valid heartbeat timeout.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_SHELLTREE: [chars]: invalid shell parser tree "[chars]" for service "[chars]": [chars] ([dec]).
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE: [chars]: standby_mode should be run.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't proceed further.
Recommended Action No action is required.
Error Message SYSMGR-2-PARSEERR_INVALID_TRANSL: [chars]: invalid translator "[chars]" for service "[chars]": [chars] ([dec]).
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_INVALID_UGRPENTRY: [chars]: service "[chars]" is not defined.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_MISSINGOPTION: [chars]: option [chars]->[chars] missing from service definition for service "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND: [chars]: service "[chars]" is MTS unaware and cannot have handshake dependencies.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_NORESTART: [chars]: option [chars]->[chars] cannot be set without setting option [chars]->[chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_NOTCONFIG: [chars]: [chars] implemented only for service config.
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error 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't 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.
Error 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't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_REP_UGRPENTRY: [chars]: service "[chars]" is used in more than one upgrade group. First use in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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't 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.
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS: [chars]: too many dependencies ([dec]) for service "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_UGRPDUPLICATEDNAME: [chars]: upgrade group name "[chars]" already used in [chars].
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error Message SYSMGR-2-PARSEERR_UGRPNAMEREDEFINED: [chars]: the upgrade group is already called "[chars]".
Explanation The system image contains an inconsistent list of services. The initialization of the system can't 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.
Error 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.
Error Message SYSMGR-2-PATCH_REPO_STORE_FAILED: Not enough space to store patch repo in standby bootflash
Explanation Failed to store patch repo in standby bootflash
Recommended Action Please free up few 100s mb in standby bootflash to store patch repo OIR bootflash and insert bootflash with needed space and then reload standby from active
Error Message SYSMGR-2-PATCH_REPO_STORE_SYNC_FAILED: Feature RPMs out of sync, reloading standby
Explanation Failed to sync rpm repo during HA
Recommended Action Feature Rpm causing rpmstore inconsistency Cleanup .rpmstore from active if standby continously reloads
Error 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.
Error 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.
Error 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 'system system internal pss kernel memstats'. If this message continues to persist, please contact TAC.
Error Message SYSMGR-2-REDSTATE_GETFAILED: Failed to request redundancy state: [chars] (error-id [hex]).
Explanation The local supervisor is unable to get the redundancy state.
Recommended Action 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.
Error Message SYSMGR-2-REDSTATE_SETFAILED: Failed to set redundancy state: ret_val ([dec]).
Explanation The local supervisor is unable to get the redundancy state.
Recommended Action 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.
Error Message SYSMGR-2-REDUNDANCY_CHANNEL_FAILURE: Remote sup will be rebooted since its coming up as active when local sup is still active.
Explanation Remote 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.
Error Message SYSMGR-2-REDUNDANCY_HEARTBEAT_FAILURE: Heartbeat between active and standby on the redundancy channel not working for last [dec] minutes.
Explanation This supervisor is not receiving 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.
Error Message SYSMGR-2-REMOTE_VER_FAIL: Remote version extraction failed.
Explanation Remote version extraction failed. Standby may not be in ha standby state.
Recommended Action Reload Standby with image in bootflash.
Error 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.
Error 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.
Error Message SYSMGR-2-SAVE_RUNTIME_DB_FAILED: Saving of runtime database for fabric switch upgrade failed (error-id [hex]).
Explanation This message indicates that the runtime database could not be saved for the fabric switch upgrade.
Recommended Action 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.
Error Message SYSMGR-2-SBY_RELOAD_CFGCTRL: The cfgctrl process on sby has failed [dec] times, reloading sby sup to recover
Explanation Configuration control has failed multipe times, the standby supervisor will be automatically reloaded so that it can be recovered.
Recommended Action No action is required.
Error Message SYSMGR-2-SERVICE_CRASHED: Service "[chars]" (PID [dec]) hasn't caught signal [dec][chars]
Explanation A service has terminated its execution abnormally. The service might be restarted, depending on the HA policies implemented for the service.
Recommended Action Please use the command 'show process' to verify that the service has been restarted.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up.
Explanation This message is printed if the standby supervisor doesn't 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 standby 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 standby supervisor from a vsh session on the active supervisor, specifying the 'force-dnld' option. Once the standby is online, fix the problem by setting the boot variables appropriately.
Error 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 'init system' to initialize the configuration partition.
Error Message SYSMGR-2-START_SCRIPT_FAILED: Start script (/isan/etc/rc.sysmgr start) failed with return value: ([dec]).
Explanation The initialization of the system could not complete.
Recommended Action 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.
Error 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.
Error 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.
Error Message SYSMGR-2-SWITCHOVER_OVER: Switchover completed.
Explanation The switchover is completed.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-2-SWITCHOVER_THRESHOLD_EXCEEDED: Switchover threshold exceeded ([dec] switchovers happened within [dec] seconds). Powering down all linecards.
Explanation Switchover threshold exceeded
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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'. Collected information in /bootflash/hap_reset_show_tech.gz.
Explanation Supervisor is automatically collecting logs
Recommended Action No action is required.
Error Message SYSMGR-2-SYSMGR_MALLOC_FAIL: [chars]: malloc ([dec] bytes) for [chars] failed [chars]([dec])
Explanation Malloc failed
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-2-VDC_NOT_CLEANEDUP_SRVS: vdc [dec]: [chars]
Explanation
Recommended Action No action is required.
Error Message SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is unexpectedly high at [dec]%.
Explanation System volatile database space is almost full.
Recommended Action Please run the command 'system pss shrink'. If this message continues to persist, please contact TAC.
Error Message SYSMGR-2-WARMSWITCHOVER_START: This supervisor is becoming active.
Explanation A cold switchover has started.
Recommended Action When the other supervisor is back online, use the command 'show system reset-reason' to know what caused the switchover.
Error Message SYSMGR-2-WDT_KGDB: System watchdog kgdb has been [chars] for slot [dec].
Explanation System watchdog kgdb has been [chars]. If the command has been enabled, the system will go into kgdb if there is a watchdog timeout.
Recommended Action No action is required.
Error Message SYSMGR-3-BASIC_TRACE: [chars]: PID [dec] with message [chars].
Explanation
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-3-CFGWRITE_SRVFAILED: Service "[chars]" failed to store its configuration (error-id [hex]).
Explanation A required service has failed to store its 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-3-COPY_CORES_FAILED: Copying cores failed ([dec]).
Explanation Copying cores to the destination failed because of an error specified in the log.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-3-CORE_CLIENT_INIT_FAILED: Core client will not be started due to some internal error.
Explanation Core client will not be started due to some internal error.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-3-CORE_SERVER_INIT_FAILED: Core server will not be started due to some internal error.
Explanation Core server will not be started due to some internal error.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-3-DISCARD_BINCFG_CONVERT_FAILURE: Binary configuration is being discarded for the reasons: < [chars] >
Explanation Binary configuration is being discarded due to conversion failure
Recommended Action No actions required. System will fallback to ASCII configuration
Error Message SYSMGR-3-DISCARD_BINCFG_VERCMP_FAILURE: Binary configuration is being discarded due to version compare failure
Explanation Binary configuration is being dicarded since the version compare failed to decode the versions
Recommended Action No actions required. System will fallback to ASCII configuration
Error Message SYSMGR-3-FAILED_PFM_HANDSHAKE: PFM-handshake from service "[chars]" failed (error-id [hex]).
Explanation The Platform Manager handshake has failed. The system can't proceed with the initialization.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SYSMGR-3-INVALID_BOOT_HANDSHAKE: Boot-scope-handshake received from service "[chars]", that is in scope [dec] (not the boot scope).
Explanation A service is trying to take actions that belong to a different class of services.
Recommended Action 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.
Error Message SYSMGR-3-INVALID_PFM_HANDSHAKE: PFM-handshake received from service "[chars]", that is in scope [dec] (not the boot scope).
Explanation A service is trying to take actions that belong to the Platform Manager service.
Recommended Action 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.
Error Message SYSMGR-3-INVALID_TRANSITION: Transition from state [chars] to state [chars] is not allowed.
Explanation Unexpected transition in the System Manager state machine.
Recommended Action 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.
Error Message SYSMGR-3-INVALID_UUID: Service "[chars]" is configured with UUID [hex], but uses UUID [hex].
Explanation The identity of a service is inconsistent in the image file
Recommended Action 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.
Error 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.
Error Message SYSMGR-3-KILLALLSRVS_FAILURE: Sysmgr rtdb controller timed out while terminating all serivces.
Explanation One or more services did not terminate during upgrade/downgrade.
Recommended Action Please collect show tech ha to find the service that did not terminate.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-3-LC_UPG_ERROR: LC ERROR: [chars]
Explanation Linecard upgrade error 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.
Error 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.
Error Message SYSMGR-3-MODULE_LOCK_FAILED: Failed to lock the local module to avoid reset (error-id [hex]).
Explanation Locking the local module has failed. Reloading the local module can now result in switchover to fail.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-3-OPERATIONAL_MODE_WARM: Operational redundancy mode set to warm (error-id [hex]).
Explanation Operational redundancy mode will be set to warm. [dec] is the error-ID representing the reason.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SYSMGR-3-RTDBCTRL_BUILD_UPG_TBL_FAILED: Failed to prepare upgrade version table during pre-upgrade
Explanation A required sequence in the preupgrade 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.
Error 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.
Error Message SYSMGR-3-RTDBCTRL_SRVTIMEOUT: Service "[chars]" failed to respond back to System Manager in the specified timeout period
Explanation A required service has failed to send a response after receiving a request for the fabric switch upgrade.
Recommended Action 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.
Error 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.
Error 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.
Error Message SYSMGR-3-SERVICE_TERMINATED: Service "[chars]" (PID [dec]) has finished with error code [chars] ([dec]).
Explanation A service has terminated its execution normally. Depending on the value of [dec2] and the HA policies implemented for the service, the service might be restarted automatically.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-3-STANDBY_VDC_RESTART_FAILURE: vdc [dec] on standby failed to restart. error: [chars] ([hex])
Explanation
Recommended Action No action is required.
Error 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 sysmgr has been restarted.
Error 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.
Error Message SYSMGR-3-UNACCEPTABLE_WAIT: Service "[chars]", no response from System Manager after [dec] seconds. Terminating.
Explanation A spawned service couldn't 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.
Error 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.
Error 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.
Error Message SYSMGR-3-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
Error Message SYSMGR-4-BASIC_TRACE_WARNING: [chars]: PID [dec] with message [chars].
Explanation
Recommended Action No action is required.
Error Message SYSMGR-4-CFGWRITE_PARTIALFORCED: Some services are missing; partial configuration write forced.
Explanation The system is not fully operational, but a configuration copy has been forced. The services that are not running won't save their configuration, and the next time they will restart with a default configuration.
Recommended Action Use the 'show process' command to find out which required services are not running.
Error Message SYSMGR-4-DISCARD_BINCFG_DOWNGRADE_VERSIONID: Binary configuration is being discarded, because the configuration was generatred previously by an image with higher version identfier
Explanation Binary configuration is being discarded, because the configuration was generatred previously by an image with higher version identfier
Recommended Action No actions required. System will fallback to ASCII configuration
Error Message SYSMGR-4-DISCARD_BINCFG_HIGH_TRAINSTAMP: Binary configuration is being discarded, because the configuration was generatred previously by an image having higher trainstamp
Explanation Binary configuration is being discarded, because the configuration was generatred previously by an image having higher trainstamp
Recommended Action No actions required. System will fallback to ASCII configuration
Error Message SYSMGR-4-DISCARD_BINCFG_SRG_INCOMPATIBLE: Binary configuration is being discarded due to incompatibility with running version
Explanation Binary configuration is being dicarded due to incompatibility with running version
Recommended Action No actions required. System will fallback to ASCII configuration
Error Message SYSMGR-4-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.
Error Message SYSMGR-4-ON_DEMAND_STOP_UID_KNOWN: On-demand service "[chars]" stopped by uid ([dec]).
Explanation The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.
Recommended Action No action is required.
Error Message SYSMGR-4-ON_DEMAND_STOP: On-demand service "[chars]" stopped.
Explanation The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-4-PARSEWARN_RESTART_CNT_TOO_BIG: Service "[chars]": [chars] restart count of [dec] too big, needs to be set to [dec].
Explanation This 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-4-SYSMGR_PATCH_START_SERVICE: vdc [dec]: Service [chars] has restarted with pid [dec] as part of patch operation
Explanation Service started for patching
Recommended Action No action is required.
Error Message SYSMGR-4-SYSMGR_PATCH_STOP_SERVICE: vdc [dec]: Service [chars] with pid [dec] has exited as part of patch operation
Explanation Service exited for patching
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-5-CFGERASE_DONE: Configuration erase successful.
Explanation The requested configuration erase has completed successfully.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SYSMGR-5-CFGSNAPSHOT_DONE: Configuration snapshot successful.
Explanation The requested configuration snapshot has completed successfully.
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-5-CFGWRITE_DONE: Configuration copy successful.
Explanation The requested configuration copy has completed successfully.
Recommended Action No action is required.
Error Message SYSMGR-5-CFGWRITE_STARTED: Configuration copy started (PID [dec]).
Explanation On the active supervisor, this message indicates that the system has started to service a 'copy running-config startup-config' 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.
Error 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.
Error 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.
Error Message SYSMGR-5-FSM_STATE_TRANS: System Manager NESTED state transition from [chars] to [chars].
Explanation
Recommended Action No action is required.
Error 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.
Error 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.
Error Message SYSMGR-5-ISSU_BEGIN_STARTED: Notifying services of ISSU (PID [dec]).
Explanation This message indicates that the system has started notifying services for the ISSU. Services can block the upgrade at this point.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-5-PARTIAL_CFGWRITE_DONE: Partial configuration copy successful.
Explanation The requested configuration copy has completed successfully.
Recommended Action No action is required.
Error Message SYSMGR-5-PARTIAL_CFGWRITE_STARTED: Partial configuration copy started by UUID [hex] (PID [dec]).
Explanation This message is printed only on active supervisor, and indicates that service with mentioned UUID has requested a partial write mem. [dec] is the Process-ID of the process servicing the request.
Recommended Action No action is required.
Error Message SYSMGR-5-RECOVERY_FAILED: Stateful recovery failed, system manager will now start stateless.
Explanation Stateful recovery failed, system manager will now restart system and start stateless.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-6-HANDSHAKE_VERIFYING_DONE: Handshake verification done from service "[chars]".
Explanation
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-6-RLIMIT_INFO: rlimit of service "[chars]"([dec]) = %llu
Explanation
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-6-STATE_CHANGED: System Manager state changed from [chars] to [chars] for vdc [dec].
Explanation
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-6-SUPERSTATE_CHANGED: System Manager super state changed from [chars] to [chars] for vdc [dec].
Explanation
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-7-CFGWRITE_UNEXPECTEDRSP: Discarding unexpected response from service "[chars]".
Explanation
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-7-ND_UPGD_RECOVERY_SRVSUCCEEDED: Service "[chars]" recovered its state during non-disruptive upgrade.
Explanation
Recommended Action No action is required.
Error 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.
Error Message SYSMGR-7-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.
Error Message SYSMGR-7-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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message SYSMGR-7-UNKNOWNPID: Opcode [dec] received from [chars] with unknown PID [dec]. Discarding.
Explanation The System Manager has received a message from an unknown process. [chars] is the source of the message. This message is for debugging purposes only.
Recommended Action No action is required.
Error Message SYSMGR-7-UNKNOWNUUID: Opcode [dec] received from [chars] with unknown UUID [dec]. Discarding.
Explanation The System Manager has received an unrecognized message from the specified UUID. [chars] is the source of the message. This message is for debugging purposes only.
Recommended Action No action is required.
This section contains the TACACS messages.
Error 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.
Error Message TACACS-3-TACACS_ERROR_MESSAGE: [chars]
Explanation TACACS+ Error Message
Recommended Action No action is required.
Error Message TACACS-4-TACACS_WARNING: [chars]
Explanation TACACS+ warning
Recommended Action No action is required.
Error Message TACACS-5-TACACS_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Tacacs+ server monitor status change
Recommended Action No action is required.
Error Message TACACS-5-TACACS_NOTIFICATION: [chars]
Explanation TACACS+ notification
Recommended Action No action is required.
Error 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.
Error Message TACACS-6-TACACS_ACCOUNTING_MESSAGE: [chars]
Explanation Accounting Message
Recommended Action No action is required.
Error Message TACACS-6-TACACS_MESSAGE: [chars]
Explanation TACACS+ Message
Recommended Action No action is required.
This section contains the TAHUSD messages.
Error Message TAHUSD-2-TAHUSD_SYSLOG_PFCWD_QUEUE_RESTORED: [chars]
Explanation NO DROP Queue Restored due to PFC WatchDog timer expiring message
Recommended Action No action is required.
Error Message TAHUSD-2-TAHUSD_SYSLOG_PFCWD_QUEUE_SHUTDOWN: [chars]
Explanation Queue Shutdown due to PFC WatchDog timer expiring as a result of NO DROP Queue stuck message
Recommended Action No action is required.
Error Message TAHUSD-3-TAHUSD_SPEED_MSG: [chars]
Explanation TAHUSD Error: same port speed must be set within a 4-port group
Recommended Action No action is required.
Error Message TAHUSD-6-TAHUSD_L2_LEARN_DISABLE_MTM_FLOW_CTRL: [chars]
Explanation MAC Learning Disabled due to MTM flow control
Recommended Action No action is required.
Error Message TAHUSD-6-TAHUSD_SYSLOG_INFO: [chars]
Explanation Tahoe log message
Recommended Action No action is required.
This section contains the TBIRD_CMN_USD messages.
Error Message TBIRD_CMN_USD-6-TBIRD_CMN_DEBUG_MSG: [chars]
Explanation Debug log message
Recommended Action No action is required.
This section contains the TCAP messages.
Error 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.
Error 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.
Error 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.
This section contains the TELEMETRY messages.
Error Message TELEMETRY-1-ALERT: [chars]
Explanation Alert message
Recommended Action No special action is required.
Error Message TELEMETRY-2-CRITICAL: [chars]
Explanation Critical message
Recommended Action No special action is required.
Error Message TELEMETRY-3-ERROR: [chars]
Explanation Error message
Recommended Action No special action is required.
Error Message TELEMETRY-3-INFRA_SYSERR: Error returned from [chars]: errno=[dec] ([chars])
Explanation Telemetry invoke an infra API which returned an error
Recommended Action No special action is required.
Error Message TELEMETRY-3-INITERR: TM initialized [chars] failed
Explanation Initialization failures condition
Recommended Action No special action is required.
Error Message TELEMETRY-3-MALLOC_FAILED: Memory allocation failed for [chars]
Explanation Telemetry could not allocate memory
Recommended Action No special action is required.
Error Message TELEMETRY-3-MTS_DROP: Error returned from mts_drop(): [chars]
Explanation An MTS API returned error when Telemetry tried to drop a message
Recommended Action Keep running, do nothing special
Error Message TELEMETRY-3-MTS_HANDLER_ERR: Unable to handle mts[[dec]] message [chars]: [chars]
Explanation An MTS API handler returned error when Telemetry tried to process message
Recommended Action Keep running, do nothing special
Error Message TELEMETRY-3-TM_ERROR: Telemetry Error:[chars]. errno=[dec] ([chars])
Explanation Telemetry API returned an error
Recommended Action No special action is required.
Error Message TELEMETRY-3-TM_SUBSCRIBE_ERR: Event subscription for sensor path [chars] failed. Error: [chars].
Explanation Telemetry Event subscription failed
Recommended Action No special action is required.
Error Message TELEMETRY-3-TM_SUB_UNSUPPORTED: Event subscription is not supported for [chars] sensor-group %l u
Explanation Telemetry Event subscription not supported
Recommended Action No special action is required.
Error Message TELEMETRY-3-TRANSPORT_DISABLED: Disabling [chars] transport for [chars] after [dec] consecutive errors.
Explanation Telemetry transport is disabled due to consecutive errors.
Recommended Action Make sure receiver is up and running and reconfigure destination group.
Error Message TELEMETRY-4-COLLECTOR_WARNING: [chars]. (While collecting: [chars])
Explanation Telemetry data collector warning message.
Recommended Action No special action is required.
Error Message TELEMETRY-4-DISABLE_DONE: [chars]
Explanation Telemetry is now disabled. You can re-enable the feature if needed.
Recommended Action No special action is required.
Error Message TELEMETRY-4-DISABLING_FEATURE: [chars]
Explanation Telemetry is being disabled. Please wait until process terminates.
Recommended Action Don't re-enable telemetry until the process exits.
Error Message TELEMETRY-4-DME_GET_ERR: [chars] data retrieval failed for path:[chars]
Explanation DME Data collection failed for DN path
Recommended Action Keep running, do nothing special
Error Message TELEMETRY-4-QUEUE_FULL: [chars] queue is full. Consider scaling down configuration or check if receiver is running.
Explanation Telemetry is streaming out too much data.
Recommended Action Consider scaling down Telemetry configuration.
Error Message TELEMETRY-4-TRANSPORT_RECONFIGURE: [chars]
Explanation A configuration change requires reconfiguring destination groups to take effect.
Recommended Action Reconfigure telemetry destination groups.
Error Message TELEMETRY-4-WARNING: [chars]
Explanation Warning message
Recommended Action No special action is required.
Error Message TELEMETRY-5-NOTICE: [chars]
Explanation Normal bug significant condition
Recommended Action No special action is required.
Error Message TELEMETRY-6-INFO: [chars]
Explanation Informational message
Recommended Action No special action is required.
Error Message TELEMETRY-6-SYSLOG_UNKNOWN: Syslog message id [dec] is not implemented
Explanation Telemetry syslog message has not been implemented
Recommended Action No special action is required.
Error Message TELEMETRY-7-DEBUG: [chars]
Explanation Debug message
Recommended Action No special action is required.
This section contains the TTYD messages.
Error Message TTYD-2-TTYD_ERROR: TTYD Error [chars]
Explanation Critical TTY daemon error.
Recommended Action No action is required.
Error Message TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars]
Explanation TTY daemon message error.
Recommended Action No action is required.
Error Message TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars]
Explanation TTY daemon Debug Facility failed.
Recommended Action No action is required.
Error Message TTYD-3-TTYD_MISC_ERROR: Error [chars] with error [chars]([hex])
Explanation TTY daemon errors.
Recommended Action No action is required.
Error Message TTYD-4-TTYD_WARN: TTYD Warning [chars]
Explanation TTY daemon warning.
Recommended Action No action is required.
Error Message TTYD-6-TTYD_MISC: TTYD [chars]
Explanation The tty daemon miscellaneous message.
Recommended Action No action is required.
Error Message TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars]
Explanation Failed to store configuration for TTY service.
Recommended Action No action is required.
This section contains the TUNNEL messages.
Error 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"
Error 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"
Error Message TUNNEL-2-TUNNEL_INTF_STATE_UPDATE: Interface [chars] is down reason ([chars])
Explanation Interface [char] is down reason [char]
Recommended Action No action is required.
Error Message TUNNEL-2-UNSUPPORTED_TUNNEL_TYPE: Failed to create interface [chars] due to unsupported-tunnel type
Explanation Current tunnel type is not supported in this release
Recommended Action No action is required.
Error Message TUNNEL-3-HW_PROGRAMMING_FAILED: for [chars], reason [chars]
Explanation Hardware programming failed for tunnel [num] interface
Recommended Action Try 'shutdown' and 'no shutdown' under tunnel interface submode after sometime. if still tunnel interface doesn't come up capture show tech-support tunnel to identify the issue
Error 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
Error 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.
Error 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
Error Message TUNNEL-4-TM_MTU_PROGRAMMING: Programming [chars] mtu [dec]...
Explanation Programming [chars] mtu [int]
Recommended Action No action is required.
Error Message TUNNEL-5-IF_CLEAR_COUNTER: Interface [chars] counters is cleared
Explanation Interface [char] counters is cleared
Recommended Action No action is required.
Error Message TUNNEL-5-IF_CREATED: Interface [chars] is created
Explanation Interface [char] is created
Recommended Action No action is required.
Error 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.
Error Message TUNNEL-5-IF_DELETED: Interface [chars] is deleted
Explanation Interface [char] is deleted
Recommended Action No action is required.
Error 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.
Error 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.
Error Message TUNNEL-5-TM_DISABLED: Tunnel Disabled
Explanation Tunnel Service Disabled
Recommended Action No action is required.
Error Message TUNNEL-5-TM_ENABLED: Tunnel Enabled
Explanation Tunnel Service Enabled
Recommended Action No action is required.
Error Message TUNNEL-7-TM_INFO: [chars]
Explanation Tunnel Service info
Recommended Action No action is required.
This section contains the U2RIB messages.
Error Message U2RIB-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode = [dec], Error code = [hex]
Explanation U2RIB encountered an error in processing an MTS message. The error and message are specified in the error message
Recommended Action No action is required.
Error Message U2RIB-2-U2RIB_INIT: U2RIB initialization of [chars] [chars]
Explanation U2RIB 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.
Error Message U2RIB-3-U2RIB_LBL_SELECT_ERROR: Error in predicting the load-balance selection, error code = [hex], [chars]
Explanation Error in processing or communicating with hardware
Recommended Action No action is required.
Error Message U2RIB-3-U2RIB_LD_BLNCE_ERROR: Error in config. lb parameters using the DCEFIB Library, error code = [hex], [chars]
Explanation Error while communicating with the dcefib library
Recommended Action No action is required.
Error Message U2RIB-5-U2RIB_DISABLED: U2RIB Disabled
Explanation U2RIB Service Disabled
Recommended Action No action is required.
Error Message U2RIB-5-U2RIB_ENABLED: U2RIB Enabled
Explanation U2RIB Service enabled
Recommended Action No action is required.
Error Message U2RIB-6-STATE_CREATED: Internal state created [chars]
Explanation U2RIB has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
This section contains the UDLD messages.
Error Message UDLD-3-IDB_ERROR: UDLD error handling [chars] interface: [chars]
Explanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Explanation Failed to send a message
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_GWRAP_COUNT: UDLD gwrap count is %lu, please log a 'show tech udld' for detail info.
Explanation UDLD gwrap count reached high level, show tech udld is needed to debug it.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_NEIGHBOR_MISMATCH: UDLD neighbor mismatch detected, exp: [chars], rec [chars]. Please collect debug info using: http://wikicentral.cisco.com/confluence/display/KGP/UDLD+debug
Explanation An interface will be disabled because UDLD protocol detected a nieghbor mismatch condition on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_PORT_DISABLED: Interface [chars], link error detected: [chars]. Please collect debug info using: http://wikicentral.cisco.com/confluence/display/KGP/UDLD+debug
Explanation An interface was disabled because UDLD protocol detected the cause on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_PORT_RESET: UDLD reset interface [chars]
Explanation A port which had been disabled for UDLD has been reset.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_SFP_TYPE_CHANGED: User changed SFP type on [chars] from [chars] to [chars], default udld port configuration was applied, 'copy running-config startup-config' recommended
Explanation SFP type was changed on this interface, all user modified configuration will be reverted back to the default config.
Recommended Action No action is required.
Error Message UDLD-5-UDLD_AGGRESSIVE: UDLD Aggressive
Explanation UDLD Service Aggressive
Recommended Action No action is required.
Error Message UDLD-5-UDLD_DISABLED: UDLD Disabled
Explanation UDLD Service Disabled
Recommended Action No action is required.
Error Message UDLD-5-UDLD_ENABLED: UDLD Enabled
Explanation UDLD Service Enabled
Recommended Action No action is required.
This section contains the UFDM messages.
Error Message UFDM-2-FIB_ROUTE_UPDATE_ERR: Route update error from slot [dec] FIB
Explanation FIB returned route update error. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action No action is required.
Error Message UFDM-2-INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support fowarding l3 unicast... command
Explanation UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv4_ADJ_CONSISTENCY_CHECKER_FAIL: FIB IPv4 adjacency consistency checker FAILED on slot [chars]
Explanation FIB Ipv4 adjacency consistency checker Failed. Adjacency database is inconsistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv4_ADJ_CONSISTENCY_CHECKER_PASS: FIB IPv4 adjacency consistency checker PASSED on slot [chars]
Explanation FIB Ipv4 adjacency consistency checker passed. Adjacency database is consistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv4_CONSISTENCY_CHECKER_TIMEDOUT: FIB IPv4 consistency checker timedout on slot [chars]
Explanation FIB Ipv4 route/adjacency consistency checker couldnot complete
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv4_ROUTE_CONSISTENCY_CHECKER_FAIL: FIB IPv4 consistency checker FAILED on slot [chars]
Explanation FIB Ipv4 route consistency checker Failed. Route database is consistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv4_ROUTE_CONSISTENCY_CHECKER_PASS: FIB IPv4 route consistency checker PASSED on slot [chars]
Explanation FIB Ipv4 route consistency checker Passed. Route database is consistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv6_ADJ_CONSISTENCY_CHECKER_FAIL: FIB IPv6 consistency checker FAILED on slot [chars]
Explanation FIB Ipv6 adjacency consistency checker failed. Adjacency database is inconsistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv6_ADJ_CONSISTENCY_CHECKER_PASS: FIB IPv6 consistency checker PASSED on slot [chars]
Explanation FIB Ipv6 adjacency consistency checker passed. Adjacency database is consistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv6_CONSISTENCY_CHECKER_TIMEDOUT: FIB IPv6 consistency checker timed out on slot [chars]
Explanation FIB Ipv6 route/adjacency consistency checker couldnt complete
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv6_ROUTE_CONSISTENCY_CHECKER_FAIL: FIB IPv6 route consistency checker FAILED on slot [chars]
Explanation FIB Ipv6 route consistency checker failed. Route database is inconsistent with hardware
Recommended Action No action is required.
Error Message UFDM-3-FIB_IPv6_ROUTE_CONSISTENCY_CHECKER_PASS: FIB IPv6 route consistency checker PASSED on slot [chars]
Explanation FIB Ipv6 route consistency checker didnot detect. Route software database is consistent with hardware
Recommended Action No action is required.
Error Message UFDM-5-DNLD_TIMEDOUT: Download timer expired: [chars]
Explanation UFDM download timer expired. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action No action is required.
Error Message UFDM-6-FIB_IPv4_CONSISTENCY_CHECKER_START: FIB IPv4 consistency checker started on slot [chars]
Explanation FIB Ipv4 route/adjacency consistency checker has been started
Recommended Action No action is required.
Error Message UFDM-6-FIB_IPv4_CONSISTENCY_CHECKER_STOP: FIB IPv4 consistency checker stopped on slot [chars]
Explanation FIB Ipv4 route/adjacency consistency checker has been stopped
Recommended Action No action is required.
Error Message UFDM-6-FIB_IPv6_CONSISTENCY_CHECKER_START: FIB IPv6 consistency checker started on slot [chars]
Explanation FIB Ipv6 route/adjacency consistency checker has been started
Recommended Action No action is required.
Error Message UFDM-6-FIB_IPv6_CONSISTENCY_CHECKER_STOP: FIB IPv6 consistency checker stopped on slot [chars]
Explanation FIB Ipv6 route/adjacency consistency checker has been stopped
Recommended Action No action is required.
This section contains the USBHSD messages.
Error Message USBHSD-1-MANUAL_FORMAT: logflash needs to be formatted
Explanation Logflash is not accessible; use \format logflash:\ to format it
Recommended Action No action is required.
Error Message USBHSD-2-AUTO_FORMAT: logflash auto-format [chars]
Explanation Logflash auto-format event
Recommended Action No action is required.
Error Message USBHSD-2-DISK_BUSY_FAILED: Cannot umount [chars],
Explanation The specified disk interface is in use it can not be un mounted, The user may experience file system correuption
Recommended Action Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again
Error Message USBHSD-2-DISK_FSCK_FAIL: file system check returned error on slot [dec]
Explanation Flash fliesyetm may be corrupted, the flash was taken while it was being accessed
Recommended Action Reformat the extarnal flash
Error Message USBHSD-2-DISK_MOUNT_FAIL: disk mount unsuccessful on [chars]
Explanation Unknown flash filesystem or not cleanly un mounted
Recommended Action Use vfat flash only and make sure external slot is not being accessed then re-insert flash
Error Message USBHSD-2-DISK_RESCAN_FAIL: disk rescan unsuccessful on [chars]
Explanation Flash fliesyetm was not cleanly un mounted
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Error Message USBHSD-2-DISK_UMOUNT_FAIL: disk umount unsuccessful for [chars]
Explanation Flash fliesyetm is busy the system could noy un-mount it
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Error Message USBHSD-2-FORK: fork failed ([chars] process)
Explanation The flash daemon failed to fork
Recommended Action No action is required.
Error Message USBHSD-2-INTERNAL_ERROR: Internal Error [dec]
Explanation The flash daemon interface returns error
Recommended Action Restart the idehsd deamon
Error Message USBHSD-2-MOUNT: [chars] online
Explanation Flash daemon mounting slot
Recommended Action No action is required.
Error Message USBHSD-2-UMOUNT: [chars] offline
Explanation Flash daemon un mounting slot
Recommended Action No action is required.
Error Message USBHSD-2-USB_SWAP: USB insertion or removal detected
Explanation USB swap event
Recommended Action No action is required.
Error Message USBHSD-3-DEVICEOPEN_FAILED: device open failed. Component [chars]
Explanation The flash daemon device open failed The failure is due to the sub-component [chars]
Recommended Action No action is required.
Error Message USBHSD-5-DISK_SWAP: [chars] [chars]
Explanation Compach flash swap event
Recommended Action No action is required.
Error Message USBHSD-6-DISK_BUSY: trying to un mount disk [chars]
Explanation Flash daemon trying to umount busy slot
Recommended Action No action is required.
Error Message USBHSD-6-DISK_EVENT: slot [dec] [chars]
Explanation Flash daemon found a disk hotswap handler event
Recommended Action No action is required.
Error Message USBHSD-6-IOCTL: ioctl: [chars] returns [dec]
Explanation Flash daemon trying to umount busy slot
Recommended Action No action is required.
Error Message USBHSD-6-STARTING: deamon started
Explanation The compact flash swap daemon successfully started
Recommended Action No action is required.
Error Message USBHSD-6-USBHSD_INFO: [chars]
Explanation Flash daemon informational message
Recommended Action No action is required.
Error Message USBHSD-7-USBHSD_TRACE: [chars]() [chars]:[dec] disk=[dec]
Explanation Flash daemon debug message to trace code path
Recommended Action No action is required.
This section contains the USDBA messages.
Error Message USDBA-6-USDBA_DEBUG_MSG: [chars]
Explanation Debug log message
Recommended Action No action is required.
This section contains the VDC_MGR messages.
Error Message VDC_MGR-2-VDC_CRITICAL: vdc_mgr has hit a critical error: [chars]
Explanation Vdc_mgr has hit a critical error
Recommended Action A critical error has been hit within vdc_mgr. Please check show vdc to determine the state of the vdcs
Error Message VDC_MGR-2-VDC_LIC_WARN_EXP: WARNING License for vdcs is about to expire! VDCs will be deleted if license is allowed to expire
Explanation VDC license is close to expire
Recommended Action Please contact your sales representative to obtain a license
Error Message VDC_MGR-2-VDC_LIC_WARN: Service using grace period will be shutdown in [dec] day(s)
Explanation The license for vdcs is not installed and currently running in the grace period
Recommended Action Vdcs will continue to work within the grace period, but obtaining a license is reccomended
Error Message VDC_MGR-2-VDC_OFFLINE: vdc [dec] is now offline
Explanation The vdc has been shut down. Either it has been deleted or has just completed ungraceful cleanup
Recommended Action If the vdc was deleted, no action is necessary. Otherwise vdc_mgr may attempt to recreate it according to the ha-policy that has been set
Error Message VDC_MGR-2-VDC_ONLINE: vdc [dec] has come online
Explanation Vdc_mgr has finished creating a vdc and it is ready to use
Recommended Action No action is required.
Error Message VDC_MGR-2-VDC_UNALLOCATED: Module [dec] is unsupported by the current vdc and some of its ports have been placed in the unallocated pool.
Explanation The module is of a type unsupported by the current vdc. You can see port membership by \'show vdc membership\' and check the current vdc\'s configuration via \'show vdc\'
Recommended Action Allocate interfaces to a vdc that supports this module type or change the current vdc to support this module type via the \'limit-resource module-type\' command
Error Message VDC_MGR-2-VDC_UNGRACEFUL: vdc_mgr: Ungraceful cleanup request recieved for vdc [dec], restart count for this vdc is [dec] restarts within the last 5 minutes
Explanation Vdc_mgr has begun ungraceful cleanup for a vdc
Recommended Action There has been a failure within the vdc and vdc_mgr has begun the cleanup process. Use show vdc to determine its state
Error Message VDC_MGR-3-VDC_ERROR: vdc_mgr: [chars]
Explanation Vdc_mgr has recieved bad data but will try to continue
Recommended Action Vdc_mgr will attempt to correct the error at hand
Error Message VDC_MGR-5-VDC_ADMIN_VDC_CHANGE: vdc_mgr: Admin-vdc mode has been [chars]
Explanation The admin-vdc mode has been changed
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_DELETED: vdc_mgr: vdc [dec] has been deleted
Explanation The vdc with id listed no longer exists
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_FCOE_VLAN_ADD: vdc_mgr: vlans [chars] has been shared to this vdc
Explanation Vlans have been shared to this fcoe vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_FCOE_VLAN_DELETE: vdc_mgr: vlans [chars] has been unshared from this vdc
Explanation Vlans have been unshared from this fcoe vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_FEATURESET_ALLOW: vdc_mgr: Feature-set [chars] can now be used in this vdc
Explanation Allowed feature-set config has changed
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_FEATURESET_DISALLOW: vdc_mgr: Feature-set [chars] is now disallowed in this vdc
Explanation Allowed feature-set config has changed
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc [dec] hostname changed to [chars]
Explanation Host name for a vdc has changed.
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_MEMBERSHIP_ADD: vdc_mgr: Interface [chars] has been added to this vdc
Explanation A new interface has been added to this vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_MEMBERSHIP_DELETE: vdc_mgr: Interface [chars] has been removed from this vdc
Explanation A new interface has been removed from this vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to [chars]
Explanation This vdc has been changed to support only the the type of modules listed
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_SH_MEMBERSHIP_ADD: vdc_mgr: Interface [chars] has been shared to this vdc
Explanation A new interface has been shared to this vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_SH_MEMBERSHIP_DELETE: vdc_mgr: Interface [chars] has been unshared from this vdc
Explanation A new interface has been unshared from this vdc
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_STATE_CHANGE: vdc [dec] state changed to [chars]
Explanation A vdc state change has happened. This is most likely due to a configuration change.
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_SWMODULETYPE: vdc_mgr: System Module type changed to [chars]
Explanation This switch has been changed to support only the the type of modules listed
Recommended Action No action is required.
This section contains the VLAN_MGR messages.
Error Message VLAN_MGR-2-CRITICAL_MSG: [chars]
Explanation VLAN Manager Critical Message
Recommended Action No action is required.
Error Message VLAN_MGR-2-FABRIC_DYNAMIC_CORE_VLAN_RANGE_REMOVED: Fabric dynamic and core VLAN ranges removed. Please delete VLANs [chars] in the ranges
Explanation VLAN Manager Core VLAN Range Removal Message
Recommended Action No action is required.
Error Message VLAN_MGR-2-VLAN_DELETE_FAILED_RSN_BD_EXIST: VTP request to delete VLAN(s) [chars] could not be processed. Bridge Domains exist for VLANs [chars]
Explanation VLAN delete failed since Bridge Domains Exist
Recommended Action No action is required.
Error Message VLAN_MGR-3-ERROR_MSG: [chars]
Explanation VLAN manager error
Recommended Action No action is required.
Error Message VLAN_MGR-4-WARN_MSG: [chars]
Explanation VLAN manager warning
Recommended Action No action is required.
Error Message VLAN_MGR-5-NOTIF_MSG: [chars]
Explanation VLAN Manager Notification Message
Recommended Action No action is required.
Error Message VLAN_MGR-5-RESERVED_VLAN_RANGE_CHANGED: New Reserved VLAN Range Configured From VLAN [dec] to VLAN [dec]
Explanation VLAN Manager Reserved VLAN Reconfiguration Message
Recommended Action No action is required.
Error Message VLAN_MGR-6-INFO_MSG: [chars]
Explanation VLAN manager info
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_CREATED: VLAN [dec], created
Explanation VLAN created
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART: VLAN Manager statefull restart
Explanation VLAN Manager statefull restart
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART: VLAN Manager stateless restart
Explanation VLAN Manager stateless restart
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_OPER_STATUS_CHG: VLAN [dec], status changed to [chars]
Explanation VLAN operational state change
Recommended Action No action is required.
This section contains the VMAN messages.
Error Message VMAN-2-ACTIVATION_STATE: [chars] '[chars]' [chars] [chars]
Explanation The activation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
Error Message VMAN-2-ALLOC_VIRT_INST_RCS: Virtual Service [chars]
Explanation A memory allocation request failed to allocate a data structure required to activate the virtual service.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-COMMIT_VIRT_INST_RCS: Virtual Service [chars]
Explanation The request to commit the resources required by the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-CPUSHARES_LIMIT: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-CPUTUNES_INTERNAL_ERROR: Virtual Service [chars]
Explanation Virt-manager and its associated infrastructure experienced an internal error.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-CPUTUNES_SHARES_LIMIT: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-CREATE_VIRT_INST_ENTRY: Virtual Service [chars]
Explanation The request to create a DB entry for the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-DEACT_FOR_ISSU: [chars] Max ([dec]s)
Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and vman will automatically restart the VMs.
Error Message VMAN-2-DEFER_VIRT_INST_PROC: Virtual Service [chars]
Explanation The final activation processing failed to successfully defer.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-DISK_IMAGE_PATH: Virtual Service [chars]
Explanation The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-FIND_VIRT_INST_ENTRY: Failed to find virtual service with id [dec] in the Virt-manager DB
Explanation The virtual service with the ID named could not be located in the Virt-manager DB.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-GENERAL_FAILURE: Virtual Service [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-2-GUESTSHELL_AUTHORIZED_KEYS_TRUNCATED_WRITE_FAILURE: The Guestshell authorized_keys file was truncated due to failing to write new public key. Any added public key have been lost.
Explanation Each time the Guestshell is activated a new public ssh key is generated and replaces the previous public key in the Guestshell's .ssh/authorized_keys file.; action Check if the Guestshell's root file system is full by issuing 'show virtual-service utilization name guestshell+' command. If 100% capacity the root file system can be resized by issuing 'guestshell resize rootfs command'
Recommended Action The user should follow the guidance provided by the syslog by running the suggested command.
Error Message VMAN-2-GUESTSHELL_ENABLED_ON_NEXTBOOT: The guest shell has been enabled to install and activate upon next bootup. You may use '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtual service has been enabled to install and activate upon next bootup.
Recommended Action The user may use or remove the guest shell from installing and activating on next bootup with the command specified.
Error Message VMAN-2-GUESTSHELL_ENABLED: The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtual service has been enabled (which is done by default).
Recommended Action The user may use or remove the guest shell with the commands specified.
Error Message VMAN-2-HA_STATE: [chars] [chars] [chars] [chars]
Explanation VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
Error Message VMAN-2-HA_SWITCHOVER_STATE: [chars] [chars] [chars] [chars]
Explanation VMAN HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
Error Message VMAN-2-HA_SYNC_ERR: [chars] '[chars]' [chars]
Explanation The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP.
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-HA_SYNC_THREAD_STATE: HA remote sychronize thread has failed and exited.
Explanation VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same.
Error Message VMAN-2-INCONSISTENT_CPUTUNES_CONFIG: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting invalid CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INCONSISTENT_MEM_CONFIG: Virtual Service [chars]
Explanation The virtual service machine definition file is inconsistent in the specification of required memory via the
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INSERT_VIRT_INST_ENTRY: Virtual Service [chars]
Explanation Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INSTALL_FAILURE: Virtual Service [chars]
Explanation The installation of the virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INSTALL_LOG: [chars] [chars] [chars] [chars]
Explanation The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
Error Message VMAN-2-INSTALL_MEDIA_RETRY: VMAN, VM install media still unavailable.[chars]
Explanation The install media was not detected. Waiting for udev to complete install media(harddisk) detection.
Recommended Action After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.
Error Message VMAN-2-INSTALL_STATE: [chars] '[chars]'[chars] [chars]
Explanation The installation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
Error Message VMAN-2-INVALID_ACT_MSG: Virtual Service [chars]
Explanation The virtual service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INVALID_DEACT_MSG: Failed to process virtual service deactivate message
Explanation The virtual service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-INVALID_PACKAGE: Virtual Service [chars]
Explanation The package definition file for the named virtual service has failed to be validated and the virtual service will not run
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer.
Error Message VMAN-2-INVALID_UNPROV_MSG: Failed to process virtual service unprovision message
Explanation The virtual service unprovision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-MACHINE_TYPE_NOT_SUPPORTED: Virtual Service [chars]
Explanation The virtual service cannot be activated as the machine type specified is not supported; action Enable the support for the machine type and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-MACH_PARSE_FAILURE: Virtual Service [chars]
Explanation The named virtual service has an invalid parameter specified in the .xml file inside the .ova package
Recommended Action Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it
Error Message VMAN-2-MEMORY_LIMIT_WARN: Virtual service ([chars])[chars] defines [dec] MB of Memory exceeding the maximum [dec] MB.
Explanation The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-MEMORY_LIMIT: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting more memory than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-MORETHANONE_CPUTUNES_CONFIG: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting more than one CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-MOVE_STATE: [chars] '[chars]' [chars] [chars]
Explanation The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
Error Message VMAN-2-NETWORKING_MODEL_DEPRECATED: Virtual service '[chars]' is using the NXOS user-space networking model that is deprecated for containers. When convenient, please [chars]
Explanation Informs the user that the virtual service is using the NXOS user-space networking model that is deprecated for containers.
Recommended Action When convenient, the user should destroy the virtual service and install an updated virtual service package that has the newer kernel stack (kstack) networking model.
Error Message VMAN-2-NETWORK_CONFIG_ERROR: Virtual Service [chars]
Explanation A network configuration error has been detected for the named virtual service.
Recommended Action No action is required
Error Message VMAN-2-PROCESS_PKG_DEF: Virtual Service [chars]
Explanation The virtual service package for the named virtual service has failed to be validated and the virtual service will not run.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-PROC_INT_LIST: Virtual Service [chars]
Explanation The interface list embedded in the activate request for the named virtual service could not be processed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-REMOVE_VIRT_INST_ENTRY: Virtual Service [chars]
Explanation Removing the named virtual service from the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-RESET_FORCE: Virtual Services non-recoverable reset command processed
Explanation A 'virtual service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.
Error Message VMAN-2-RESIZE_OPER_STATE: Virtual service '[chars]' [chars][chars] to '[dec]' [chars]
Explanation VMAN attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
Error Message VMAN-2-RSYNC_STATE: [chars] [chars] [chars] [chars]
Explanation VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same.
Error Message VMAN-2-SEC_ATTR_LABEL_ERROR: A failure to apply security labels has been detected. You may use '[chars]' to capture the failures.
Explanation Informs the user a failure has occurred when labeling the network elements root filesystem. This failure will likely result in a non-deterministic behavior.
Recommended Action The user should follow the guidance provided by the syslog by running the suggested command.
Error Message VMAN-2-SET_VTX_ROMVAR_SPACE: Failed to set ROM monitor variable ENABLE_VTX: No space in table
Explanation Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table.
Recommended Action Verify number of entries in Monitor Variable Table.
Error Message VMAN-2-SET_VTX_ROMVAR_STRING: Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars]
Explanation Failed to set ENABLE_VTX rom monitor variable due to invalid string format.
Recommended Action Verify format of string from error message.
Error Message VMAN-2-START_FAILED: Virtual Service [chars]
Explanation The named virtual service failed to start.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-UNINSTALL_ALL_VMS: All Virtual Services are being uninstalled [chars][chars] [chars]
Explanation All virtual services are being uninstalled by Virt-manager.
Recommended Action Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-manager's logs for the cause of the failure.
Error Message VMAN-2-UPGRADE_LOG: [chars] [chars] [chars] [chars]
Explanation The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
Error Message VMAN-2-VCPU_INVALID: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-VCPU_LIMIT: Virtual Service [chars]
Explanation The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-VIRT_DISK_CAPACITY_HIGH_WATERMARK: Virtual service '[chars]', application '[chars]' disk '[chars]' capacity is at '[dec] percent' utilization. [chars]
Explanation A virtual service filesystem disk device has reached a high watermark in disk utilization.
Recommended Action Connect to your virtual-service and purge/delete any unneeded files, logs, packages etc.
Error Message VMAN-2-VIRT_INST_CRIT: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-2-VIRT_INST_DISK: Virtual Service [chars]
Explanation The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-VIRT_INST_GEN_CORE: Virtual service '[chars]', application '[chars]' has generated a core '[chars].gz'.
Explanation Informs the user that an application within the virtual service has generated a core.
Recommended Action Guest shell generated cores will be located at /cisco/core directory within the guest shell root filesystem. For all virtual services, the core file can be moved to desired location using the 'virtual-service move name
Error Message VMAN-2-VIRT_INST_INTERFACE: Virtual Service [chars]
Explanation The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-VIRT_INST_LOG_UNTHROTTLE: Failed to unthrottle the log for virtual service [chars]
Explanation The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the virt-manager logs and scan them for the cause.
Error Message VMAN-2-VIRT_INST_MEMORY: Virtual Service [chars]
Explanation The virtual service requires physical memory in excess of the free memory available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-2-VIRT_INST_MGMT_INTERFACE: Virtual service [chars] has no management interface defined but it is configured in CLI.
Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service.
Error Message VMAN-2-VIRT_INST_STATE: Virtual Service [chars]
Explanation The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-3-PSS_ERR: Purpose: [chars], URI: [chars], errcode: [dec]
Explanation Persistent Storage Service handling error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-3-PSS_SNAPSHOT_ERR: Source URI: [chars], Destination URI: [chars], errcode: [dec]
Explanation Persistent Storage Service snapshot error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-3-SDWRAP_ERR: Description: [chars], errcode: [dec]
Explanation Debug infrastructure error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Error Message VMAN-3-VIRT_INST_ERR: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-4-HA_SYNC_NEEDED: If using the Guest shell, please use 'guestshell sync' to preserve its content on the standby in case of a supervisor switchover
Explanation Message notifying user that he needs to manually synchronize the Virtual service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell
Recommended Action User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired.
Error Message VMAN-4-PACKAGE_SIGNING_LEVEL_CHANGED: Package signing level changed from allow '[chars]' to allow '[chars]'
Explanation The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode.
Recommended Action Ensure that this setting has been changed as expected by an authorized user.
Error Message VMAN-4-VIRT_INST_WARN: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-4-VIRT_SERV_LIBVIRTD_WARN: VMAN not able to connect to the libvirt daemon after '[dec]' attempts
Explanation VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made.
Recommended Action Collect the logs produced by 'show virt tech'
Error Message VMAN-4-WATCHDOG_TIMER: [chars] '[chars]' [chars] [chars]
Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtual service to determine the cause.
Error Message VMAN-5-AUX: Virtual Service [chars]
Explanation The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required
Error Message VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL: Package '[chars]' for service container '[chars]' is '[chars]', [chars] '[chars]'
Explanation A service container software package with the certificate signing level described is being installed.
Recommended Action Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins.
Error Message VMAN-5-VIRT_DISK_CAPACITY_LOW_WATERMARK: Virtual service '[chars]', application '[chars]' disk '[chars]' capacity is at '[dec] percent' utilization. No action is necessary.
Explanation A virtual service filesystem disk device has reached its low watermark.
Recommended Action No action is necessary.
Error Message VMAN-5-VIRT_INST_NOTICE: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-5-VIRT_INST: LOG FROM VIRTUAL SERVICE [chars]: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-6-VIRT_INST_INFO: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Error Message VMAN-7-VIRT_INST_DEBUG: VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
This section contains the VMM messages.
Error Message VMM-2-VMM_DBG_SEQDELAY_LOG: VDC[dec]: Sending [chars] mts([chars]) request to service [dec] for slot [dec].
Explanation VMM sent request for the sap mentioned
Recommended Action No action is required.
Error Message VMM-2-VMM_SERVICE_ERR: VDC[dec]: Service SAP [chars] for slot [chars] returned error [hex] ([chars]) in [chars] sequence
Explanation Service returned error in the specified sequence
Recommended Action No action is required.
Error Message VMM-2-VMM_TIMEOUT: VDC[dec]: Service SAP [chars] for slot [chars] timed out in [chars] sequence
Explanation Service did not respond in the specified sequence
Recommended Action No action is required.
This section contains the VMTRACKER messages.
Error Message VMTRACKER-2-VMTRACKER_CONNECTION_ISSUE: Problem with connection: [chars]
Explanation Connection problem
Recommended Action Problem with connection. Try "no connect"; "connect"
Error Message VMTRACKER-2-VMTRACKER_HMM_REGISTRATION_FAIL: [chars]
Explanation HMM Registration error
Recommended Action No action is required.
Error Message VMTRACKER-2-VMTRACKER_TRUNK_MODE_WARN: Interface [chars] is used by VMTracker. Changing it back to TRUNK mode.
Explanation Port trunk mode warning message
Recommended Action Do not change port mode when it is used by VMTracker. To change the mode, disable VMTracker on the interface first.
Error Message VMTRACKER-3-VMTRACKER_SOAP_ERR: Soap Err:[chars]
Explanation Soap Call failure message
Recommended Action No action is required.
Error Message VMTRACKER-4-VMTRACKER_HMM_TRIGGER_FAIL: auto-config trigger failure, vlan [dec] [chars]
Explanation HMM Request error
Recommended Action No action is required.
Error Message VMTRACKER-4-VMTRACKER_SOAP_WARN: Soap Warn:[chars]
Explanation Soap Call warning message
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_CONFIG_VLAN: [chars]
Explanation Vlan configuration message
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_CREATE_VLAN: Vlan Created: [chars]
Explanation Vlan addition message
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_DISABLED: Service Disabled
Explanation Service Disabled
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_ENABLED: Service Enabled
Explanation Service enabled
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_MESSAGE: [chars]
Explanation Generic message
Recommended Action No action is required.
Error Message VMTRACKER-5-VMTRACKER_REMOVE_VLAN: Vlan Removed: [chars]
Explanation Vlan deletion message
Recommended Action No action is required.
This section contains the VNI messages.
Error Message VNI-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Error Message VNI-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Error Message VNI-6-INTERFACE_EVENT: VSAN interface [chars] [chars]
Explanation The specified VSAN Interface has been successfully [chars].
Recommended Action No action is required.
Error Message VNI-6-STARTING: Virtual Network Interface Manager started
Explanation The service has successfully started.
Recommended Action No action is required.
Error Message VNI-6-VSAN_DELETED: VSAN [dec] has been deleted
Explanation The specified VSAN has been deleted. The service will delete all the configuration on that VSAN.
Recommended Action No action is required.
This section contains the VNSEGMENT_MGR messages.
Error Message VNSEGMENT_MGR-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode = [dec], Error code = [hex]
Explanation VNSEG encountered an error in processing an MTS message. The error and message are specified in the error message
Recommended Action No action is required.
Error Message VNSEGMENT_MGR-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.
Error Message VNSEGMENT_MGR-2-VNSEG_INIT: VNSEG initialization of [chars] [chars]
Explanation VNSEG 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.
Error Message VNSEGMENT_MGR-2-VNSEG_ISSU_LC_RESET: VNSEG 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 VNSEG 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 VNSEG detects a potential Loop, it will reset the Linecard to prevent the Loop
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-2-VNSEG_PENDING_RESPONSE_TIMEOUT: Waiting for Pending response for req [chars] (msg id:[dec])
Explanation Responses not received for requests sent out
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-2-VNSEG_SET_PORT_STATE_FAIL: Port state change req to PIXM failed, status = [hex] [[chars]] vdc [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
Error Message VNSEGMENT_MGR-2-VNSEG_SET_PORT_STATE_TIMEOUT: Port state change req to PIXM timedout after [dec] sec. vdc [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
Error Message VNSEGMENT_MGR-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
Error Message VNSEGMENT_MGR-6-PORT_DELETED: Interface [chars], removed from [chars]
Explanation This spanning tree port has been deleted
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-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
Error Message VNSEGMENT_MGR-6-SERVICE_UP: Initialized [chars]
Explanation VNSEG line 2.
Recommended Action No action is required.
Error Message VNSEGMENT_MGR-6-STATE_CREATED: Internal state created [chars]
Explanation VNSEG has created its internal state stateless/stateful [chars].
Recommended Action No action is required.
This section contains the VNTAGC messages.
Error Message VNTAGC-5-VNTAGC_GENERIC_SYSLOG: [chars]
Explanation VNTag Manager Client Generic Syslog
Recommended Action No action is required.
This section contains the VNTAG_MGR messages.
Error Message VNTAG_MGR-2-MCAST_DVIF_ALLOC_FAILURE: DVIF allocation failure during MCAST group creation. TCB RID: [hex]. MCAST LTL: [hex]. Reason: [chars].
Explanation MCAST DVIF allocation for MCAST group.
Recommended Action No action is required.
Error Message VNTAG_MGR-2-VLAN_DVIF_ALLOC_FAILURE: DVIF allocation failure for VLANs [chars]. Reason: [chars].
Explanation Flood DVIF allocation failure for VLANs.
Recommended Action No action is required.
Error Message VNTAG_MGR-2-VNTAG_IFTMC_ERROR: Desired VLAN programming failed !!! Kindly undo the VLAN programming and retry with reduced Allowed-VLAN scale
Explanation IFTMC Programming Failure due to Table Exhaustion
Recommended Action No action is required.
Error Message VNTAG_MGR-2-VNTAG_SEQ_ERROR: [chars]
Explanation Some step in an event sequence has failed
Recommended Action No action is required.
Error Message VNTAG_MGR-2-VNTAG_SEQ_TIMEOUT: [chars]
Explanation Event sequence timeout
Recommended Action No action is required.
Error Message VNTAG_MGR-5-VNTAG_MGR_DISABLED: VNTag Manager Disabled
Explanation VNTag Manager Service Disabled
Recommended Action No action is required.
Error Message VNTAG_MGR-5-VNTAG_MGR_ENABLED: VNTag Manager Enabled
Explanation VNTag Manager Service Enabled
Recommended Action No action is required.
Error Message VNTAG_MGR-5-VNTAG_MGR_GENERIC_SYSLOG: [chars]
Explanation VNTag Manager Generic Syslog
Recommended Action No action is required.
This section contains the VPC messages.
Error Message VPC-2-L3_VPC_UNEQUAL_WEIGHT: Layer3 peer-router is enabled. Please make sure both vPC peers have the same L3 routing configuration
Explanation Unequal weight routing is not supported when layer3 peer-router is enabled
Recommended Action No action is required.
Error Message VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain [dec], VPC peer keep-alive receive has failed
Explanation Peer keep-alive receive failed
Recommended Action No action is required.
Error Message VPC-2-PEER_KEEP_ALIVE_SEND_FAIL: In domain [dec], VPC peer keep-alive send has failed
Explanation Peer keep-alive send failed
Recommended Action No action is required.
Error Message VPC-2-PEER_VPC_RESP_TIMEDOUT: Failed to receive response from peer for vPC: [dec]
Explanation VPC bringup failed
Recommended Action No action is required.
Error Message VPC-2-TRACK_INTFS_DOWN: In domain [dec], vPC tracked interfaces down, suspending all vPCs and keep-alive
Explanation VPC tracked object down
Recommended Action No action is required.
Error Message VPC-2-VPCCONFIG_ON_FPC: A green start is a must after ISSU for VPC config on FPC([hex]) for AA-FEX bringup. Please ignore if you already reloaded the switch after upgrading to version >= 7.0.3(I5)2
Explanation Green start (post ISSU) is a must to ensure programming correctness before configuring AA-FEXes
Recommended Action No action is required.
Error Message VPC-2-VPC_ADD_L3_BKUP_VLAN_TO_PEER_GW_EXCLUDE_LIST: Exclude L3 backup routing VLAN from vpc peer-gateway config.
Explanation Triggered when peer-link is F1 and peer-gateway is configured without exclude-vlan list.
Recommended Action No action is required.
Error Message VPC-2-VPC_CORE_PORT_FPATH_BUP_FAILED: Failed to bring up vPC+ peer link port [chars] in Fabric Path Port Mode - vPC+ Fabric Path switch ID not configured
Explanation VPC+ Failed to bringup peer-link - switch-ID not configured
Recommended Action No action is required.
Error Message VPC-2-VPC_ES_FAILED_LID_ALLOC: Failed to negotiate common LID between vPC peers.
Explanation Failed to find common lid.
Recommended Action No action is required.
Error Message VPC-2-VPC_ES_FAILED_PEERLINK_DOWN: vPC+ operations failed. Bringing down peer-link.
Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Recommended Action No action is required.
Error Message VPC-2-VPC_ES_PEER_LINK_OPERATION_FAILED: Peer-link operation failed due to SAP [dec].
Explanation Triggered in mcecm_cfg_es_failed when peer-link bringup fails.
Recommended Action No action is required.
Error Message VPC-2-VPC_GRACEFUL_SUSP_ALL_VPC: Operational graceful type-1 check state changed, reinitiating all vPCs
Explanation Graceful state change,reinit vPCs
Recommended Action No action is required.
Error Message VPC-2-VPC_ISSU_END: Peer vPC switch ISSU end, unlocking configuration
Explanation Peer vPC switch issu end
Recommended Action No action is required.
Error Message VPC-2-VPC_ISSU_START: Peer vPC switch ISSU start, locking configuration
Explanation Peer vPC switch issu start
Recommended Action No action is required.
Error Message VPC-2-VPC_LC_FAIL: LC [dec] does not support required hardware for vPC; run 'show vdc membership status' for port status
Explanation Lc insertion failed
Recommended Action No action is required.
Error Message VPC-2-VPC_NON_DEF_LID: vPC+ negotiated non-default local id. Flapping orphan edge ports recommended.
Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Recommended Action No action is required.
Error Message VPC-2-VPC_PEER_LINK_FPATH_BUP_FAILED: Failed to bring up vPC+ peer link port [chars] - port [chars] is not configured as a Fabric Path port
Explanation VPC+ Failed to bringup Peer-link - not in Fabric Path mode
Recommended Action No action is required.
Error Message VPC-2-VPC_PSS_ERROR: [chars], 0x([hex]) present in VPC DB but not is IM DB
Explanation Triggered when vpc DB and IM SDB are inconsistent
Recommended Action No action is required.
Error Message VPC-2-VPC_SHUTDOWN: vPC shutdown status is [chars]
Explanation VPC shutdown status change
Recommended Action No action is required.
Error Message VPC-2-VPC_STATE_CHANGE_ON_PEER_ISSU: VPC [dec] state transition happened during peer ISSU, please shut and no shut the VPC PO on both the Switches
Explanation VPC state change during peer on ISSU, check the HW programming on both the switches
Recommended Action No action is required.
Error Message VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on secondary. If vfc is bound to vPC, then only ethernet vlans of that VPC shall be down.
Explanation Peer link down suspend vPCs
Recommended Action No action is required.
Error Message VPC-2-VPC_SVI_EXCLUDE: vPC [dec] has up vlans [chars] which are excluded from suspension on dual-active
Explanation VPC track object deconfigured
Recommended Action No action is required.
Error Message VPC-3-FEX_AA_NO_SUPPPORT: FEX AA not supported
Explanation FEX AA not supported
Recommended Action No action is required.
Error Message VPC-3-GLOBAL_CONSISTENCY_FAILED: In domain [dec], global configuration is not consistent ([chars])
Explanation Global compat-check failed
Recommended Action No action is required.
Error Message VPC-3-INTF_CONSISTENCY_FAILED: In domain [dec], VPC [dec] configuration is not consistent ([chars])
Explanation MCEC compat-check failed
Recommended Action No action is required.
Error Message VPC-3-PEER_UNREACHABLE: Remote Switch Unreachable
Explanation Peer unreachable
Recommended Action No action is required.
Error Message VPC-3-PEER_VPC_BRINGUP_FAILED: Peer vPC [dec] bringup failed ([chars])
Explanation Peer vPC bringup failed
Recommended Action No action is required.
Error Message VPC-3-VPCM_ASSERTION_FAILED: [chars]
Explanation VPCM has hit an assert condition at file [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_INIT_FAIL: vPC Manager Initialization Failed ([chars])
Explanation VPCM Initialization failed. due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_INTERNAL_ERR: [chars]
Explanation VPCM encountered an internal error due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_MTS_ERR: [chars]
Explanation VPCM encountered an MTS error due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPC_BRINGUP_FAILED: vPC [dec] bringup failed ([chars])
Explanation VPC bringup failed
Recommended Action No action is required.
Error Message VPC-3-VPC_PEER_LINK_BRINGUP_FAILED: vPC peer-link bringup failed ([chars])
Explanation VPC Peer-link bringup failed
Recommended Action No action is required.
Error Message VPC-3-VPC_PEER_LINK_DOWN: VPC Peer-link is down
Explanation VPC Peer link is down
Recommended Action No action is required.
Error Message VPC-4-PEER_VPC_DELETED: Peer vPC [dec] deleted
Explanation Peer vPC configuration deleted
Recommended Action No action is required.
Error Message VPC-4-VPC_CFGD_EXISTING: vPC [dec] might be used already, please check vpc configuration!
Explanation VPC configuration duplication
Recommended Action No action is required.
Error Message VPC-4-VPC_CONSISTENCY_NEW_VLAN_FAIL: Global Consistency check for vPC failed for new vlans
Explanation Global Consistency check for vPC failed for new vlans
Recommended Action No action is required.
Error Message VPC-4-VPC_DELETED: vPC [dec] is deleted
Explanation VPC configuration deleted
Recommended Action No action is required.
Error Message VPC-4-VPC_DISABLE_IP_REDIRECTS: peer-gateway enabled. Disabling IP redirects on all interface-vlans of this vPC domain for correct operation of this feature.
Explanation Peer-gateway enabled, hence IP redirects on SVIs are disabled
Recommended Action No action is required.
Error Message VPC-4-VPC_LC_UPG_OVER_DELIVERY_FAIL: Failed to deliver LC upgrade to vPC peer
Explanation Failed to deliver LC upgrade to peer
Recommended Action No action is required.
Error Message VPC-4-VPC_PEER_LINK_DELETED: vPC Peer-link deleted. This will bringdown all vPC interfaces
Explanation VPC Peer-link configuration removed
Recommended Action No action is required.
Error Message VPC-4-VPC_PEER_ROLE_CHANGE: In domain [dec], VPC peer role status has changed to [chars]
Explanation VPC Peer role status changed to (Primary/Secondary
Recommended Action No action is required.
Error Message VPC-4-VPC_PER_VLAN_CONSISTENCY_FAILED: Global consistency check for vPC failed for few vlans
Explanation Global Consistency check for vPC failed for few vlans
Recommended Action No action is required.
Error Message VPC-4-VPC_PER_VLAN_NO_SUPPORT: ISSD/ISSU to an image that does not support "per-vlan type-1 check" will not bring down/up any vlan (i.e. nothing will happen) until next compat-check.
Explanation Triggered when ISSU/ISSD to an image which does not support per-vlan compat-check
Recommended Action No action is required.
Error Message VPC-4-VPC_REINITIALIZED: Reinitializing vpcs assuming peer dead
Explanation Initializing vpcs assuming peer dead
Recommended Action No action is required.
Error Message VPC-4-VPC_ROLE_CHANGE: In domain [dec], VPC role status has changed to [chars]
Explanation VPC role status changed to (Primary/Secondary
Recommended Action No action is required.
Error Message VPC-5-GLOBAL_CONSISTENCY_SUCCESS: In domain [dec], global configuration is consistent
Explanation Global compat-check passed
Recommended Action No action is required.
Error Message VPC-5-INTF_CONSISTENCY_SUCCESS: In domain [dec], vPC [dec] configuration is consistent
Explanation VPC configuration is consistent
Recommended Action No action is required.
Error Message VPC-5-ORPHANPORT_RESUME: Orphan-port [chars] is removed from suspended
Explanation Orphan-port is removed from suspended due to peer-link up or VPC role selection
Recommended Action No action is required.
Error Message VPC-5-ORPHANPORT_SUSPEND: Orphan-port [chars] is suspended
Explanation Orphan-port is suspended due to peer-link down or no VPC role selection
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_RECV_INT_LATEST: In domain [dec], VPC peer-keepalive received on interface [chars]
Explanation VPC peer-keepalive receive interface changed
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_RECV_SUCCESS: In domain [dec], vPC peer keep-alive receive is successful
Explanation Peer keep-alive receive successful
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_SEND_INT_LATEST: In domain [dec], VPC peer-keepalive sent on interface [chars]
Explanation VPC peer-keepalive send interface changed
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_SEND_SUCCESS: In domain [dec], vPC peer keep-alive send is successful
Explanation Peer keep-alive send successful
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_STATUS: In domain [dec], peer keep-alive status changed to [chars]
Explanation Peer keep-alive (oob) status is changed to Recommended Action Peer-not-alive
Error Message VPC-5-ROLE_PRIORITY_CFGD: In domain [dec], vPC role priority changed to [dec]
Explanation Role priority configured
Recommended Action No action is required.
Error Message VPC-5-SYSTEM_MAC_CFGD: In domain [dec], vPC system-mac changed to [chars]
Explanation System mac configured
Recommended Action No action is required.
Error Message VPC-5-SYSTEM_PRIO_CFGD: In domain [dec], vPC system priority changed to [dec]
Explanation System priority changed
Recommended Action No action is required.
Error Message VPC-5-VPCM_DISABLED: vPC Manager disabled
Explanation VPCM Service Disabled
Recommended Action No action is required.
Error Message VPC-5-VPCM_ENABLED: vPC Manager enabled
Explanation VPCM Service Enabled
Recommended Action No action is required.
Error Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_EXPIRED: vPC restore, delay interface-vlan bringup timer expired, reinitiating interface-vlans
Explanation VPC delay interface-vlan restore timer expired
Recommended Action No action is required.
Error Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_START: vPC restore, delay interface-vlan bringup timer started
Explanation VPC delay interface-vlan restore timer start
Recommended Action No action is required.
Error Message VPC-5-VPC_DOWN: vPC [dec] is down ([chars])
Explanation VPC is down (reason)
Recommended Action No action is required.
Error Message VPC-5-VPC_OPERATIONAL_L3_ROUTING: VPC operational layer 3 peer-router is [chars]
Explanation VPC operational layer 3 peer-router enabled or disabled
Recommended Action No action is required.
Error Message VPC-5-VPC_PEER_LINK_UP: vPC Peer-link is up
Explanation VPC Peer-link is up
Recommended Action No action is required.
Error Message VPC-5-VPC_RESTORE_TIMER_EXPIRED: vPC restore timer expired, reinitiating vPCs
Explanation VPC restore timer expired
Recommended Action No action is required.
Error Message VPC-5-VPC_RESTORE_TIMER_START: vPC restore timer started to reinit vPCs
Explanation VPC restore timer start
Recommended Action No action is required.
Error Message VPC-5-VPC_ROLE_PREMPT: In domain [dec], vPC role pre-emption triggered
Explanation VPC preemption triggered
Recommended Action No action is required.
Error Message VPC-5-VPC_SCALE_LIMIT: No port-channel limit configuration is [chars]
Explanation No port-channel limit configuration is changed
Recommended Action No action is required.
Error Message VPC-5-VPC_UP: vPC [dec] is up
Explanation MCEC is UP
Recommended Action No action is required.
Error Message VPC-6-PEER_LOCK_FAILED: Locking failed on peer switch - Aborting upgrade!!
Explanation Locking failed on peer switch
Recommended Action No action is required.
Error Message VPC-6-PEER_VPC_CFGD_VLANS_CHANGED: Peer vPC [dec] configured vlans changed
Explanation Remote MCEC configured vlans Changed
Recommended Action No action is required.
Error Message VPC-6-PEER_VPC_CFGD: peer vPC [dec] is configured
Explanation VPC is configured
Recommended Action No action is required.
Error Message VPC-6-PEER_VPC_DOWN: Peer vPC [dec] is down ([chars])
Explanation Peer vPC is down
Recommended Action No action is required.
Error Message VPC-6-PEER_VPC_UP: Peer vPC [dec] is up
Explanation Peer vPC is up
Recommended Action No action is required.
Error Message VPC-6-STATS_CLEARED: vPC Statistics Cleared
Explanation VPC statistics cleared
Recommended Action No action is required.
Error Message VPC-6-TRACK_OBJ_CONFIGURED: In domain [dec], track object configured [dec]
Explanation VPC track object configured
Recommended Action No action is required.
Error Message VPC-6-TRACK_OBJ_DELETED: In domain [dec], track object deleted
Explanation VPC track object deconfigured
Recommended Action No action is required.
Error Message VPC-6-TYPE1_PARAM_CHANGED: TYPE-1 parameters changed: [chars]
Explanation Type-1 Parameters Changed
Recommended Action No action is required.
Error Message VPC-6-VPCM_INTERNAL_INFO: [chars]
Explanation VPCM got an internal info [chars]
Recommended Action No action is required.
Error Message VPC-6-VPC_ALLOWED_VLAN_CHANGED: vPC [dec] operational vlans changed
Explanation Operational vlans changed on vPC
Recommended Action No action is required.
Error Message VPC-6-VPC_CFGD: vPC [dec] is configured
Explanation VPC is configured
Recommended Action No action is required.
Error Message VPC-6-VPC_CONSISTENCY_CHECK_BYPASS: Bypassing consistency check for vPC: [dec]
Explanation Bypassing consistency check for vpcs
Recommended Action No action is required.
Error Message VPC-6-VPC_CONSISTENCY_NEW_VLAN_PASS: Global Consistency check for vPC passed for new vlans
Explanation Global Consistency check for vPC passed for new vlans
Recommended Action No action is required.
Error Message VPC-6-VPC_DOMAIN_ID_CFGD: vPC domain-id configured to [dec]
Explanation VPC domain-id configured
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_EGRESS_DF_STATE_CHANGED: Egress designated forwarder state changed from [chars] to [chars] for vPC [dec].
Explanation DF state changed for some vPC.
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_ID_CFGD: Fabricpath switch ID [dec] configured
Explanation Fabricpath switch ID configured
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_ID_REMOVED: Fabricpath switch ID [dec] removed
Explanation Fabricpath switch ID removed
Recommended Action No action is required.
Error Message VPC-6-VPC_PEER_LINK_CFGD: vPC peer-link is configured
Explanation VPC Peer-link is configured
Recommended Action No action is required.
Error Message VPC-6-VPC_PER_VLAN_CONSISTENCY_PASSED: Global Consistency check for vPC passed for all vlans
Explanation Global Consistency check for vPC passed for all vlans
Recommended Action No action is required.
This section contains the VRRP-CFG messages.
Error Message VRRP-CFG-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Error Message VRRP-CFG-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Error Message VRRP-CFG-5-STARTING: VRRP Manager service started
Explanation The service successfully started.
Recommended Action No action is required.
Error Message VRRP-CFG-5-VR_ADMIN_DOWN: VR [chars]group [dec] on interface [chars] is administratively down
Explanation The specified vrrp group is administratively down on interface [chars].
Recommended Action No action is required.
Error Message VRRP-CFG-5-VR_ADMIN_UP: VR [chars]group [dec] on interface [chars] is administratively up
Explanation The specified vrrp group is administratively up on interface [chars].
Recommended Action No action is required.
Error Message VRRP-CFG-5-VR_ADV_INT_CHANGE: Adv Interval for VR [chars]group [dec] on intf [chars] changed from [dec] to [dec] secs
Explanation The specified vrrp group advertisement inerval changed on interface [chars].
Recommended Action No action is required.
Error Message VRRP-CFG-5-VR_CREATED: VR [chars]group [dec] created on interface [chars]
Explanation The specified vrrp group has been successfully created on interface [chars].
Recommended Action No action is required.
Error Message VRRP-CFG-5-VR_DELETED: VR [chars]group [dec] removed from interface [chars]
Explanation The specified vrrp group has been successfully deleted on interface [chars].
Recommended Action No action is required.
This section contains the VRRP-ENG messages.
Error Message VRRP-ENG-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Error Message VRRP-ENG-2-VR_FAILURE: Error in VR[chars] [dec] interface [chars]. Going to init state
Explanation The VR [dec] on the interface [chars] is in init state for an internal error.
Recommended Action Show interface to check the status of the interface, show configuration, status and statistics of the specified virtual router, enable the vrrp debug and shut/ no shut the specified virtual router.
Error Message VRRP-ENG-3-ARP_INIT_ERROR: Failed to init ARP, ret [hex], errno [dec]
Explanation VRRP-ARP interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove interface level VRRP-BFD sessions ([hex] [hex]), Refer logs
Explanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_ADD_ERROR: Failed to add a few VRRP-BFD sessions([hex] [hex]), Refer logs
Explanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information([hex] [hex]), Refer logs
Explanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove a few VRRP-BFD sessions([hex] [hex]), Refer logs
Explanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Error Message VRRP-ENG-3-IP_INIT_ERROR: Failed to init IP, ret [hex], errno [dec]
Explanation VRRP-IP interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-3-L3VM_INIT_ERROR: Failed to init L3VM, ret [hex], errno [dec]
Explanation VRRP-L3VM interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-3-URIB_INIT_ERROR: Failed to init URIB, ret [hex], errno [dec]
Explanation VRRP-URIB interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-4-BAD_ADV: VR[chars] ID [dec] on interface [chars] bad advertisement received: reason [chars]
Explanation The virtual router specified has received an invalid advertisement.
Recommended Action Check that all VRRP nodes have the same configuration.
Error Message VRRP-ENG-5-INTERFACE_DOWN: Cannot start the VR[chars] [dec] since the interface [chars] is down
Explanation The specified VR is enabled but can't change state from init. The specified interface is down or doesn't have a primary IP address configured.
Recommended Action No action is required.
Error Message VRRP-ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed to [chars]
Explanation The interface specified has changed state This could have triggered a VRRP status change.
Recommended Action No action is required.
Error Message VRRP-ENG-5-INVALID_CONFIG: Cannot start the VR[chars] [dec] on the interface [chars]. Invalid IP configuration. Reason: [chars]
Explanation The specified VR on interface [chars] is enabled but the IP configuration is not valid because of [chars].
Recommended Action Show interface to check that the IP address of the interface is configured and it is in the same subnet of the virtual router address.
Error Message VRRP-ENG-5-STARTING: VRRP Engine service started
Explanation The service successfully started.
Recommended Action No action is required.
Error Message VRRP-ENG-5-VR_STATE_CHANGE: VR[chars] ID [dec] on interface [chars] state changed to [chars], event [chars]
Explanation The status of the specified virtual router has changed to [chars].
Recommended Action No action is required.
Error Message VRRP-ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change request result [chars]
Explanation The result of the request for status change on the virtual router (with VSHA extension) specified is [chars].
Recommended Action No action is required.
This section contains the VSAN messages.
Error Message VSAN-2-PROGRAM_EXIT: process exiting with reason: [chars]
Explanation VSAN manager process is exiting with reason [chars].
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.
Error Message VSAN-3-CFS_OPERATION_FAILED: cfs [chars] operation failed : [chars]
Explanation Cfs operation [chars1] has failed. [chars2]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec]
Explanation Memory allocation of size [dec] failed.
Recommended Action Do "show process memory" command to see memory usage of processes.
Error Message VSAN-3-MESSAGE_ERROR: could not handle message:[chars] of type [dec] sent by addr [dec]:[dec]
Explanation Got an IPC message [chars] of type [dec1] sent by a component running on node [dec2] with sap [dec3].
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.
Error Message VSAN-6-ACTIVATED: VSAN:[dec] changing from suspended to active
Explanation Making VSAN with ID [dec] active from suspended state.
Recommended Action No action is required.
Error Message VSAN-6-CFS_MERGE_NOT_SUPPORTED: merging of fctimer configuration data is not supported
Explanation Merging of fctimer configuration data using cfs is not supported
Recommended Action No action is required.
Error Message VSAN-6-CREATED: Created VSAN:[dec] with name:[chars]
Explanation Created VSAN with ID [dec] and name [chars].
Recommended Action No action is required.
Error Message VSAN-6-MEMBERSHIP_UPDATE: Updated membership for interface:[chars] with VSAN:[dec]
Explanation Updating membership for interface [chars] with VSAN [dec].
Recommended Action No action is required.
Error Message VSAN-6-REMOVED: Removed VSAN:[dec]
Explanation Removed VSAN with ID [dec].
Recommended Action No action is required.
Error Message VSAN-6-SUSPENDED: VSAN:[dec] changing from active to suspended
Explanation Suspending VSAN with ID [dec] from active state.
Recommended Action No action is required.
Error Message VSAN-6-TRUNKING_MEMBERSHIP_UPDATE: trunking membership updated for interface:[chars] with VSAN bitmap:[chars]
Explanation Updated trunking membership for interface [chars1] with allowed VSAN list [chars2].
Recommended Action No action is required.
This section contains the VSHD messages.
Error Message VSHD-2-VSHD_INVALID_HA_OPERATOR_OID: Unknown ha operator: [dec]
Explanation This is probably occurring due to improper config
Recommended Action Please collect show tech and debugs
Error Message VSHD-2-VSHD_INVALID_ROLE_OPCODE_OID: Invalid role op code [chars]
Explanation This is probably occurring due to improper config
Recommended Action Please collect show tech and debugs
Error Message VSHD-2-VSHD_INVALID_ROLE_SYNC_OID: Invalid role sync msg received
Explanation This is probably occurring due to improper config
Recommended Action Please collect show tech and debugs
Error Message VSHD-2-VSHD_INVALID_SUBTYPE_RANGE_OID: the name, the lower or the upper value of the subtype are not correct
Explanation This is probably occurring due to improper config
Recommended Action Please collect show tech and debugs
Error Message VSHD-2-VSHD_ROLE_DATABASE_TOO_LARGE: Role database too large. Unable to add RBAC entry
Explanation There are too many rules and policies configured causing the entire role database too exceed 120KB
Recommended Action Please delete some rules, policies, or roles and try to better optimize the RBAC database
Error Message VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function [chars] from library [chars] exited due to Signal [dec]
Explanation Error in CLI EOL function
Recommended Action No action is required.
Error Message VSHD-2-VSHD_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec]
Explanation PSS snapshot error
Recommended Action No action is required.
Error Message VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec]
Explanation Debug infrastructure error
Recommended Action No action is required.
Error Message VSHD-3-VSHD_ROLE_DISTRIBUTE_FAILURE: Role distribution operation ([chars]) failed with error id [hex]
Explanation This is probably occurring due to unstable fabric
Recommended Action Please retry operation when fabric is stable
Error Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec]
Explanation File handling error
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars]
Explanation MTS message handling error
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars]
Explanation Error while updating parse tree in shell
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec]
Explanation PSS handling error
Recommended Action No action is required.
Error Message VSHD-4-VSHD_LICENSE_EXPIRY_WARNING: License [chars] expires on [chars]. Vsan policy will be set to default (deny) for all roles when license expires
Explanation Vsan policy would be set default (deny) for all roles when license expires
Recommended Action Please install the license file to continue using the feature.
Error Message VSHD-4-VSHD_MTS_ERROR_OID: [chars]
Explanation This is probably occurring due to improper config
Recommended Action Please collect show tech and debugs
Error Message VSHD-4-VSHD_PORT_CHANNEL_CREATE: [chars]
Explanation This is probably occurring when trying to create more port channels than allowed
Recommended Action Please collect show tech, accounting logs and debugs
Error Message VSHD-4-VSHD_ROLE_DATABASE_OUT_OF_SYNC: Role configuration database found to be different between the switches during merge
Explanation Role configuration database is recommended to be identical among all switches in the fabric.
Recommended Action Edit the configuration on one of the switches to obtain the desired role configuration database and then commit it
Error Message VSHD-4-VSHD_ROLE_DATABASE_VERSION_NOT_UNDERSTOOD: This switch does not understand the version of role configuration database received during merge
Explanation This is probably occurring due to different versions of system image on switches in the fabric
Recommended Action Please make sure all switches are running the same version of the system image
Error Message VSHD-4-VSHD_ROLE_RULE_ACCESS_SCOPE_EXTRA_OID: Too many oid elements. Please enter up to 32.
Explanation This is probably occurring due to the value given for snmp oid field is more than 32 elements
Recommended Action Please make sure the oid element should not exceed 32
Error Message VSHD-4-VSHD_ROLE_RULE_ACCESS_SCOPE_INVALID_OID: Rule access scope OID value is Invalid
Explanation This is probably occurring due to the value given for snmp oid field is neither digit nor dot
Recommended Action Please make sure the oid value should only contains digit and dot
Error Message VSHD-5-VSHD_SYSLOG_CONFIG_CHANGE: VDC="[chars]", VTY="[chars]", user="[chars]", CMD="[chars]"
Explanation Configuration change notification
Recommended Action No action is required.
Error Message VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by [chars] on [chars]
Explanation CLI Configuration mode was exited
Recommended Action No action is required.
Error Message VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] created
Explanation New cli role created
Recommended Action No action is required.
Error Message VSHD-7-VSHD_SYSLOG_PARSE_TREE_UPDATE: Parse tree [chars]
Explanation Parse tree updated in shell
Recommended Action No action is required.
This section contains the VTP messages.
Error Message VTP-0-EMERGENCY_MSG: [chars]
Explanation VTP Emergency Message
Recommended Action Capture show tech-support vtp
Error Message VTP-1-ALERT_MSG: [chars]
Explanation VTP Alert Message
Recommended Action Capture show tech-support vtp
Error Message VTP-2-CRITICAL_MSG: [chars]
Explanation VTP Critical Message
Recommended Action No action is required.
Error Message VTP-2-VTP_MODE_OFF_LONG_VLAN_NAME_EXIST: VTP Mode changed to off as long vlan name configuration is enabled
Explanation By default, VTP feature comes up in Server mode. long vlan name can only be enabled in VTP transparent/off mode As long vlan name is already enabled, VTP mode is changed to off.
Recommended Action No action is required.
Error Message VTP-2-VTP_MODE_OFF_PVLAN_EXIST: VTP Mode changed to off as Private VLAN configuration exists
Explanation By default, VTP feature comes up in Server mode. Private Vlans can only operate in VTP transparent/off mode As Private Vlan configuration already exist, VTP mode is changed to off.
Recommended Action No action is required.
Error Message VTP-2-VTP_MODE_OFF_RESERVED_VLAN_EXIST: VTP Mode changed to off as reserved vlan configuration exists
Explanation By default, VTP feature comes up in Server mode. reserved vlans can only operate in VTP transparent/off mode As Reserved Vlan configuration already exist, VTP mode is changed to off.
Recommended Action No action is required.
Error Message VTP-3-ERROR_MSG: [chars]
Explanation VTP Error Message
Recommended Action No action is required.
Error Message VTP-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory
Explanation VLAN software failed to use VLAN configuration from startup-config file. It will fallback to use the binary VLAN configuration file in non-volatile memory.
Recommended Action No action is required.
Error Message VTP-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars]
Explanation The VLANs specified in the error message could not be created. The VLAN manager called an VLAN database routine to create one or more VLANs, but the Vlan Manager failed the VLAN creation requests.
Recommended Action Collect show tech-support
Error Message VTP-4-VTP_BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version: [dec]
Explanation The VLAN configuration file read by the VLAN manager contained an unrecognized file version number. (This may indicate an attempt to regress to an older version of the VLAN manager software.)
Recommended Action LOG_STD_ACTION
Error Message VTP-4-VTP_BAD_VLAN_CONFIGURATION_FILE: Vlan configuration file contained incorrect verification word: [hex]
Explanation The VLAN configuration file read by the VLAN manager did not begin with correct value which would indicate a valid VLAN configuration file. Thus, it has been rejected.
Recommended Action Collect show tech-support
Error Message VTP-4-VTP_BAD_VLAN_DOMAIN_NAME_LENGTH: VLAN configuration file contained incorrect domain name length: [dec]
Explanation The VLAN configuration file read by the VLAN manager did not contain a valid domain name length. Thus, it has been rejected.
Recommended Action Please provision VTP domain name again
Error Message VTP-4-VTP_BAD_VLAN_PASSWORD_LENGTH: VLAN configuration file contained incorrect VTP password length: [dec]
Explanation The VLAN configuration file read by the VLAN manager did not contain a valid VTP password length. Thus, it has been rejected.
Recommended Action Please provision VTP password again
Error Message VTP-4-VTP_INVALID_DATABASE_DATA: VTP received bad data
Explanation Invalid data was received by VTP process
Recommended Action Collect show tech-support
Error Message VTP-4-VTP_PROTOCOL_ERROR: VTP protocol code internal error: [chars]
Explanation VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.
Recommended Action Collect show tech-support
Error Message VTP-4-WARN_MSG: [chars]
Explanation VTP Warning Message
Recommended Action No action is required.
Error Message VTP-5-NOTIF_MSG: [chars]
Explanation VTP Notification Message
Recommended Action No action is required.
Error Message VTP-6-IFS_FAILURE: VLAN manager encountered file operation error: call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transfered = [dec]
Explanation VTP received an unexpected error return from a file system call.
Recommended Action Collect show tech-support
Error Message VTP-6-INFO_MSG: [chars]
Explanation VTP Informational Message
Recommended Action No action is required.
Error Message VTP-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].
Explanation The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.
Recommended Action No action is required.
Error Message VTP-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars].
Explanation Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is.
Recommended Action No action is required.
Error Message VTP-6-VTP_OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.
Explanation VLAN software detected an old version of the VLAN configuration file format. It was able to interpret the file with no problems but will create files using the new format in the future.
Recommended Action No action is required.
Error Message VTP-6-VTP_PRUNING_CHANGE: VTP Operational Pruning [chars].
Explanation VTP operational pruning changed. This can happen due to admin pruning change, VTP mode changes or VTP config propagation. 'show vtp status' output can be looked up to find the reason for this change.
Recommended Action Check 'show vtp status' output to find the reason for this change. No action is required.
Error Message VTP-7-DEBUG_MSG: [chars]
Explanation Association Manager Debug Message
Recommended Action No action is required.
This section contains the WWN messages.
Error Message WWN-1-TYPE1_ALERT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has run out of WWNs. No new dynamically allocated WWNs are available. However, statically assigned WWNs such as switch WWN, port WWN, etc. are still available.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-1-TYPES2_5_ALERT: Only [dec] (< [dec] %) Type 2 & 5 WWNs Remain
Explanation The WWN Manager has run out of WWNs of NAA Types 2 and 5
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-2-BKPLN_PROM_CANT_READ: Can not read backplane PROM
Explanation The WWN Manager has failed to read chassis information. No dynamic WWNs could be allocated.
Recommended Action 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.
Error Message WWN-2-EXITING: Exited due to [chars]
Explanation The WWN Manager process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message WWN-2-GENERAL_ERROR: [chars]
Explanation The WWN Manager has encountered an critical error. The description of error is [str.].
Recommended Action No action is required.
Error Message WWN-2-MALLOC_ERROR: Size [dec] bytes
Explanation The WWN Manager could not allocate memory.
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.
Error Message WWN-2-PSS_BKP_PSS_MISMATCH: Block [dec]: PSS: Not Free; BKPLN PROM: Free
Explanation This WWN Manager detected a discrepancy between the information on the chassis and that in its persistent information databases. The persistent information database has been updated with the information on the chassis.
Recommended Action No action is required.
Error Message WWN-2-PSS_ERROR: [chars]
Explanation The WWN Manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Error Message WWN-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars]
Explanation The WWN Manager has failed to rotate its current stdout file with filename [str.]. The filesize could grow beyond its maximum limit.
Recommended Action No action is required.
Error Message WWN-2-TYPE1_CRIT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-2-TYPES2_5_CRIT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-3-PSS_SYNC_TO_STNDBY_FAILED: PSS TYPE=[chars] KEY=[chars]
Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.].
Recommended Action No action is required.
Error Message WWN-3-RELEASE_ERR_UNKNOWN: Unknown WWN [chars] [chars]
Explanation WWN Manager received a request to release a WWN [char] that could not have been allocated by this WWN Manager due to [char].
Recommended Action No action is required.
Error Message WWN-3-RELEASE_ERR: Cant Rel. WWN [chars]
Explanation WWN Manager received a request to release a WWN that cannot be released.
Recommended Action No action is required.
Error Message WWN-3-STARTUP_COPY_TO_RUNNING_FAILED: [chars]
Explanation Could not snapshot Startup-Config PSS to Running-Config. The description of error is [str.].
Recommended Action No action is required.
Error Message WWN-3-TOOMANY_REQ_REL: WWNs [chars] = [dec] > MAX LIMIT 1024 - Denied
Explanation The WWN Manager received a request to allocate [dec] WWN, which is more than the maximum number of WWNs that can be allocated/released in a single request.
Recommended Action No action is required.
Error Message WWN-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec] Opcode=[dec]
Explanation The WWN Manager has received an unknown message from [dec]].[dec] with opcode [dec]. This information is for debugging only.
Recommended Action No action is required.
Error Message WWN-3-WWN_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The WWN Manager has detected corruption in one of its persistent information database. The database would be recreated.
Recommended Action No action is required.
Error Message WWN-4-PSS_SUP_CNT_MISMATCH: PSS [dec] Bkpln [dec]
Explanation The WWN Manager has detected that some other supervisor card was plugged in earlier on this chassis. This WWN Manager is making sure that new WWNs allocate do not conflict with WWNs that could have been allocated by the previous supervisor card.
Recommended Action No action is required.
Error Message WWN-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the WWN Manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error Message WWN-4-TYPE1_WARN: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining for allocation.
Recommended Action No action is required.
Error Message WWN-4-TYPES2_5_WARN: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-5-VSAN_WWN_CHANGE: [chars]
Explanation VSAN-WWN created or deleted. The description of error is [str.].
Recommended Action No action is required.
Error Message WWN-6-ALLOCATED_BLOCK: Block number [dec]
Explanation The WWN Manager has allocated a new block, block number [dec], of 256 WWNs for internal use.
Recommended Action No action is required.
Error Message WWN-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The WWN Manager on the standby supervisor became active and it is ready to serve client requests for WWNs.
Recommended Action No action is required.
Error Message WWN-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The WWN Manager became standby from active mode.
Recommended Action No action is required.
Error Message WWN-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.].
Recommended Action No action is required.
Error Message WWN-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]
Explanation The WWN Manager was unable to send heartbeat to the system manager.
Recommended Action No action is required.
Error Message WWN-6-GENERAL_EVENT: [chars]
Explanation The WWN Manager has generated an important event. The description of the event is [str.].
Recommended Action No action is required.
Error Message WWN-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of the WWN Manager has been recreated.
Recommended Action No action is required.
Error Message WWN-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases has been intentionally destroyed and would be recreated.
Recommended Action No action is required.
Error Message WWN-6-RELEASED_BLOCK: Block number [dec]
Explanation The WWN Manager has released a block, block number [dec], of 256 WWNs.
Recommended Action No action is required.
Error Message WWN-6-SEC_MAC_UPDATED: MAC=[chars] Range=[dec]
Explanation The WWN Manager had updated the Secondary MAC address with MAC address [char] and range [dec]. This update was initiated from a management entity.
Recommended Action No action is required.
Error Message WWN-6-SERVICE_UP: Initialized [chars]
Explanation The WWN Manager is up and ready to accept client requests for WWNs. The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message WWN-6-SWITCHOVER: Switching Over to other Supervisor
Explanation The WWN Manager has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Error Message WWN-7-RELEASE_ERR_FREE: Already free WWN [chars]
Explanation A client of WWN Manager attempted to release WWN [char] which is already free. This information is for debugging only.
Recommended Action No action is required.
This section contains the XBAR_CLIENT messages.
Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_MEM_FULL: memory allocation failed in routine [chars]
Explanation Process xbar_client failed to allocate memory
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_DN: terminating due to signal [dec]
Explanation Process xbar_client is exiting
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_INITFAIL: initialization failed: [chars], errno [dec]
Explanation Process xbar_client failed initialization
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-2-XBC_ALL_INTERNAL_LINKS_DOWN: [chars]
Explanation All internal links on module are down
Recommended Action Please perform a 'show system xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-2-XBC_INTERNAL_LINK_DOWN: [chars], macf link - [dec], hg link - [dec]
Explanation The internal link on module is down
Recommended Action Please perform a 'show system xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_IPC_MSGUNKN: unknown IPC message received: opcode [dec]
Explanation Process xbar_client hass received an unknown IPC message
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]
Explanation The module initialiazation failed
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Error Message XBAR_CLIENT-SLOT#-4-XBC_SOME_INTERNAL_LINK_DOWN: Internal HG links from LC unit-[dec] to FM unit-[dec] are down
Explanation Some internal links on module are down
Recommended Action Please perform a 'show system xbar-client event-history' to collect more information
This section contains the XBAR messages.
Error Message XBAR-2-ARB_INIT_FAIL: Arbiter Initialization failed return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-2-INCOMPATIBLE_CONFIG: [chars] [dec] [chars].
Explanation This module is not compatible with the current fabric mode. It will be powered down.
Recommended Action No action is required.
Error Message XBAR-2-XBAR_HGLINK_DOWN: fabric link [dec] on [chars]module [dec] unit [dec] connected to [chars]module [dec] unit [dec] is down
Explanation Received fabric link down event.
Recommended Action No action is required.
Error Message XBAR-2-XBAR_HGLINK_FLAP: fabric link [dec] on [chars]module [dec] unit [dec] connected to [chars]module [dec] unit:[dec] flapped and violated eem policy
Explanation Fabric link flapped more times than the configured limit of eem policy.
Recommended Action No action is required.
Error Message XBAR-2-XBAR_HGLINK_NOT_UP: fabric link [dec] on [chars]module [dec] unit [dec] connected to [chars]module [dec] unit:[dec] is not up during module bring up
Explanation Fabric link did not come up during module bring up.
Recommended Action No action is required.
Error Message XBAR-2-XBAR_INSUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has insufficient xbar-bandwidth.
Explanation To track insufficient xbar-bandwidth.
Recommended Action No action is required.
Error Message XBAR-2-XBAR_MIXED_SPINES_POLICY_MATCHED: [chars]
Explanation Fabric could not be brought online due to policy match:
Recommended Action No action is required.
Error Message XBAR-2-XBAR_SUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has sufficient xbar-bandwidth.
Explanation To track recovery from insufficient xbar-bandwidth.
Recommended Action No action is required.
Error Message XBAR-2-XBM_EEM_FABRIC_ACTION: Fabric [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %i
Explanation Xbar-manager has removed the fabric because an eem policy has been met This means that the fabric has hit the maximum number of recoverable sync-losses with multiple line-cards within a time-window.
Recommended Action No action is required.
Error Message XBAR-2-XBM_EEM_MODULE_ACTION: Module [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %i
Explanation Xbar-manager has removed the linecard because an eem policy has been met This means that the module has hit the maximum number of recoverable sync-losses with fabric card(s) within a time-window.
Recommended Action No action is required.
Error Message XBAR-3-MEM_FULL: Memory allocation failed. [chars] %i
Explanation
Recommended Action No action is required.
Error Message XBAR-4-XBAR_MIXED_SPINES_IN_CHASSIS: [chars]
Explanation There are both FAB-1 and FAB-2 type spines in the Chassis. Please replace the FAB-1 spines with FAB-2 Spines.
Recommended Action No action is required.
Error Message XBAR-5-ARBITER_INIT_FAILURE: Re-initializing Arbiter. [chars] [chars] module %i
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_CLEAR_PORT_FAIL: Arbiter reported failure to de-register port [dec] in group [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_MOD_DIS_INTR_FAIL: Arbiter reported failure to disable interrupt for module [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_MOD_INSERT_CHECK_FAIL: Arbiter reported failure to recognize module [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_MOD_INSERT_FAIL: Arbiter reported failure to init module [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_MOD_INTR_FAIL: Arbiter reported failure to enable interrupt for module [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_MOD_REMOVE_FAIL: Arbiter reported failure to remove module [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-ARB_INIT_PORT_FAIL: Arbiter reported failure to register port [dec] in group [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Recommended Action No action is required.
Error Message XBAR-5-MOD_CONNECTION_REATTEMPT: Re-attempting XBAR connection with module [dec]
Explanation The module has experienced a setup failure on connecting the module to the fabric.
Recommended Action Collect more informations about XBAR component Use command 'show xbar internal event-history module
Error Message XBAR-5-SYNC_THRESHOLD_FAILURE: Module resync threshold exceeded [chars] [chars] module %i
Explanation This module has exceeded the number of resync attempts in a day. Module will be reloaded
Recommended Action No action is required.
Error Message XBAR-5-XBAR_ENABLE_FPOE_DB_FAILURE: XBAR [chars] enabling FPOE-DB mode failed
Explanation The supervisor failed to enable FPOE-DB mode in fabric. The supervisor is going to reboot. In case of dual supervisor, a switchover will occur.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_INIT_FAILURE: XBAR [chars] initialization failed [chars] %i
Explanation The supervisor has experienced a fabric initialization failure. The supervisor is going to reboot. In case of dual supervisor, a switchover will occur.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig intialization return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_MOD_INSERT_SEQ_FAILURE: [chars] for module [dec]
Explanation The xbar manager received failure response and is failing the insert sequence
Recommended Action No action is required.
Error Message XBAR-5-XBAR_MOD_LC_INSERT_SEQ_FAILURE: Module in slot [dec] has failed insert sequence
Explanation The xbar manager is failing the insert sequence
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_FORCE_POE_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable force poe mode on [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_FORCE_POE_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable force poe mode on [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_RELEASE_ACCESS_FAIL: Slot [dec] reported failure releasing [chars] xbar access return_code [hex] ([chars])
Explanation The supervisor has experienced an xbar access failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_SET_ACCESS_FAIL: Slot [dec] reported failure acquiring [chars] xbar access return_code [hex] ([chars])
Explanation The supervisor has experienced an xbar access failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_STANDBY_SUP_ARB_FAIL: [chars] return_code [hex] ([chars])
Explanation The supervisor has experienced an arbiter access failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_STATUS_REPORT: Module [dec] reported status for component [dec] code [hex].
Explanation An error status has been reported. If error is on supervisor, the supervisor is going to reboot. In case of dual supervisors, a switchover will occur. If error is on module, the module will be power cycled.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig sw intialization return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Recommended Action No action is required.
Error Message XBAR-5-XBAR_VERSION_CHECK_FAILURE: XBAR [chars] SCZ version check failed [chars] %i
Explanation This SUP has an older Santacruz version, and so will not be allowed to power-up, Please upgrade to the latest supervisor version.
Recommended Action No action is required.
This section contains the XMLMA messages.
Error Message XMLMA-2-HEARTBEAT_FAIL: XML master agent failed to send heart beat: [chars]
Explanation XML master agent has failed sending heartbeat.
Recommended Action No action is required.
Error Message XMLMA-2-INITFAIL: XML master agent initialization fails: [chars]
Explanation XML master agent has failed initialization.
Recommended Action No action is required.
Error Message XMLMA-2-MTSERROR: XML master agent mts operation failed: [chars]
Explanation XML master agent mts operation failed.
Recommended Action No action is required.
Error Message XMLMA-2-PSSFAILURE: XML master agent pss operation failed: [chars]
Explanation XML master agent pss operation failed.
Recommended Action No action is required.
Error Message XMLMA-2-XMLMACRIT: XML master agent: [chars]
Explanation XML master agent critical log.
Recommended Action No action is required.
Error Message XMLMA-3-XMLMAERR: XML master agent: [chars]
Explanation XML master agent error log.
Recommended Action No action is required.
Error Message XMLMA-5-STARTING: XML master agent started [chars]
Explanation XML master agent has been started.
Recommended Action No action is required.
Error Message XMLMA-6-XMLMAEXIT: XML master agent exiting...: [chars]
Explanation XML master agent is exiting.
Recommended Action No action is required.
Error Message XMLMA-6-XMLMALOG: XML master agent operation log: [chars]
Explanation XML master agent operation log.
Recommended Action No action is required.
This section contains the XMLSA messages.
Error Message XMLSA-2-CANDIDATE_WRITE_FAIL: Netconf session id:[dec],candidate config has no space left
Explanation No space left in candidate configuration of the netconf session.
Recommended Action Please send the commit or discard request for the outstanding config.
Error Message XMLSA-2-HEARTBEAT_FAIL: XML sub agent failed sending heart beat: [chars]
Explanation XML sub agent failed sending heartbeat.
Recommended Action No action is required.
Error Message XMLSA-2-INITFAIL: XML sub agent initialization fails: [chars]
Explanation XML agent has failed initialization.
Recommended Action No action is required.
Error Message XMLSA-2-USER_INACTIVE: XML sub agent timeed out: [chars]
Explanation XML sub agent timedout due to inactivity.
Recommended Action No action is required.
Error Message XMLSA-2-VSH_ERR: XML sub agent vsh cmd error...: [chars]
Explanation XML sub agent vsh cmd error.
Recommended Action No action is required.
Error Message XMLSA-5-RPC_ERROR: Netconf session id:[dec], operation:[chars], status:FAILED, reason:[chars]
Explanation Netconf operation has failed.
Recommended Action No action is required.
Error Message XMLSA-5-RPC_OK: Netconf session id:[dec], operation:[chars], status:SUCCESS
Explanation Netconf operation is successful.
Recommended Action No action is required.
Error Message XMLSA-5-STARTING: XML sub agent started: [chars]
Explanation XML sub agent has been started.
Recommended Action No action is required.
Error Message XMLSA-6-XMLSAEXIT: XML sub agent exiting...: [chars]
Explanation XML sub agent is exiting.
Recommended Action No action is required.
Error Message XMLSA-6-XMLSALOG: XML sub agent log: [chars]
Explanation XML sub agent log.
Recommended Action No action is required.
This section contains the ZONE messages.
Error Message ZONE-2-ZS_ALIAS_LIMIT_EXCEEDED: The limit for maximum number of aliases exceeded
Explanation The number of aliases configured has exceeded the maximum number of aliases allowed per vsan Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of aliases is less than the maximum allowed in a vsan.
Error Message ZONE-2-ZS_ATTR_GROUP_LIMIT_EXCEEDED: The limit for maximum number of attribute groups exceeded
Explanation The number of attribute groups configured has exceeded the maximum number of attribute groups allowed in a vsan Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of attribute groups is less than the maximum allowed in a vsan.
Error Message ZONE-2-ZS_BLOCKED_ATTR_PRESENT: Module [dec] failed to come online due to [chars] in VSAN [dec] to bring up the module.
Explanation Module [dec] failed to come up due to [chars].
Recommended Action Verify if RO/LUN/Broadcast attributes are configured, in the VSAN, disable if configured
Error Message ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed : [chars]
Explanation Zone Server cannot acquire change authorization : [chars].
Recommended Action Verify the interoperability mode on all the switches OR retry later.
Error Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed on VSAN [dec]
Explanation Zone Server cannot acquire authorization on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: Activation failed : reason [chars] domain [dec]
Explanation Zone Server cannot activate due to reason [chars] on domain [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN: Activation failed : reason [chars]
Explanation Zone Server cannot activate due to reason [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failed
Explanation Zone Server cannot activate the zoneset.
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_APPLY_FAILED: Apply changed failed on VSAN [dec]
Explanation Zone Server cannot apply changes on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN_DOM: Deactivation failed : reason [chars] domain [dec]
Explanation Zone Server cannot deactivate due to reason [chars] on domain [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN: Deactivation failed : reason [chars]
Explanation Zone Server cannot deactivate due to reason [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Deactivation failed
Explanation Zone Server cannot deactivate the zoneset.
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_RELEASE_AUTH_FAILED: Release authorization failed on VSAN [dec]
Explanation Zone Server cannot release authorization on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_RRCA_REJECTED: RRCA received from remote domain [dec] is rejected: [chars]
Explanation Received invalid RRCA from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_RUFC_REJECTED: RUFC received from remote domain [dec] is rejected: [chars]
Explanation Received invalid RUFC from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed : [chars]
Explanation Zone Server cannot stage zone configuration : [chars].
Recommended Action Verify the interoperability mode on all the switches.
Error Message ZONE-2-ZS_CHANGE_SFC_REJECTED: SFC received from remote domain [dec] is rejected: [chars]
Explanation Received invalid SFC from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_SMART_ZONING_POLICY_CHANGE_FAILED: Smart Zoning Policy Change Failed
Explanation Zone Server cannot distribute smart zoning policy change.
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_BY_NAME_FAILED: Stage activate zoneset by name failed on VSAN [dec]
Explanation Zone Server cannot stage activate zoneset by name on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_ENH_FAILED: Stage activate zone set enhanced failed on VSAN [dec]
Explanation Zone Server cannot stage activate zone set enhanced on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DEACTIVATE_ZSSET_ENH_FAILED: Stage deactivate zoneset enhanced failed on VSAN [dec]
Explanation Zone Server cannot stage deactivate zoneset enhanced on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_DFLT_ZONE_FAILED: Stage distribute default zone failed on VSAN [dec]
Explanation Zone Server cannot stage distribute default zone on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_ZS_DB_FAILED: Stage distribute zoneset database failed on VSAN [dec]
Explanation Zone Server cannot stage distribute zoneset database on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_MODE_FAILED: Stage set zoning mode failed on VSAN [dec]
Explanation Zone Server cannot stage set zoning mode on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_POLICIES_FAILED: Stage set zoning policies failed on VSAN [dec]
Explanation Zone Server cannot stage set zoning policies on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars]
Explanation Database operation is failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_DDAS_TABLE_CLEANUP_DUPLICATE_ENTRIES: Zone Device-alias table cleanup failed. Please try again. Do not initiate any Zone configuration commands until this command is successful.
Explanation Zone device-alias table cleanup failed due to error: [chars]
Recommended Action Please try again. Do not initiate any zone configuration command until this command is successful.
Error Message ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failed
Explanation [chars] (Export/Import) operation failed.
Recommended Action No action is required.
Error Message ZONE-2-ZS_FC2_DB_SIZE_LIMIT_EXCEEDED: [chars] Zone database size [dec] bytes exceeded maximum limit of [dec] bytes
Explanation Zone database size exceeded : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_FIPS_COMPLIANCE_FAILURE: FIPS compliance error: consecutively same random numbers
Explanation FIPS compliance error: consecutively same random numbers
Recommended Action No action is required.
Error Message ZONE-2-ZS_INIT_FAILED: [chars]
Explanation Zone Server initialization failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_LICENSE_UNAVAIL: License:[chars] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs
Explanation License:[char] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs.
Recommended Action No action is required.
Error Message ZONE-2-ZS_LIC_FAILURE: License [chars] operation failed for license [chars]
Explanation License [char] operation failed for license [char].
Recommended Action No action is required.
Error Message ZONE-2-ZS_LUN_DISABLING_FAILED: license expiry handling failed for VSAN [dec]
Explanation License expiry handling failed for VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_LUN_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of lun members exceeded
Explanation The number of lun members configured has exceeded the maximum number of lun members allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of lun members is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_MALLOC_FAILURE: Memory allocation failed for size [dec]
Explanation Memory allocation is failed for size [dec] bytes.
Recommended Action Restart the process.
Error Message ZONE-2-ZS_MEMBER_HARD_LIMIT_EXCEEDED: Maximum configurable unique zone member limit of [dec] reached. Creation of any more zone members is not supported
Explanation The number of members configured has exceeded the maximum number of members: [dec] allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of members is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_MEMBER_SOFT_LIMIT_REACHED: Zone member count has reached the maximum validated limit of [dec]. Creation of any more members could potentially destabilize the fabric.
Explanation The number of zone members configured has exceeded the validated number of members: [dec] allowed across all vsans Creation of any more zones could potentially destabilize the fabric.
Recommended Action Make sure the number of zone members is less than the validated limit allowed across all vsans.
Error Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding, isolating interface [chars]
Explanation Interface [chars] isolated due to adjacent switch not responding to Zone Server requests.
Recommended Action Flap the interface.
Error Message ZONE-2-ZS_MERGE_FAILED: Zone merge failure, isolating interface [chars] [chars]
Explanation Interface [chars] isolated due to zone merge failure. error [chars]
Recommended Action Compare active zoneset with the adjacent switch OR use "zone merge interface [interface] {import/export} VSAN [VSAN-num]" command.
Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars]
Explanation Full zoning databases are inconsistent between two switches connected by interface [chars]. Databases are not merged.
Recommended Action Compare full zoning database with the adjacent switch, correct the difference and flap the link.
Error Message ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface [chars]
Explanation Interface [chars] isolated due to unknown format in merge request.
Recommended Action Set the interoperability mode to same value on both switches.
Error Message ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed : [chars]
Explanation Zone Server MTS [chars] operation failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_NO_RSCN_ON_SW_CARD: Devices on Module [dec] will not be receiving RSCN as [chars]
Explanation Devices on Module [dec] will not be receiving RSCN as [chars].
Recommended Action Enable Zone Based RSCN
Error Message ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failed
Explanation Port swap operation failed.
Recommended Action No action is required.
Error Message ZONE-2-ZS_PSS_VER_MISMATCH: PSS version mismatch URL: [chars] (expected [chars], got [chars])
Explanation Configuration version mismatch. PSS URL [chars]. Expected version [chars], stored version [chars].
Recommended Action Upgrade/Downgrade to expected version.
Error Message ZONE-2-ZS_SHARED_DB_INIT_FAILED: [chars]
Explanation Zone Server shared DB initialization failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_TCAM_BROADCAST_ZONE_DISABLED: Broadcast zoning disabled : Reason: Hard zoning disabled
Explanation Broadcast zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Error Message ZONE-2-ZS_TCAM_LUN_ZONING_DISABLED: LUN zoning disabled : Reason: Hard zoning disabled
Explanation LUN zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Error Message ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: TCAM operation failed : [chars], Reason: [chars]
Explanation TCAM Programming failure has occurred : [chars]. [chars] is the reason for failure.
Recommended Action No action is required.
Error Message ZONE-2-ZS_TCAM_READ_ONLY_ZONE_DISABLED: Read-only zoning disabled : Reason: Hard zoning disabled
Explanation Read-only zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Error Message ZONE-2-ZS_TCAM_SWITCHED_TO_SOFT_ZONING_MODE: Switched to soft zoning : Reason: Hard zoning disabled
Explanation Switched to soft zoning : Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Error Message ZONE-2-ZS_VIRTUAL_DOMAIN_INCONSISTENT: IVR reporting virtual domain different from rib and domain manager in vsan [dec]
Explanation IVR reporting virtual domain different from rib and domain manager in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_ZONE_BASED_RSCN_DISABLED: Zone based RSCN Generation has been Disabled. Devices on non ISOLA line cards will not be receiving RSCN
Explanation Devices on one or more line cards will not be receiving RSCN as RSCN generation by zone has been disabled on this switch
Recommended Action No action is required.
Error Message ZONE-2-ZS_ZONE_HARD_LIMIT_EXCEEDED: Maximum configurable zone limit of [dec] reached. Creation of any more zones is not supported
Explanation The number of zones configured has exceeded the maximum number of zones: [dec] allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of zones is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_ZONE_SET_LIMIT_EXCEEDED: The limit for maximum number of zonesets exceeded
Explanation The number of zonesets configured has exceeded the maximum number of zonesets allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of zonesets is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_ZONE_SOFT_LIMIT_REACHED: Zone count has reached the maximum validated limit of [dec]. Creation of any more zones could potentially destabilize the fabric.
Explanation The number of zones configured has exceeded the validated number of zones: [dec] allowed across all vsans Creation of any more zones could potentially destabilize the fabric.
Recommended Action Make sure the number of zones is less than the validated limit allowed across all vsans.
Error Message ZONE-3-ZS_ACTIVATION_FAILED_DUE_TO_QOS_DISABLED: Activation failed due to qos not enabled
Explanation Activation of zoneset failed due to qos not enabled
Recommended Action Make sure qos is enabled and reactivate the zoneset in vsan.
Error Message ZONE-3-ZS_MGMT_SEC_SDB_ERR: [chars] : [chars]
Explanation FC CT Mgmt Security shared db operation : [chars] : [chars].
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.
Error Message ZONE-4-ZS_BROADCAST_LUN_WARNING: LUN member(s) and Broadcast attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur for LUN members.
Explanation Broadcast violations can happen in zone [chars] in vsan [dec] since it has LUN zone members.
Recommended Action No action is required.
Error Message ZONE-4-ZS_CHANGE_LC_UPGRADE_IN_PROGRESS: Change protocol request is received from domain [dec] when linecard upgrade is in progress
Explanation A change request has been received from domain [dec] when a linecard upgrade is in progress. The change request is rejected.
Recommended Action No action is required.
Error Message ZONE-4-ZS_DB_WARNING: [chars]
Explanation Database operation warning: [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_DOMAIN_MGR_WARNING: Unable to retrieve domain info from domain mgr error: [chars] in vsan [dec]
Explanation Unable to retrieve info of domain from domain manager, error: [chars] in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-4-ZS_FC2_OPER_FAILED: FC2 [chars] operation failed : [chars]
Explanation Zone Server FC2 [chars] operation failed : [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_IF_PORT_MODE_CONFLICT: Port mode conflict for if [chars]
Explanation Port mode conflict for if [chars]
Recommended Action Shutdown/no shutdown the interface
Error Message ZONE-4-ZS_INVALID_FPORT_WWN_MEMBER: Virtual device fwwn: [chars] is not a valid zone/alias member virtual name: [chars] pwwn: [chars]
Explanation Virtual device fwwn: [chars] is not a valid zone/alias member, virtual name: [chars] pwwn: [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_LC_UPGRADE_CHANGE_IN_PROGRESS: Linecard upgrade request is received when change protocol is in progress
Explanation A request for linecard upgrade has been received when change protocol is in progress. The linecard upgrade will occur after the completion of the change protocol.
Recommended Action No action is required.
Error Message ZONE-4-ZS_LICENSE_EXPIRY_WARNING: Feature [chars] evaluation license [chars] expiry in [dec] days
Explanation Feature [chars1] will exceed it's evaluation time period in [dec] days and will be shut down unless a permanent license [chars2] is installed.
Recommended Action Please install the license file to continue using the feature.
Error Message ZONE-4-ZS_MEMBER_CONVERSION_FAILED: Zone Member conversion failed for [chars]. Error: [chars]
Explanation Zone Member conversion has failed in : [chars] due to error: [chars]
Recommended Action No action is required.
Error Message ZONE-4-ZS_MGMT_SEC_RJT: FC CT Management Server query Rejected: [chars]. from FCID [hex]
Explanation Mgmt-security has rejected FC CT Management Server query: [chars]. from FCID [hex].
Recommended Action No action is required.
Error Message ZONE-4-ZS_NON_INTEROPERABLE_ZONE_SET: Non interoperable active zoneset present on VSAN [dec] in interoperability mode
Explanation Active zoneset has non interoperable members (FCID, FWWN, ..) when interoperability mode is turned on the VSAN [dec].
Recommended Action Turn off interoperability mode OR make sure that active zoneset has only interoperable members (PWWN).
Error Message ZONE-4-ZS_QOS_LUN_WARNING: LUN member(s) and QoS attribute are present in zone [chars] in vsan [dec]. QoS will not be applicable for LUN members.
Explanation QoS will not be applicable to LUN zone members in zone [chars] in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-4-ZS_SDV_VIRT_REAL_CONFLICT_WARNING: Virtual and Real devices are zoned together or zoned with same device. virtual name: [chars] pwwn: [chars]
Explanation Virtual and Real devices are zoned together or zoned with same device, virtual name: [chars] pwwn: [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_SMART_ZONING_AUTO_CONVERSION_FAILED: Smart Zoning auto conversion failed for [chars]. Error: [chars]
Explanation Smart Zoning auto conversion has failed in : [chars] due to error: [chars]
Recommended Action No action is required.
Error Message ZONE-4-ZS_SMART_ZONING_CLEAR_SMART_ZONING_CONFIG_FAILED: Clearing Smart Zoning config failed for [chars]. Error: [chars]
Explanation Clearing Smart Zoning config has failed in : [chars] due to error: [chars]
Recommended Action No action is required.
Error Message ZONE-4-ZS_TOO_MANY_ALIAS_IN_CURRENT_INTEROP_MODE: Too many aliases in current interoperability mode
Explanation Too many aliases configured in current interoperability mode on the VSAN. Due to this, the next zoneset activation, distribution or merge operation may fail.
Recommended Action Set the interoperability mode to appropriate value OR make sure the number of aliases is less than the maximum allowed in the current interoperability mode.
Error Message ZONE-4-ZS_UNSUPPORTED_MEMBER_IN_CURRENT_INTEROP_MODE: Unsupported member present in active or full zoneset in current interoperability mode
Explanation Active or full zoneset has members that are not supported in the current interoperability mode set on the VSAN.
Recommended Action Set the interoperability mode to appropriate value OR make sure that active or full zoneset has only supported members in the current interoperability mode.
Error Message ZONE-5-ZS_EXPORT_IMPORT_COMPLETE: [chars] operation completed
Explanation [chars] (Export/Import) operation completed.
Recommended Action No action is required.
Error Message ZONE-5-ZS_POLICY_CHANGE: Default zoning policy changed to [chars]
Explanation Default zoning policy changed to (permit/deny).
Recommended Action No action is required.
Error Message ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activated
Explanation Zoneset [chars] activated.
Recommended Action No action is required.
Error Message ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivated
Explanation Zoneset deactivated.
Recommended Action No action is required.
Error Message ZONE-6-ZS_CHANGE_ACA_REJECTED: ACA received from remote domain [dec] is rejected
Explanation Received invalid ACA from domain [dec]. Either the domain list do not match OR authorization has already been acquired by another switch.
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-6-ZS_FC2_OPER_INFO: FC2 [chars] operation failed : [chars]
Explanation Zone Server FC2 [chars] operation failed : [chars].
Recommended Action No action is required.
Error Message ZONE-6-ZS_INIT_PROCESS: Zone Server process started [chars] at [chars]
Explanation Zone Server process started in [chars] (stateless/stateful) mode at time [chars].
Recommended Action No action is required.
Error Message ZONE-6-ZS_INIT_WARNING: [chars]
Explanation Warning during Zone Server Initialization: [chars].
Recommended Action No action is required.
Error Message ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars]
Explanation Invalid member type [dec] [chars] recieved from the API call.
Recommended Action
Error Message ZONE-6-ZS_MGMT_SERVER_REQ: ZS received FC CT Mgmt Server [chars] Command code [hex], from FCID [hex].
Explanation FC CT request has been received from Managment Server. It is [chars]. Command code [hex], from FCId [hex]
Recommended Action No action is required.
Error Message ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars]
Explanation Zone Server received an event for an known licensing feature: [chars].
Recommended Action No action is required.