ACLLOG-5-ACLLOG_PKTLOG Format: %s

Explanation: New Acllog Packet Log: [chars]

Recommended Action: No action is required.

ARP-2-SET_SCHED Format: Failed to set policy or priority

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-INIT_FAIL Format: Initialization failure

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-SYSMGR_QUERY Format: Failed to query sysmgr for %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-SYSMGR_UUID Format: Failed to get uuid from sysmgr during %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-SYSMGR_NOTIFY Format: Bad notification from sysmgr for %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-SHM_ATTACH Format: Failed to attach %s shared memory

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-API_INIT Format: Failed to initialize %s API

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-API_INITIALIZE Format: Failed to initialize %s API with rc=0x%x, %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-SVR_REG Format: Failed to register as a client of %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-AM_REG Format: Failed to register as a client of AM %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-TIMERS_INIT Format: Failed to initialize timers

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-TIMER_SET Format: Failed to initialize new timer set

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-3-TIMER_RSTART Format: Failed to restart timer 0x%p for %s on %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-2-CLI_INIT Format: Failed to initialize CLI

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-THR_CREAT Format: Failed to create thread %s: error %d

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-THREAD_FAIL Format: Failed to start %s thread

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-3-API_MTS_INVAL Format: ARP API Error: Invalid ARP MTS queue in %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-API_MTS_SEND Format: ARP API Error: Failed to send %s to %s queue: %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-5-MQ_UNEXP Format: Received unexpected message (%d/%d) on %s queue

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-5-MQ_MINOR Format: Received unknown minor message type (%d) from %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-5-MSG_UNK Format: Received unknown % type: %lu

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-5-MTS_OPC_UNK Format: Received unknown MTS opcode %lu

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-2-MTS_OPC_SET Format: Failed to register with opcode %d: %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-MTS_BIND Format: Failed to do mts_bind for %s: %s

Explanation: An unrecoverable software error has occurred during arp initialization.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-MTS_RECV Format: MTS queue receive failed on %s queue: %s

Explanation: An unexpected fatal error has occurred.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-2-MTS_RECV_FAIL Format: %s as MTS queue receive failed: %s

Explanation: An unexpected fatal error has occurred.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ARP-3-MAC_ERR Format: Failed to get MAC address on %s for %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-ADJ_ADD Format: Failed to add adjacency for received packet from %s on %s

Explanation: Due to this failure, packet forwarding to this address will be affected until the next successful retrial.

Recommended Action: No user action is required.

ARP-3-ADJ_UPD Format: Failed to update adjacency for received packet from %s on %s

Explanation: Due to this failure, packet forwarding will continue to use the existing ARP adjacency entry values.

Recommended Action: No user action is required.

ARP-2-DUP_SRCIP Format: Source address of packet received from %s on %s is duplicate of local, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-2-DUP_SRC_IP Format: Source address of packet received from %s on %s(%s) is duplicate of local, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VADDR_SRCIP Format: Source address of packet received from %s on %s is duplicate of local virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VADDR_SRC_IP Format: Source address of packet received from %s on %s(%s) is duplicate of local virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VIRT_SRCIP Format: Source address of packet received from %s on %s is duplicate of local virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VIRT_SRC_IP Format: Source address of packet received from %s on %s(%s) is duplicate of local virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_SRCIP_PROBE Format: Duplicate address Detected. Probe packet received from %s on %s with destination set to our local ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_SRC_IP_PROBE Format: Duplicate address Detected. Probe packet received from %s on %s(%s) with destination set to our local ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VADDR_SRCIP_PROBE Format: Duplicate address Detected. Probe packet received from %s on %s with destination set to our local Virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-DUP_VADDR_SRC_IP_PROBE Format: Duplicate address Detected. Probe packet received from %s on %s(%s) with destination set to our local Virtual ip, %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-4-DIR_BCAST Format: %s address of packet received from %s on %s matches directed broadcast address, %s

Explanation: There may be a configured subnet mask-length mismatch among router interfaces connected on this LAN.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-4-INVAL_IP Format: Received packet with invalid %s IP address (%s) from %s on %s

Explanation: There may be a connected router sending packets with a bogus IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-4-INVAL_MAC Format: Received packet with invalid %s MAC address (%s) from %s on %s

Explanation: There may be a connected router sending packets with a bogus MAC address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-4-OWN_SRCMAC Format: Received packet with a local source MAC address (%s) from %s on %s

Explanation: There may be a connected router sending packets with local MAC address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-MBUF_ERR Format: Failed to get the remainder of packet, expected %d, got %d bytes

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-HDR_L2LEN_ERR Format: Received packet with incorrect layer 2 address length (%d bytes)

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-HDR_L3LEN_ERR Format: Received packet with incorrect layer 3 address length (%d bytes)

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-HDR_ERR Format: Failed to get ARP header, expected %d, got %d bytes

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-INVAL_HDR_HRD_TYPE Format: Found incorrect hardware type in ARP header: %hu

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-INVAL_HDR_PROT_TYPE Format: Found incorrect protocol type in ARP header: 0x%x

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-INVAL_STATE Format: Unrecognized ARP entry state in timer callback: %lu

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-4-DUP_IP Format: ARP entry found with duplicate IP address %s on %s

Explanation: There may be another router on this network that is configured with the same IP address.

Recommended Action: Check all routers on the interface for misconfiguration.

ARP-3-NO_MEM Format: Malloc failed for %s %s

Explanation: The system may be low on 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.

ARP-3-NO_MBUF Format: Failed to allocate buffer for %s

Explanation: The system may have run out of packet memory 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.

ARP-3-PKT_OUT Format: Failed to send packet to PM

Explanation: PM's message queue may be temporarily full.

Recommended Action: No user action is required.

ARP-3-MTS_DROP Format: MTS drop failed on %s queue: %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-REQ_IOD Format: Sending ARP request for %s on an invalid interface %u, request from pid: %d

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-REQ_NON_AM Format: Sending ARP request for %s on invalid interface %s request from pid: %d

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-REQ_IP Format: Sending ARP request for %s IP address %s on %s, request from pid: %d

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-REQ_ADD Format: Failed to add adjacency while sending request for %s on %s, request from pid: %d

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-GRAT_IOD Format: Sending gratuitous ARP for %s on an invalid interface %u

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-GRAT_NON_AM Format: Sending gratuitous arp for %s on invalid interface %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-GRAT_IP Format: Sending gratuitous ARP request for %s IP address %s on %s

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-IF_INDEX Format: Invalid interface index received from %d

Explanation: An unexpected but recoverable error has occurred.

Recommended Action: No user action is required.

ARP-3-IM_EXT Format: Couldn't set IM-extension for interface %s

Explanation: ARP process failed to set IM extension.

Recommended Action: No user action is required.

BGP-6-START Format: BGP process %s startup, reason: %s

Explanation: The indicated BGP process has started.

Recommended Action: No user action is required.

BGP-5-ADJCHANGE Format: neighbor %s %s %s

Explanation: A BGP session has just been established. Or a session has just been shutdown.

Recommended Action: No user action is required.

BGP-4-SLAB_HOLD Format: Not able to hold element from %s slab

Explanation:

Recommended Action: No user action is required.

BGP-6-EXIT_DECONFIG Format: BGP process exiting due to deconfiguration

Explanation: The indicated BGP process has been deconfigured.

Recommended Action: No user action is required.

BGP-6-EXIT_RESTART Format: BGP process exiting due to manual restart

Explanation: The indicated BGP process is being restarted.

Recommended Action: No user action is required.

BGP-6-EXIT_UNKNOWN Format: BGP process exiting due to unknown reason

Explanation:

Recommended Action: No user action is required.

BGP-5-SHUTDOWN Format: BGP protocol administratively shutdown

Explanation: BGP protocol was administratively shutdown.

Recommended Action: No user action is required.

BGP-5-NO_RD Format: VRF %s : RD deconfigured

Explanation: RD deconfigured from VRF.

Recommended Action: No user action is required.

BGP-6-MEMSTAT Format: Hit low memory condition - Free: %u MB, Min free: %u MB

Explanation:

Recommended Action: No user action is required.

BGP-6-PATH_MAXASLIMIT Format: [%s] Path for %s from peer %s found to %s the maxas-limit

Explanation:

Recommended Action: No user action is required.

BGP-4-AFIMPORT Format: %s prefixes imported from default vrf to %s vrf reached the limit %d

Explanation:

Recommended Action: No user action is required.

BGP-6-BADASPATH Format: Long AS path %s received from peer %s: more than configured maxas-limit %d

Explanation: The peer sent an AS path exceeding the maxas-limit.

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-6-MAXPEER_LIMIT Format: Reached maximum-peer limit on the prefix peer %s, ignoring connection request from %s

Explanation: Session can be brought up due to maximum-peer limit

Recommended Action: No user action is required.

BGP-6-AS4PATH_CONFED Format: Received AS4_PATH with CONFED related path segments in it from peer %s

Explanation: The peer has sent AS4_PATH with confed based path segments which would be discarded.

Recommended Action: No user action is required.

BGP-6-AS4PATH_SEGLEN Format: Received AS4_PATH with zero path segment length in it from peer %s

Explanation: The peer has sent AS4_PATH with zero path segment length which would be discarded.

Recommended Action: No user action is required.

BGP-6-AS4PATH_SEGTYPE Format: Received AS4_PATH with invalid path segment type in it from peer %s

Explanation: The peer has sent AS4_PATH with invalid path segment type which would be discarded.

Recommended Action: No user action is required.

BGP-6-AS4AGG_INVALID Format: Received AS4_AGGREGATOR with invalid length %d in it from peer %s

Explanation: The peer has sent AS4_AGGREGATOR with invalid attr length which would be discarded.

Recommended Action: No user action is required.

BGP-5-MEMALERT Format: BGP memory status changed from %s to %s

Explanation:

Recommended Action: No user action is required.

BGP-4-INVALIDIOD Format: Received interface(%s) %s notification from IM with zero iod

Explanation: BGP received an IF notification from IM with zero or invalid iod

Recommended Action: No user action is required.

BGP-3-RT_DB_ADD Format: Couldn't add route target %s into the database

Explanation: The router could not add route-target in its internal 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.

BGP-3-NEXTHOPADD Format: [%s] Couldn't add next-hop to RNHDB for %s/%d, error %d

Explanation: The router was unable to store a BGP next hop in an internal database, perhaps because it ran out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-NEXTHOPDEL Format: [%s] Couldn't delete next-hop from RNHDB for %s/%d, error %d

Explanation: An unexpected but handleable event has 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.

BGP-3-BRIBADD Format: [%s] Couldn't add dest to BRIB for %s

Explanation: BGP was unable to add a prefix to the BGP RIB. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-BRIB_ADD_INT Format: Internal error in adding to BRIB: %s

Explanation: An internal error was encountered in adding a path to the BRIB. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-BRIBDEL Format: [%s] Error %u deleting %s from BRIB

Explanation: An unexpected but handleable event has 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.

BGP-3-FINDAGGR Format: [%s] Did not find aggregate path for entry %s/%d

Explanation: BGP was unable to find an internal datastructure for originating a configured aggregate.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-AGGADD Format: [%s] Couldn't add aggregate for %s/%d

Explanation: BGP was unable to store an aggregate in an internal datastructure. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-AGGDEL Format: [%s] Couldn't delete aggregate for %s/%d

Explanation: An unexpected but handleable event has 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.

BGP-4-MAXPEERS Format: Trying to configure more than %d neighbors

Explanation: BGP has hit the limit of the number of peers that can. be configured.

Explanation: ACTION_KEEP_RUNNING

Recommended Action:

BGP-3-UNEXPPATHATTR Format: [%s] Unexpected attr (%p) path chain for %s

Explanation: An unexpected but handleable event has 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.

BGP-4-PFXEXCEED Format: [%s] No. of prefix received from %s exceeded configured limit %d

Explanation: A peer sent us more routes than BGP was configured to accept.

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-4-PFXWARN Format: [%s] Number of prefixes received from %s reached %d, maximum %d

Explanation: The number of routes sent to us by a peer exceeded the threshold at which BGP should generate a warning.

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-LIST Format: %s

Explanation: An internal software error has 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.

BGP-3-ATTRID_OP Format: Failed to %s attribute ID

Explanation: BGP was unable to allocate or free an index for a BGP PATH attribute block

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-ATTRAVL_OP Format: Failed attribute external database operation: %s, id %lu

Explanation: BGP was unable to perform an attribute external database 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.

BGP-3-VRF_CTX Format: VRF %s, failed %s

Explanation: An internal software error has 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.

BGP-3-VRFAVL_OP Format: Failed vrf database operation: %s, vrf %s id %lu

Explanation: BGP was unable to perform a vrf database 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.

BGP-3-TBLAVL_OP Format: Failed table database operation: %s, table %s id %#lx

Explanation: BGP was unable to perform a table database 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.

BGP-3-PEER Format: Peer %s, failed %s

Explanation: An internal software error has 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.

BGP-3-TBLCTX_INIT Format: VRF %s, %s, table %s: Table initialization failed

Explanation: BGP was unable to initialize an internal datastructure. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-BRIB_RDADD Format: [%s] Couldn't add rdinfo %s to BRIB

Explanation: BGP was unable to add a prefix to the BGP RIB. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-BRIB_RDDEL Format: [%s] Couldn't delete rdinfo %s from BRIB

Explanation: BGP was unable to remove from BGP RIB. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-TBLATTRAVL_OP Format: Failed table attribute database operation: %s, id %lu

Explanation: BGP was unable to perform a table attribute database 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.

BGP-3-RDINFO Format: VRF %s, %s, table %s: rdinfo %s failed

Explanation: BGP was unable to initialize an internal datastructure. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-BRIB_RDCLASH Format: VRF %s, %s: RD clash found during %s

Explanation: BGP was unable to allocate RD for the BGP RIB. The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-URIB_RT_MODIFY Format: URIB route modify operation failed during %s

Explanation: An internal software error has 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.

BGP-3-RPMHANDLE Format: RPM notification handle does not match existing handle for policy %s

Explanation: An unexpected but handleable event has 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.

BGP-3-RPMBIND Format: RPM policy bind failed for %s %s

Explanation: An unexpected but handleable event has 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.

BGP-3-PLCYOUT Format: Cannot add reference to policy out info for route-map %s

Explanation: BGP was not able to create an entry for an outbound policy.

Explanation: ACTION_SW_RESTART_COMP

Recommended Action:

BGP-3-PLCYRNHATTACH Format: Couldn't attach to policy RNH info for policy %s, error: %s

Explanation: An internal error occurred in using a policy. The system may be low on memory._MAYBE

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-PLCYRNHDETACH Format: Couldn't detach from policy RNH info for policy %s, error: %s

Explanation: An internal software error has 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.

BGP-3-PLCYRNHSETUP Format: Couldn't setup rnh notifications for policy %s, error: %s

Explanation: An internal error occurred in using a policy. The system may be low on memory._MAYBE

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-NETWKRNHSETUP Format: Couldn't setup rnh notifications for network %s, error: %s

Explanation: Could not setup RNH for network prefix

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-CLISET Format: Unable to set %s inheritance for %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-DAMPCFG Format: Both policy and global dampconf exist

Explanation: An internal software error has 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.

BGP-3-ACLTESTADD Format: Failed to add %s peer policy test

Explanation: An internal software error has 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.

BGP-3-RPM_L3VPN_EXTCOMM Format: L3vpn extcommunity failure during %s

Explanation: An unexpected but handleable event has 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.

BGP-4-MQUNEXPECT Format: Recieved unexpected message (%d/%d) on %s queue

Explanation: An unexpected but handleable event has 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.

BGP-2-MTSBIND Format: Unable to bind to MTS SAP for %s, sap %d: %s

Explanation: BGP was not able to create a message queue for communication.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-4-MTSUNKOPC Format: Recieved unknown MTS message on %s queue, opc %d

Explanation: An unexpected but handleable event has 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.

BGP-4-MTSNOMSG Format: No MTS payload found on %s queue, opc %d

Explanation: An unexpected but handleable event has 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.

BGP-3-MTSRECV Format: MTS receive failed on %s queue: %s

Explanation: An unexpected but handleable event has occured.

Recommended Action: No user action is required.

BGP-3-MTSDROP Format: MTS drop failed on %s queue: %s

Explanation: An unexpected but handleable event has 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.

BGP-3-MTSSEND Format: MTS send() error to SAP %d, opcode %d: %s

Explanation: An unexpected but handleable event has 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.

BGP-4-TXLIST Format: %s

Explanation: An unexpected but handleable event has 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.

BGP-3-API_UNEXP_RESP Format: Received unexpected message from SAP %d, opcode %d, address %s, ignore it

Explanation: An unexpected but handleable event has occured.

Recommended Action: No user action is required.

BGP-2-APIMTSBIND Format: Unable to bind to MTS SAP for %s, sap %d: %s

Explanation: BGP client was not able to create a message queue for communication.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-APIMTSRECV Format: MTS receive failed on %s queue: %s

Explanation: An unexpected but handleable event has occured.

Recommended Action: No user action is required.

BGP-3-APIMTSDROP Format: MTS drop failed on %s queue: %s

Explanation: An unexpected but handleable event has 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.

BGP-3-APIMTSSEND Format: MTS send() error to SAP %d, opcode %d: %s

Explanation: An unexpected but handleable event has 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.

BGP-4-APIMTSNOMSG Format: No MTS payload found on %s queue, opc %d

Explanation: An unexpected but handleable event has 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.

BGP-3-APIASSERT Format: %s:%d: Assertion `%s' failed.

Explanation: An internal software error has 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.

BGP-2-APIINIT Format: Unable to initialize %s API

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-ATTACH Format: Unable to attach to %s

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-URIBREG Format: Unable to register with URIB for [afi/safi:%d/%d]

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-ULIBREG Format: Unable to register with ULIB

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-URIBRNH Format: URIB RNH error: %s

Explanation: An internal software error has 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.

BGP-3-U6RIBRNH Format: U6RIB RNH error: %s

Explanation: An internal software error has 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.

BGP-3-ULIBRNH Format: ULIB RNH error: %s

Explanation: An internal software error has 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.

BGP-3-RNHCB Format: RNH %s error: %s

Explanation: An internal software error has 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.

BGP-3-URIBRT Format: URIB RT error: %s

Explanation: An internal software error has 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.

BGP-2-SRVREG Format: Unable to register with %s

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-AFINIT Format: Error initializing address family, (%d)

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-AFINITFUNCS Format: Error initializing address family function vectors, (%d)

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-IPV6REG Format: Unable to register with IPv6

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-U6RIBREG Format: Unable to register with U6RIB for [afi/safi:%d/%d]

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-TSP_INIT Format: Unable to initialize with TSP

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-SUPSTATE Format: Error in learning SUP state

Explanation: An internal software error has 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.

BGP-3-RESTARTTYPE Format: Error in learning restart type

Explanation: An internal software error has 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.

BGP-2-SYSMGR_QUERY Format: Failed to query sysmgr for %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-SYSMGR_CONDVERIF Format: Sysmgr conditional verify failed

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-LISTEN_SOCK Format: Failed to listen on %s BGP TCP port

Explanation: An error occured during a socket operation.OR

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-SOCK_ERR Format: Socket (%d/%d): %s\n

Explanation: An error occured during a socket operation.OR

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-SOCKOPEN Format: TCP connection for peer %s already open, fd %d, state %s

Explanation: An internal software error has 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.

BGP-3-SOCKCREATE Format: Cannot create socket for peer %s: %s, stats: %lu/%lu/%lu/%lu/%lu

Explanation: An error occured during a socket 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.

BGP-3-SOCKBIND Format: Cannot bind local socket for peer %s: %s

Explanation: An error occured during a socket 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.

BGP-3-SOCK_ACCEPT Format: Socket (%d/%d) accept: %s\n

Explanation: An error occured during a socket operation.OR

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-SOCKNONBLOCK Format: Couldn't make fd %d non-blocking: %s

Explanation: An error occured during a socket 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.

BGP-3-SENDBUF Format: Error manipulating sendbuf: %s

Explanation: An internal software error has 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.

BGP-3-NEGWRITE Format: Negative nr of %d bytes left to write to peer %s

Explanation: An internal software error has 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.

BGP-3-MD5PASS Format: Cannot set MD5 password %s for peer %s

Explanation: An internal software error has 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.

BGP-3-EBGPTTL Format: Unable to set EBGP TTL for peer %s, fd %d

Explanation: An unexpected but handleable event has 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.

BGP-3-IPTOS Format: Unable to set IP TOS bits for %s, fd %d

Explanation: An unexpected but handleable event has 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.

BGP-3-SOCK_FDPOP Format: Unexpected error during socket fd population %s(%d)

Explanation: An unexpected but handleable event has 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.

BGP-3-SOCK_RECV Format: Unexpected error during socket data recv %s(%d)

Explanation: An unexpected but handleable event has 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.

BGP-3-LOWMEM Format: Low on heap memory

Explanation: The system may be low on 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.

BGP-2-PEERSHALTED Format: BGP %s shutdown due to no memory condition (%s)

Explanation: The system may be low on 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.

BGP-3-ALLOCFAIL Format: %s malloc (%ld) failed for: %s

Explanation: The system may be low on 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.

BGP-3-PFX_NOMEM Format: Could not allocate %s for %s/%d

Explanation: The system may be low on 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.

BGP-3-NOMEMORY Format: Could not allocate %s

Explanation: The system may be low on 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.

BGP-3-NOBUF Format: [%s] Unable to get buffer for %s msg to peer %s

Explanation: An internal software error has 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.

BGP-1-FATAL Format: Fatal error: %s: %s

Explanation: An unexpected fatal error has occured.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-1-UNKNOWNFATAL Format: Unknown fatal error %d: %s

Explanation: An unexpected fatal error has occured.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-2-PTHREAD Format: procket_pthread_create failed for %s: error %d

Explanation: An unexpected fatal error has occured.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-5-BADSIG Format: Should not have received signal %d

Explanation: An unexpected but handleable event has occured.

Recommended Action: No user action is required.

BGP-3-ILLARGS Format: %s called with illegal arguments

Explanation: An internal software error has 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.

BGP-4-NODAMPMEM Format: [%s] Unable to dampen prefix %s from peer %s due to no memory

Explanation: The system may be low on memory.ORY

Recommended Action: No user action is required.

BGP-3-INTERNAL Format: Internal error %d: %s

Explanation: An internal software error has 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.

BGP-3-NBRERR Format: %s Peer error: %s

Explanation: An internal software error has 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.

BGP-3-ASSERT Format: %s:%d: Assertion `%s' failed.

Explanation: An internal software error has 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.

BGP-3-UNEXPECT Format: %s L%d: %s

Explanation: An internal software error has 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.

BGP-3-PATH_DEL Format: Failed to destroy path (%s), error %d

Explanation: The BGP process may have run out of memory.

Recommended Action: If BGP ran out of memory, add memory to the router or change the network configuration to decrease memory requirements. Clear any BGP peers that may have been shut down automatically. If BGP has memory available, there was an internal error, restart BGP.

BGP-3-TIMER_START Format: Couldn't start %s timer %s

Explanation: An internal software error has 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.

BGP-3-THREAD_SHUTDOWN Format: Problem shutting down thread %s: Operation - %s, Error - %s\n

Explanation: An unexpected but handleable event has 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.

BGP-2-MQLOOP_INIT Format: Message queue loop %s, %s, Error - %s

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-MQLOOP_SHUTDOWN Format: Couldn't shut down %s message queue loop

Explanation: An unexpected but handleable event has 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.

BGP-3-APPLY_BESTPATH_CFG Format: Failed to apply bestpath configuration: %s

Explanation: An unexpected but handleable event has 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.

BGP-3-RESTARTINIT Format: Unable to determine restart status and initialize

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-PATH_STALE Format: [%s] %s path being %s, for %s from peer %s, should not be stale

Explanation: An internal software error has 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.

BGP-3-SRAND Format: Failed to set random seed

Explanation: An unrecoverable error has occured during BGP initialization.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

BGP-3-EVENT_WAIT Format: Error while waiting for %s event, error - %s\n

Explanation: An unexpected but handleable event has 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.

BGP-4-RLIMIT Format: Error while setting rlimit, error - %s\n

Explanation: An unexpected but handleable event has occured.

Recommended Action: No user action is required.

BGP-4-NORID Format: Peer %s sent us 0.0.0.0 as its router-id

Explanation: A BGP peer sent us an invalid router id.

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-4-SAMERID Format: Peer %s uses same routerid as us

Explanation: A BGP peer is using the same router id as this router.

Recommended Action: Configure either the local or remote router with a different router ID.

BGP-3-INVHDR Format: Peer %s sent unexpected header pattern

Explanation: The marker pattern in message header was invalid

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADPEERAS Format: VRF %s, Peer %s - bad remote-as, expecting %s received %s.

Explanation: The peer sent an incorrect AS Number

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADOPENCAP Format: VRF %s, Peer %s - bad capability code received %u.

Explanation: The peer sent a bad/unknown capability

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADOPENPARAM Format: VRF %s, Peer %s - unknown optional parameter received %u.

Explanation: The peer sent an unknown optional parameter

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADLOCALAS Format: VRF %s, Peer %s - bad AS sent in Open message %u.

Explanation: The peer received an incorrect AS Number

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADPEERHOLDTIME Format: VRF %s, Peer %s - bad hold time %s %d.

Explanation: The peer sent and/or received an incompatible hold time

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADPEERRID Format: VRF %s, Peer %s - bad router-id %s %s.

Explanation: The peer sent and/or received a bad router-id

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-BADPEERDYNAS Format: VRF %s, Peer %s - bad remote-as, failed route-map %s received %s.

Explanation: The peer sent an AS Number that did not match route-map

Recommended Action: Check that the peering router is configured correctly. Clear the peer if necessary after any change.

BGP-3-IMPORT_VRF_EXCEED Format: Maximum limit on number of import VRFs exceeded

Explanation: An unexpected but handleable event has 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.

BGP-3-BADNEXTHOP Format: [%s] Peer %s advertised non-mapped nexthop %s in MP reach attr [afi/safi:%d/%d], dropping NLRI

Explanation: The router received a next-hop that was inconsistent with the address-family in the update 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.

BGP-5-MAXMSGLIMIT Format: [%s] Failed to send update message with prefix %s for peer %s because the msg size(%u) exceeded the maximum limit(%u)

Explanation: BGP Update message reached the maximum limit

Recommended Action: No user action is required.

BGP-3-ASPREPEND Format: Expected AS sequence or entry sequence, got %d/%d

Explanation: An error was encountered in prepending to an AS path.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-COMLEN Format: Community sets exceeded maximum allowed limit

Explanation: An internal limit was hit in adding a community.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-4-EXTCOMLEN Format: Extended communities exceeded the max limit of %u

Explanation: An internal limit was hit in adding an extended community.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-COMADD Format: Error occurred in community addition, no action taken

Explanation: An internal error was encountered in adding a community.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-EXTCOMADD Format: Error occurred in extended community addition, no action taken

Explanation: An internal error was encountered in adding an extended community.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-ASLEN Format: AS-PATH prepend length exceeds internal limit

Explanation: An internal limit was hit in prepending and AS path.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

BGP-3-SOFTINCAP Format: Peer %s not capable of soft refresh in, operator intervention needed: %s

Explanation: The router is unable to do soft refresh for the indicated peer.

Recommended Action: If necessary, reset the connection with the peer.

BGP-3-SNMP_API_DATA Format: Message data is NULL

Explanation: SNMP message does not have memory to store data.

Recommended Action: No user action is required.

BGP-3-CONDSRV_CLEANUP Format: Conditional Service cleanup request failed, %s

Explanation: Sysmgr rejected BGP's request to shut down.

Recommended Action: No user action is required.

BGP-4-SNMP_REGFAIL Format: Failed to register MIB with the SNMP agent, the BGP MIB will be unavailable. (%s)\n

Explanation: MIB registration failed during startup.

Recommended Action: No user action is required.

BGP-4-SNMP_DEREGFAIL Format: Failed to deregister MIB with the SNMP agent (%s).\n

Explanation: MIB deregistration failed during shutdown.

Recommended Action: No user action is required.

BGP-3-FEATURE_STATUS Format: FM status for feature %s failed with error: %s(0x%08x).\n

Explanation: FM get feature status failed

Recommended Action: No user action is required.

BGP-3-URIB_API Format: URIB API %s() failed\n

Explanation: URIB API had failed

Recommended Action: No user action is required.

BGP-3-CONFCHECK Format: confcheck API %s() failed with error: %s(0x%08x).\n

Explanation: confcheck API has failed

Recommended Action: No user action is required.

BGP-7-OBJSTORE Format: Objstore API %s() failed with error: %d\n

Explanation: Objstore API has failed

Recommended Action: No user action is required.

BIOS_DAEMON-LC-2-BIOS_DAEMON_LC_ERROR Format: BIOS Sector (%d) is write protected

Explanation: BIOS WRITE PROTECTED

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

BIOS_DAEMON-2-BIOS_DAEMON_SUP_ERROR Format: BIOS Sector (%d) is write protected

Explanation: BIOS WRITE PROTECTED

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

BIOS_DAEMON-2-BIOS_DAEMON_FLASH_WARNING Format: Flash chip not supported by running image. Skipping bios upgrade.

Explanation: BIOS CHIP NOT SUPPORTED

Recommended Action: No action is required.

BIOS_DAEMON-LC-2-BIOS_DAEMON_LC_PRI_BOOT_FAIL Format: System booted from Alternate BIOS Flash

Explanation: Boot from Alternate

Recommended Action: No action is required.

BIOS_DAEMON-LC-5-BIOS_DAEMON_LC_PRI_BOOT Format: System booted from Primary BIOS Flash

Explanation: Boot from Primary

Recommended Action: No action is required.

BIOS_DAEMON-2-BIOS_DAEMON_PRI_BOOT_FAIL Format: System booted from Alternate BIOS Flash

Explanation: Boot from Alternate

Recommended Action: No action is required.

BIOS_DAEMON-5-BIOS_DAEMON_PRI_BOOT Format: System booted from Primary BIOS Flash

Explanation: Boot from Primary

Recommended Action: No action is required.

CRDCLIENT-3-CARDCL_ERR Format: %s

Explanation: CardClient Error

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCLIENT-2-CARDCL_CRIT Format: %s

Explanation: CardClient Critical Message

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCLIENT-2-SSE Format: %s

Explanation: CardClient Console Message

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCLIENT-2-REG Format: %s

Explanation: CardClient Console Message

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCLIENT-LC-2-IMG_ERR Format: %s

Explanation: CardClient Remote Syslog msg

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCLIENT-LC-2-ERR Format: %s

Explanation: CardClient Remote Syslog msg

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CDPD-2-INITFAIL Format: CDP Daemon Initialization failed: %s

Explanation: CDP Daemon Initialization failed. [chars] explains the reason for the failure.

Recommended Action: No action is required.

CDPD-3-ALLOCFAIL Format: Heap Memory allocation failed: %s

Explanation: CDP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action: No action is required.

CDPD-3-MTSERROR Format: %s

Explanation: CDP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action: No action is required.

CDPD-3-PSSERROR Format: %s

Explanation: CDP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.

Recommended Action: No action is required.

CDPD-3-GENERROR Format: %s

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.

CDPD-3-PKTRECVFAIL Format: Failed to receive packet - %s

Explanation: Failed to receive packet. [char] identifies the reason.

Recommended Action: No action is required.

CDPD-3-PKTSENDFAIL Format: Failed to send packet, interface 0x%x - %s

Explanation: Failed to send packet. [dec] identifies the interface [char] identifies the reason.

Recommended Action: No action is required.

CDPD-6-CDPDUP Format: 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.

CDPD-6-PORTUP Format: A CDP enabled port %s 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.

CDPD-6-PORTDOWN Format: A CDP enabled port %s 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.

CDPD-6-PORTENABLE Format: CDP enabled on port %s

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.

CDPD-6-PORTDISABLE Format: CDP disabled on port %s

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.

CDPD-6-CDPEXIT Format: CDP Daemon shutting down gracefully.

Explanation: CDP Daemon is shutting down gracefully. This is an informational message.

Recommended Action: No action is required.

CDPD-5-ENABLED Format: CDP is enabled

Explanation: CDP is enabled on the device.

Recommended Action: No action is required.

CDPD-5-DISABLED Format: CDP is disabled

Explanation: CDP is disabled on the device.

Recommended Action: No action is required.

CDPD-5-NEIGHBOR_ADDED Format: Device %s discovered of type %s with port %s on incoming port %s with ip addr %s and mgmt ip %s

Explanation: Discovered a neighbor device. This is an informational message.

Recommended Action: No action is required.

CDPD-5-NEIGHBOR_REMOVED Format: CDP Neighbor %s on port %s has been removed

Explanation: Deleted a neighbor device. This is an informational message.

Recommended Action: No action is required.

CDPD-4-DUPLEX_MISMATCH Format: Duplex mismatch discovered on %s, with %s

Explanation: duplex mismatch discovered from the received cdp packet This is a warning message.

Recommended Action: No action is required.

CDPD-4-NATIVE_VLAN_MISMATCH Format: Native VLAN mismatch discovered on %s(%d), with %s(%d)

Explanation: Native VLAN mismatch discovered This is a warning message.

Recommended Action: No action is required.

CDPD-3-CDPD_INTERNAL_ERROR Format: CDP internal error: %s

Explanation: Internal error is encountered

Recommended Action: No action is required.

CDPD-3-ISTACKREGISTER Format: Failed to register istack - %s

Explanation: Failed to register istack. [char] identifies the reason.

Recommended Action: No action is required.

CRDCFG-3-CRDCFG_ERR Format: %s

Explanation: CardConfig error mesage

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCFG-3-CRDCFG_SRV_ERR Format: %s

Explanation: CardConfigServer error mesage

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

CRDCFG-LC-2-CONFIG_ERR Format: %s

Explanation: CardConfig Failed to find matching cardid, pnum in database

Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.

DC3_SENSOR-3-DC3_SENSOR_MSG1 Format: %s

Explanation: SENSOR log message

Recommended Action: No action is required.

DEVICE_TEST-2-MALLOC_FAILURE Format: "Memory allocation failed"

Explanation: Device Test process could not allocate memory

Recommended Action: No action is required.

DEVICE_TEST-4-THREAD_CREATE_FAIL Format: "Thread creation failed"

Explanation: Device Test process could not create threads

Recommended Action: No action is required.

DEVICE_TEST-3-STANDBY_TEST_INIT_FAIL Format: "Init for standby test failed due to error %x")msgdef_explanation("Device Test StandbyFabricLoopback Test failed init process"

Recommended Action: No action is required.

DEVICE_TEST-3-STANDBY_TEST_MTS_FAIL Format: "Mts Init for standby test failed due to error %x")msgdef_explanation("Device Test StandbyFabricLoopback Test failed mts init"

Recommended Action: No action is required.

DEVICE_TEST-3-STANDBY_TEST_GET_SPINE_FAIL Format: "Standby test get spines failed due to error %x")msgdef_explanation("Device Test StandbyFabricLoopback Test get spine failed"

Recommended Action: No action is required.

DEVICE_TEST-3-STANDBY_TEST_GET_DIAG_VQI_FAIL Format: "Standby test get diag vqi failed due to error %x")msgdef_explanation("Device Test StandbyLoopback Test failed get vqi"

Recommended Action: No action is required.

DEVICE_TEST-3-STANDBY_TEST_SOCKET_FAIL Format: "Standby test socket error %s: %x")msgdef_explanation("Device Test StandbyFabricLoopback Test Socket error"

Recommended Action: No action is required.

DEVICE_TEST-5-LC_TEST_PASS Format: Module-id(%d): %s has completed successfully

Explanation: Test on this particular LineCard completed successfully

Recommended Action: No action is required.

DEVICE_TEST-5-LC_TEST_FAIL Format: Module-id(%d): %s has failed

Explanation: Test on this particular LineCard failed

Recommended Action: No action is required.

DEVICE_TEST-5-TEST_FAILURE_EXCESS Format: "Module-id(%d): %s has failed more %d times"

Explanation: A test has failed more than configured allowed limit

Recommended Action: No action is required.

DEVICE_TEST-5-RT_PSS_OP_FAILURE Format: "DiagClient PSS operation failed"

Recommended Action: No action is required.

DEVICE_TEST-2-ASIC_REG_CHECK_FAIL Format: Module %d has failed test %s %d times on device %s %s %d %s due to error %s

Explanation: Online diagnostics ASICRegisterCheck test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-USB_FAIL Format: Module %d has failed test %s %d times on device USB due to error %s

Explanation: Online diagnostics USB test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-NVRAM_FAIL Format: Module %d has failed test %s %d times on device NVRAM due to error %s

Explanation: Online diagnostics NVRAM test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-RTC_FAIL Format: Module %d has failed test %s %d times on device RealTimeClock due to error %s

Explanation: Online diagnostics RealTimeClock test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-PRIMARY_BOOTROM_FAIL Format: Module %d has failed test %s %d times on device Primary BootROM due to error %s

Explanation: Online diagnostics PrimaryBootROM test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-SPINE_CONTROL_BUS_FAIL Format: Module %d has failed test %s %d times on device Spine Control Bus on slot %d due to error %s error number 0x%08X

Explanation: Online diagnostics SpineControlBus test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-POWER_SUPPLY_FAIL Format: Module %d has failed test %s %d times on System Mgmt Bus for chassis %s instance %d due to error %s error number 0x%08X

Explanation: Online diagnostics SystemMgmtBus test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-FAN_MOD_FAIL Format: Module %d has failed test %s %d times on System Mgmt Bus for chassis %s instance %d due to error %s error number 0x%08X

Explanation: Online diagnostics SystemMgmtBus test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-TWOWIRE_STW_FAIL Format: Module %d has failed test %s %d times on Status Bus on slot %d due to error %s

Explanation: Online diagnostics Status bus test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-STANDBY_LOOPBACK_TEST_FAIL Format: Module %d has failed test %s %d times on %s %d due to error %s

Explanation: Online diagnostics StandbyFabricLoopback test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-MGMT_PORT_SKIP Format: Module %d has skipped test %s on Management Port due to error %s

Explanation: Online diagnostics ManagementPort test is skipped

Recommended Action: No action is required.

DEVICE_TEST-2-EOBC_FAIL Format: Module %d has failed test %s on EOBC due to error %s

Explanation:

Recommended Action:

DEVICE_TEST-2-EPC_FAIL Format: Module %d has failed test %s on EPC due to error %s

Explanation: Online diagnostics EOBC test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-OBFL_FAIL Format: Module %d has failed test %s %d times on device OBFL due to error %s

Explanation: Online diagnostics OBFL test has failed

Recommended Action: No action is required.

DEVICE_TEST-2-EPC_EOBC_SWITCH_FAIL Format: %s switch device %d diag failed. Port bitmap 0x%x, Pass bitmap 0x%x

Explanation: Bootup diagnostics test on EPC/EOBC switch failed

Recommended Action: No action is required.

DHCP_SNOOP-2-INITFAIL Format: DHCP Daemon Initialization failed: %s

Explanation: DHCP Daemon Initialization failed. [chars] explains the reason for the failure.

Recommended Action: No action is required.

DHCP_SNOOP-2-REGPARTREE Format: Unable to register par tree: %s

Explanation: Could not register par tree. [chars] explains the reason for the failure.

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_SNOOP_PROGRAM_EXIT Format: %s

Explanation: DHCP snoop process did an abnormal exit

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_DISCOVER_START Format: DHCP client Discover phase started

Explanation: DHCP client Discover phase started

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_DISCOVER_START_INTF_LIST Format: DHCP client discover phase started list of interfaces

Explanation: DHCP client discover phase started list of interfaces

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_REQUEST_START_INTF_LIST Format: DHCP client request phase started list of interfaces

Explanation: DHCP client request phase started list of interfaces

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_REQUEST_START Format: DHCP client starts from Request phase directly

Explanation: DHCP client starts from Request phase directly

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_FAILURE Format: DHCP client failed

Explanation: DHCP client failed

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_CLIENT_INFO Format: %s

Explanation: DHCP client info

Recommended Action: No action is required.

DHCP_SNOOP-2-DHCP_DISCOVER_RECVD_NAK Format: Received DHCP NAK

Explanation: Received DHCP NAK

Recommended Action: No action is required.

DHCP_SNOOP-3-MTSERROR Format: %s

Explanation: DHCP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action: No action is required.

DHCP_SNOOP-3-SOCKOPENFAIL Format: Failed to open socket for receiving DHCP packets - %s

Explanation: An attempt to open a socket for receiving DHCP packets failed. [char] identifies the reason.

Recommended Action: No action is required.

DHCP_SNOOP-3-SOCKBINDFAIL Format: Failed to bind to raw socket - %s

Explanation: Failed to bind to socket. [char] identifies the reason.

Recommended Action: No action is required.

DHCP_SNOOP-3-PKTRECVFAIL Format: Failed to receive packet - %s

Explanation: Failed to receive packet. [char] identifies the reason.

Recommended Action: No action is required.

DHCP_SNOOP-3-PKTDROP Format: Packet dropped. Reason - %s

Explanation: Dropping the packet. [char] identifies the reason.

Recommended Action: No action is required.

DHCP_SNOOP-3-PKTSENDFAIL Format: Failed to send packet, - %s

Explanation: Failed to send packet. [char] identifies the reason.

Recommended Action: No action is required.

DHCP_SNOOP-3-INVDHCPPKTS Format: Validation errors while processing DHCP packet received on interface %s vlan %d Reason:%s. Dropping the packet

Explanation: Validation errors DHCP packet receieved on the interface [chars] vlan [%d]. Reason:[chars]

Recommended Action: No action is required.

DHCP_SNOOP-6-DHCPUP Format: 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.

DHCP_SNOOP-6-OPT82INSTFAIL Format: %s %s

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.

DHCP_SNOOP-6-DHCPEXIT Format: DHCP Daemon shutting down gracefully.

Explanation: DHCP Daemon is shutting down gracefully. This is an informational message.

Recommended Action: No action is required.

DHCP_SNOOP-6-NONDHCPPKTFWD Format: Non DHCP packet with src port:%d dst port:%d on intf:%s vlan:%d. Forwarding on %s

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.

DHCP_SNOOP-6-DHCPPKTFWD Format: Gracefully forwarding DHCP packet. Reason: %s

Explanation: Gracefully forwarding DHCP packet. reason [chars]

Recommended Action: No action is required.

DHCP_SNOOP-3-ASSERTION_FAILED Format: %s:%d

Explanation: DHCP Snoop process has hit an assert condition at file [chars] line number [dec]

Recommended Action: No action is required.

DIAGCLIENT-5-CALLOC_FAILURE Format: Memory allocation failed

Explanation: DiagClient process could not allocate memory

Recommended Action: No action is required.

DIAGCLIENT-3-ONDEMAND_FAIL_EXCESS Format: Module \ Test \ has failed more than \ 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

DIAGCLIENT-5-ONDEMAND_SUCCESS Format: Module \ Test \ has completed successfully in Test_Iteration \

Explanation: The specified test has reported SUCCESS in this Iteration

Recommended Action: No action is required.

DIAGCLIENT-5-ONDEMAND_FAIL Format: Module \ Test \ has failed in Test_Iteration \

Explanation: The specified test has reported FAILURE in this Iteration

Recommended Action: No action is required.

DIAGCLIENT-7-DIAG_HM_FAIL Format: Module \ Health Monitoring Test \ has failed. Please use 'show diagnostic result \' to see test results

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.

DIAGCLIENT-7-PER_PORT_TEST_FAIL Format: PORT_LIST */ "Module \ Test \ has failed on Ports \ Please use 'show diagnostic result \' to see test results"

Explanation: Per Port Test has failed on the above all ports

Recommended Action: No action is required.

DIAGCLIENT-4-MTS_SEND_FAILURE Format: MTS send failed, mts_opc: %s, dest slot: %u, dest SAP: %d, error-id: 0x%x

Explanation: MTS send reports failure

Recommended Action: No action is required.

DIAGCLIENT-2-PSS_WRITE_FAILURE Format: /* MODULE_ID */ "Write to PSS failed on Module \"

Explanation: Write operation on PSS store failed

Recommended Action: No action is required.

DIAGCLIENT-2-PSS_READ_FAILURE Format: /* MODULE_ID */ "Read from PSS failed on Module \"

Explanation: Read operation from PSS store failed

Recommended Action: No action is required.

DIAGCLIENT-4-LC_OFFLINE_FOR_CURR_SLOT Format: Received LC offline event for the current slot:%d. Ignoring it

Explanation: Informational Syslog

Recommended Action: No action is required.

DIAGCLIENT-5-DIAG_ONDEMAND_TEST_START Format: Module %d: Ondemand test %s started

Explanation: Informational Syslog

Recommended Action: No action is required.

DIAGCLIENT-5-DIAG_ONDEMAND_TEST_STOP Format: Module %d: Ondemand test %s stopped

Explanation: Informational Syslog

Recommended Action: No action is required.

DIAGCLIENT-5-DIAG_ONDEMAND_TEST_FINISH Format: Module %d: Ondemand test %s finished

Explanation: Informational Syslog

Recommended Action: No action is required.

DIAGMGR-5-CALLOC_FAILURE Format: Memory allocation failure

Explanation: Memory allocation in a call to malloc/calloc has failed

Recommended Action: No action is required.

DIAGMGR-5-BOOTUP_CONF Format: /*COMPLETE/BYPASS*/ "Diagnostic Bootup Level: \"

Explanation: Current Diagnostic BootUp Level being configure or changed

Recommended Action: No action is required.

DIAGMGR-2-MTS_SEND_FAILURE Format: MTS send failed, mts_opc: %s, dest slot: %d, dest SAP: %d, error-id: 0x%x

Explanation: MTS send reports failure

Recommended Action: No action is required.

DIAG_PORT_LB-5-DIAG_PORT_LB_ENABLED Format: DIAG_PORT_LB Enabled

Explanation: DIAG_PORT_LB Service nabled

Recommended Action: No action is required.

DIAG_PORT_LB-5-DIAG_PORT_LB_DISABLED Format: DIAG_PORT_LB Disabled

Explanation: DIAG_PORT_LB Service Disabled

Recommended Action: No action is required.

DIAG_PORT_LB-2-MALLOC_FAILURE Format: %s(%d) Memory allocation failed.

Explanation: Port Loopback test process could not allocate memory

Recommended Action: No action is required.

DIAG_PORT_LB-3-PIXM_LIB_ERROR Format: %s(%d) Failed to convert %s:%x to %s. Error:%s

Explanation: Port Loopback test process failed to convert port ifindex \ port index.

Recommended Action: No action is required.

DIAG_PORT_LB-3-PORT_CLIENT_LIB_ERROR Format: %s(%d) %s. Error:%s

Explanation: Port Loopback test process failed in Port Client API.

Recommended Action: No action is required.

DIAG_PORT_LB-4-MTS_LIB_ERROR Format: %s(%d) %s. Warning:%s

Explanation: Port Loopback test process failed in MTS API.

Recommended Action: No action is required.

DIAG_PORT_LB-3-FSM_LIB_ERROR Format: %s(%d) %s. Error:%s

Explanation: Port Loopback test process failed in MTS API.

Recommended Action: No action is required.

DIAG_PORT_LB-3-STATS_LIB_ERROR Format: %s(%d) %s:%d

Explanation: Port Loopback test process failed in stats infra lib API.

Recommended Action: No action is required.

DIAG_PORT_LB-3-DIAG_PKT_SEND_FAILURE Format: %s(%d) %s. Error:%s

Explanation: Port Loopback test process failed to send loopback packets.

Recommended Action: No action is required.

DIAG_PORT_LB-3-TIMER_LIB_ERROR Format: %s(%d) %s

Explanation: Port Loopback test process timer handling failure.

Recommended Action: No action is required.

DIAG_PORT_LB-3-INVALID_TEST_REQUEST Format: %s(%d) %s:%d

Explanation: Port Loopback test process failed to get test request info.

Recommended Action: No action is required.

DIAG_PORT_LB-3-INVALID_TEST_RUN Format: %s(%d) %s:%d

Explanation: Port Loopback test process failed to get the current test run information

Recommended Action: No action is required.

DIAG_PORT_LB-3-RESULT_ADD_FAILURE Format: %s(%d) %s:%d

Explanation: Port Loopback test process failed to add the port test result

Recommended Action: No action is required.

DIAG_PORT_LB-3-IFINDEX_LIB_FAILURE Format: %s(%d) %s %s:%x %s %s

Explanation: Port Loopback test process failed in if_index library API

Recommended Action: No action is required.

DIAG_PORT_LB-2-PROC_INIT_FAILURE Format: %s(%d) %s Error:%s

Explanation: Port Loopback test process failed in process initialization

Recommended Action: No action is required.

DIAG_PORT_LB-3-SOCKET_ERROR Format: %s(%d) %s Error:%s

Explanation: Port Loopback test process failed in socket operations

Recommended Action: No action is required.

DIAG_PORT_LB-2-LIF_GET_ERROR Format: %s(%d) %s Error:%s

Explanation: Port Loopback test process failed to get Diagnostic LIF id

Recommended Action: No action is required.

DIAG_PORT_LB-3-VLAN_ERROR Format: %s(%d) %s Error:%s

Explanation: Port Loopback test process failed to get Diagnostic VLAN info

Recommended Action: No action is required.

DIAG_PORT_LB-2-PORTLOOPBACK_TEST_FAIL Format: Module:%d Test:PortLoopback failed %d consecutive times. Faulty module:%s %s Error:%s

Explanation: PortLoopback test failed on the module consecutively

Recommended Action: No action is required.

DIAG_PORT_LB-2-REWRITE_ENGINE_LOOPBACK_TEST_FAIL Format: Module:%d Test:RewriteEngine Loopback failed %d consecutive times. Faulty module:%s %s Error:%s

Explanation: Rewrite Engine Loopback test failed on the module consecutively

Recommended Action: No action is required.

DIAG_PORT_LB-4-PORT_CFG_REQ_SEND Format: %s(%d) Failed to send request to configure port ifindex:%d for port loopback test

Explanation: Failed to configure/restore the port to do/cleanup port loopback testing

Recommended Action: No action is required.

DIAG_PORT_LB-3-VQI_GET_FAIL Format: Failed to get the Diag VQi from XBM. Error:%s

Explanation: Rewrite Engine Loopback test failed to get the Diag VQi from XBAR Mgr

Recommended Action: No action is required.

DIAG_PORT_LB-3-RW_ENGINE_LOOPBACK_TEST_SPINE_PATH_FAIL Format: Module:%d Test:RewriteEngine Loopback Spine path:%d failed %d consecutive times. Error:%s

Explanation: Rewrite Engine Loopback test failed on the spine path consecutively

Recommended Action: No action is required.

DIAG_PORT_LB-3-TEST_RES_SEND_FAIL Format: Failed to send %s test results back to Diagnostics Infrastucture. Error:%s.

Explanation: The port loopback test was not able to send the test results

Recommended Action: No action is required.

DIAG_PORT_LB-3-PDB_LIB_API_ERROR Format: Failed to %s. Error:%d.

Explanation: The port loopback test was not able to get chassis info

Recommended Action: No action is required.

DIAG_PORT_LB-3-DIAG_FWD_PATH_SETUP_FAILURE Format: %s. Module:%d Error:%s.

Explanation: Forwarding path setup for port loopback tests failed

Recommended Action: No action is required.

DIAG_PORT_LB-2-LCM_RESP_SEND_FAILURE Format: LC Inserted request response send to Module Manager failed . Error:%s

Explanation: Failed to send the response for LC insertion to Module Manager.

Recommended Action: No action is required.

DIAG_PORT_LB-2-FIPS_RANDOM_ERROR Format: Random Number Generation Failure

Explanation: Random Number genration failed in FIPS module

Recommended Action: No action is required.

DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL Format: Module:%d Test:SnakeLoopback failed %d consecutive times. Faulty module:%s affected ports:%s Error:%s

Explanation: Snake test failed on the module consecutively

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-CREATED Format: %s created

Explanation: a port-channel is created

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-DELETED Format: %s deleted

Explanation: a port-channel is deleted

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_ADDED Format: %s added to %s

Explanation: ports are added to a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_REMOVED Format: %s removed from %s

Explanation: ports are removed from a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-4-PORT_CFG_DELETED Format: %s removed from %s (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.

ETH_PORT_CHANNEL-5-PORT_UP Format: %s: %s is up

Explanation: port comes up in a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_DOWN Format: %s: %s is down

Explanation: port goes down in a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_SUSPENDED Format: %s: %s is suspended

Explanation: port is suspended in a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY Format: %s: %s goes to hot-standby

Explanation: port goes to hot-standby in a port-channel

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY_DOWN Format: %s: hot-standby port %s is down

Explanation: port-channel hot-standby member goes down

Recommended Action: No action is required.

ETH_PORT_CHANNEL-3-COMPAT_CHECK_FAILURE Format: %s 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

ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_MODE Format: Interface %s 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

ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_SPEED Format: Interface %s 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

ETH_PORT_CHANNEL-1-MALLOC_FAILED Format: cannot allocate memory (size %d)

Explanation: no enough memory

Recommended Action: No action is required.

ETH_PORT_CHANNEL-3-MSG_SEND_FAILURE Format: failed to send %s to sap %d: %s

Explanation: failed to send a message

Recommended Action: No action is required.

ETH_PORT_CHANNEL-5-FOP_CHANGED Format: %s: first operational port changed from %s to %s

Explanation: the first operational port in a port-channel is changed

Recommended Action: No action is required.

ETH_PORT_CHANNEL-3-PORT_CHANNEL_NOT_FOUND Format: %s 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.

ETH_PORT_CHANNEL-4-RACE_WARN Format: %s

Explanation: warning of possible race condition

Recommended Action: No action is required.

ETH_PORT_CHANNEL-3-GENERAL_ERROR Format: %s

Explanation: general error

Recommended Action: No action is required.

ETH_PORT_CHANNEL-4-PORT_INDIVIDUAL Format: port %s 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

ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN Format: individual port %s is down

Explanation: port-channel member operating in individual mode goes down

Recommended Action: No action is required.

ETH_PORT_CHANNEL-3-RSP_TIMEOUT Format: Component %s timed out on response to opcode:%s (for:%s)

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

Recommended Action: None

ETH_PORT_CHANNEL-3-ALL_DROP_TIMEOUT Format: Some component(s) (sap:%s) timed out on dropping notif:%s (for:%s); Please collect \

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

Recommended Action: None

ETH_PORT_CHANNEL-3-NUM_ACTIVE_PORTS_ERROR Format: Port-channel:%s active_nports %d; No member is active; Please collect \

Explanation: Port-channel num active ports error

Recommended Action: None

ETH_PORT_CHANNEL-3-PCM_HWCFG_FAIL_ERROR Format: Port-channel:%s mbr:%s SAP %d returned error %s for opc %s; if lacp port-channel please collect \ or please collect \

Explanation: Port-channel hwcfg fail error

Recommended Action: None

ETH_PORT_CHANNEL-3-PCM_PORT_DOWN_IN_PC_UP_ERROR Format: Port-channel:%s mbr:%s; if lacp port-channel please collect \ or please collect \

Explanation: Port-channel port down in pc_up. No bundle member down

Recommended Action: None

ETH_PORT_CHANNEL-3-ADD_REM_MEMBERS_FAILURE Format: %s

Explanation: Some service(s) failed to add or remove ports to port-channel

Recommended Action: None

ETH_PORT_CHANNEL-3-PCM_PORT_DEL_IN_PC_UP_ERROR Format: Port-channel:%s mbr:%s; if lacp port-channel please collect \ or please collect \

Explanation: Port-channel port del in pc_up. Shut resp recvd before bundle member down

Recommended Action: None

ETH_PORT_CHANNEL-3-RESOURCE_ALLOC_FAILED_PORT_CHANNEL_DELETED Format: %s deleted

Explanation: port-channel deleted from running config

Recommended Action: may need to re-configure the port-channel and its members

ETH_PM-5-IF_UP Format: Interface %s is up %s

Explanation: Interface is up in mode specified, if applicable

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_NONE Format: Interface %s is down (%s)

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

ETH_PM-5-IF_DOWN_HW_FAILURE Format: Interface %s 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'

ETH_PM-5-IF_DOWN_LOOPBACK_DIAG_FAILURE Format: Interface %s 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

ETH_PM-2-IF_DOWN_ERROR_DISABLED Format: Interface %s is down (Error disabled. Reason:%s)

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.

ETH_PM-5-IF_DOWN_SOFTWARE_FAILURE Format: Interface %s is down (Port software failure)

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

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_LINK_FAILURE Format: Interface %s 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

ETH_PM-5-IF_DOWN_OFFLINE Format: Interface %s is down (Offline)

Explanation: The interface has been placed into the offline state

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_NON_PARTICIPATING Format: Interface %s is down (Non participating)

Explanation: The loop port has been put into non participating mode

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_INITIALIZING Format: Interface %s 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

ETH_PM-5-IF_DOWN_INACTIVE Format: Interface %s is down (Inactive)

Explanation: The port VSAN has been suspended or deleted

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

ETH_PM-5-IF_DOWN_ADMIN_DOWN Format: Interface %s is down (Administratively down)

Explanation: Interface has been configured to be administratively down

Recommended Action: Perform 'no shutdown'

ETH_PM-5-IF_DOWN_CHANNEL_ADMIN_DOWN Format: Interface %s 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

ETH_PM-3-IF_DOWN_CHANNEL_ERR_DISABLED Format: Interface %s 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

ETH_PM-5-IF_DOWN_SUSPENDED Format: Interface %s 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

ETH_PM-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS Format: Interface %s 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

ETH_PM-5-IF_DOWN_PARENT_ADMIN_DOWN Format: Interface %s is down (Parent interface down)

Explanation: Parent interface is down

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_SRC_PORT_NOT_BOUND Format: Interface %s is down (Tunnel port src interface unbound)

Explanation: Tunnel port source interface unbound

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_INTERFACE_REMOVED Format: Interface %s is down (Interface removed)

Explanation: Interface removed

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_FCOT_NOT_PRESENT Format: Interface %s is down (FCOT not present)

Explanation: The FCOT has been removed

Recommended Action: Insert an FCOT

ETH_PM-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED Format: Interface %s 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

ETH_PM-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE Format: Interface %s 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

ETH_PM-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED Format: Interface %s 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

ETH_PM-5-IF_DOWN_SUSPENDED_BY_MODE Format: Interface %s 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

ETH_PM-5-IF_DOWN_SUSPENDED_BY_SPEED Format: Interface %s 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

ETH_PM-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE Format: Interface %s is down (Isolation due to domain manager other side not responding)

Explanation: Remote end domain manager not responding

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_LOOPBACK_ISOLATION Format: Interface %s 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

ETH_PM-5-IF_DOWN_UPGRADE_IN_PROGRESS Format: Interface %s is down (Linecard upgrade in progress)

Explanation: Upgrade of the linecard software is in progress

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN Format: Interface %s 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

ETH_PM-5-IF_DOWN_MODULE_REMOVED Format: Interface %s is down (module removed)

Explanation: Interface is down because the module was removed

Recommended Action: No action is required.

ETH_PM-5-IF_DUPLEX Format: Interface %s, operational duplex mode changed to %s

Explanation: Operational duplex mode has changed when link came up

Recommended Action: No action is required.

ETH_PM-5-SPEED Format: Interface %s, operational speed changed to %s

Explanation: Operational speed has changed when link came up

Recommended Action: No action is required.

ETH_PM-5-IF_RX_FLOW_CONTROL Format: Interface %s, operational Receive Flow Control state changed to %s

Explanation: Operational receive flow control has changed when link came up

Recommended Action: No action is required.

ETH_PM-5-IF_TX_FLOW_CONTROL Format: Interface %s, operational Transmit Flow Control state changed to %s

Explanation: Operational transmit flow control has changed when link came up

Recommended Action: No action is required.

ETH_PM-5-IF_TRUNK_UP Format: Interface %s, vlan %s up

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

Recommended Action: No action is required.

ETH_PM-5-IF_TRUNK_DOWN Format: Interface %s, vlan %s 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

ETH_PM-3-IF_UNSUPPORTED_TRANSCEIVER Format: Transceiver on interface %s 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

ETH_PM-5-IF_DOWN_ETH_LINK_DOWN Format: Interface %s 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

ETH_PM-5-IF_DOWN_ETH_IF_DOWN Format: Interface %s 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

ETH_PM-5-IF_DOWN_CFG_CHANGE Format: Interface %s is down(Config change)

Explanation: FCIP interface temporarily down due to reconfiguration

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_SRC_PORT_REMOVED Format: Interface %s 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

ETH_PM-5-IF_DOWN_SRC_MOD_NOT_ONLINE Format: Interface %s 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

ETH_PM-5-IF_DOWN_VRF_UNUSABLE Format: Interface %s is down (Vrf down)

Explanation: The vrf for which this interface is a member is removed

Recommended Action: No action is required.

ETH_PM-5-SEQ_TIMEOUT Format: Component %s timed out on response to opcode %s (%s)

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

Recommended Action: None

ETH_PM-5-IF_SEQ_ERROR Format: Error (\%s\") communicating with %s for opcode %s (%s) "#ifndef FINAL " Follow PM FAQ #6 at: http://zed.cisco.com/confluence/display/KGP/Port+Manager+FAQ"#endif

Explanation: Some component returned system error as a response to one of the port event sequence.

Recommended Action: None

ETH_PM-5-STORM_CONTROL_ABOVE_THRESHOLD Format: Traffic in port %s exceeds the configured threshold %s

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

ETH_PM-5-STORM_CONTROL_BELOW_THRESHOLD Format: Traffic in port %s has fallen below the configured threshold %s

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

Recommended Action: No action is required.

ETH_PM-5-IF_BANDWIDTH_CHANGE Format: Interface %s,bandwidth changed to %s Kbit

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

Recommended Action: No action is required.

ETH_PM-5-IF_HARDWARE Format: Interface %s, hardware type changed to %s

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.

ETH_PM-3-IF_ERROR_VLANS_SUSPENDED Format: VLANs %s on Interface %s are being suspended. (Reason: %s)

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

Recommended Action: No action is required.

ETH_PM-3-IF_ERROR_VLANS_REMOVED Format: VLANs %s on Interface %s are removed from suspended state.

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

Recommended Action: No action is required.

ETH_PM-4-IF_SFP_WARNING Format: Interface %s, %s

Explanation: There was an warning on the transceiver module

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

ETH_PM-3-IF_SFP_ALARM Format: Interface %s, %s

Explanation: There was an alarm on the transceiver module

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

ETH_PM-3-IF_SFP_ERROR Format: Interface %s, %s

Explanation: There was an error on the transceiver module

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

ETH_PM-5-IF_L2MP_MODE Format: Interface %s, l2mp-mode changed to %s

Explanation: The l2mp-mode on the port has changed

Recommended Action: No action is required.

ETH_PM-2-IF_CRITICAL_FAILURE Format: (Debug syslog)Critical failure: %s, %s

Explanation: There was a critical failure in the component.

Recommended Action: Please follow instructions on the syslog.)msgdef_ddts_component(SRVNAME_ETH_PORT_MGR

ETH_PM-2-SYSLOG_ETHPM_CRITICAL Format: Critical failure: %s

Explanation: There was a critical failure in the component.

Recommended Action: Please collect system tech-support)msgdef_ddts_component(SRVNAME_ETH_PORT_MGR

ETH_PM-4-IF_XCVR_WARNING Format: Interface %s, %s

Explanation: There was an warning on the transceiver module

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

ETH_PM-3-IF_XCVR_ALARM Format: Interface %s, %s

Explanation: There was an alarm on the transceiver module

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

ETH_PM-3-IF_XCVR_ERROR Format: Interface %s, %s

Explanation: There was an error on the transceiver module

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

ETH_PM-5-IF_ADMIN_UP Format: Interface %s is admin up %s

Explanation: Interface is admin up

Recommended Action: No action is required.

ETH_PM-4-IF_NON_QUALIFIED_TRANSCEIVER Format: Non-qualified transceiver on interface %s 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

ETH_PM-5-IF_ERRDIS_RECOVERY Format: Interface %s is being recovered from error disabled state (Last Reason:%s)

Explanation: Interface is being recovered from error disabled state

Recommended Action: No action is required.

ETH_PM-5-IF_DOWN_PARENT_DOWN Format: Interface %s is down (Parent interface is down)

Explanation: The physical link on the parent interface has gone down

Recommended Action: No action is required.

IGMP-6-SHUTDOWN Format: IGMP shutting self down

Explanation: IGMP process is shutting itself down.

Recommended Action: No user action is required.

IGMP-6-RECEIVE_QUERY Format: Received %s interface %s from %s

Explanation: IGMP version mismatch, query still processed.

Recommended Action: No user action is required.

IGMP-6-RESTART_SHUTDOWN Format: IGMP shutting self down via restart command

Explanation: IGMP process is shutting itself down due to the restart command.

Recommended Action: No user action is required.

IGMP-3-RESTART_REASON Format: IGMP process has restarted, restart reason: %s\n

Explanation: IGMP is restoring the routes it had added in previous instance.

Recommended Action: No user action is required.

IGMP-6-STATE_LIMIT_WARNING Format: Exceeded 80% of the state-limit for interface %s

Explanation: Exceeded 80% of the state-limit for interface

Recommended Action: No user action is required.

IGMP-6-RESERVE_LIMIT_WARNING Format: Exceeded 80% of the reserve-limit for interface %s

Explanation: Exceeded 80% of the reserve-limit for interface

Recommended Action: No user action is required.

IGMP-6-AS_LIMIT_INCREASED Format: Address space size for %s increased %d times

Explanation: IGMP process incremented AS memory resource limit

Recommended Action: No user action is required.

IGMP-4-SYSTEM_RESOURCE_THRESHOLD_WARNING Format: System resource usage for %s is above 84%

Explanation: IGMP entries reached 84% of Threshold.

Recommended Action: No user action is required.

IGMP-3-STATE_LIMIT Format: Exceeded state-limit for interface %s - dropping

Explanation: Exceeded the state-limit for interface

Recommended Action: No user action is required.

IGMP-3-RESERVE_LIMIT Format: Exceeded reserve-limit for interface %s - dropping

Explanation: Exceeded the reserve-limit for interface

Recommended Action: No user action is required.

IGMP-3-GROUP_PREFIX_IGNORE Format: Too many Groups in Group Prefix %s. Specify the prefix within /24

Explanation: GPrefix yiels too many Groups

Recommended Action: No user action is required.

IGMP-3-GROUP_RANGE_IGNORE Format: Too many Groups in Group Range %s - %s

Explanation: Group Range yields too many Groups

Recommended Action: No user action is required.

IGMP-3-UNKNOWN_MTYPE Format: Unknown mtype: %d/%d in %s, opc:%d, from:%s

Explanation: IGMP process received unknown Interprocess message, dropped.

Recommended Action: No user action is required.

IGMP-6-UNKNOWN_OPC Format: Received unknown mts opcode %d

Explanation: IGMP process received unknown Interprocess message, dropped.

Recommended Action: No user action is required.

IGMP-3-MALLOC_FAILED Format: %s failed in %s

Explanation: IGMP process is out of free memory.

Recommended Action: Configure the network or router to decrease the number of routes.

IGMP-3-BITFIELD_FAILED Format: %s failed in %s

Explanation: IGMP process could not execute the bitfield operation.

Recommended Action: Dump core, then reload the stack.

IGMP-3-VRF_CREATE Format: IGMP VRF creation failed for vrf %s

Explanation: IGMP process could not create the VRF context.

Recommended Action: Dump core, then reload the stack.

IGMP-3-API_FAILED Format: %s failed in %s

Explanation: IGMP process failed in invoking an API.

Recommended Action: No user action is required.

IGMP-3-GET_MAC_ADDR Format: %s failed in %s with error %s

Explanation: IGMP process failed in getting mac addr

Recommended Action: No user action is required.

IGMP-3-IM_API_FAILED Format: %s failed in %s

Explanation: IM API failed in MCEC IGMP Snoop.

Recommended Action: No user action is required.

IGMP-3-vPC_API_FAILED Format: %s%s

Explanation: API failed in vPC IGMP snoop module.

Recommended Action: No user action is required.

IGMP-3-vPC_ERROR Format: %s%s

Explanation: vPC related messages.

Recommended Action: No user action is required.

IGMP-6-vPC_INFO Format: %s%s

Explanation: vPC related messages.

Recommended Action: No user action is required.

IGMP-3-PTHREAD_FAILED Format: %s failed in %s for thread %s

Explanation: IGMP process failed to create a task thread.

Recommended Action: Dump core, then restart component.

IGMP-3-TIMER_FAILED Format: %s failed for %s in %s

Explanation: IGMP process failed to configure a timer event.

Recommended Action: Dump core, then restart component.

IGMP-3-PULLUP_FAILED Format: m_pullup() of %d bytes failed in %s

Explanation: IGMP process failed to process the packet, dropping it.

Recommended Action: No user action is required.

IGMP-3-NO_SHUTDOWN Format: Unable to shutdown %s

Explanation: IGMP process unable to shut itself down.

Recommended Action: Dump core, then restart component.

IGMP-3-ALREADY_RUNNING Format: IGMP already running, exiting

Explanation: Another IGMP process is already running, this process will shutdown.

Recommended Action: No user action is required.

IGMP-3-NO_SET_PRIORITY Format: Failed to set policy or priority

Explanation: IGMP process could not set itself process priority, exiting.

Recommended Action: No user action is required.

IGMP-3-SETRLIMIT_FAILED Format: Address space size increment of %ld failed, reason %s

Explanation: IGMP process could not set itself memory resource limit

Recommended Action: No user action is required.

IGMP-3-GETRLIMIT_FAILED Format: Address Space size retrieval failed, reason %s

Explanation: IGMP process could not retrieve memory resource limit

Recommended Action: No user action is required.

IGMP-2-STARTUP_FAILURE Format: Startup failure: %s

Explanation: An unrecoverable software error has occurred during igmp startup.

Recommended Action: No user action is required.

IGMP-2-STARTUP_DEBUG Format: %s %d

Explanation: An unrecoverable software error has occurred during igmp startup.

Recommended Action: No user action is required.

IGMP-3-AVL_ERROR Format: AVL-tree operation %s failed for %s

Explanation: IGMP process failed in an AVL-tree manipulation.

Recommended Action: No user action is required.

IGMP-3-PT_ADD Format: Couldn't add element to PT %s

Explanation: IGMP failed to update the local snooping-db entry.

Recommended Action: No user action is required.

IGMP-3-PT_DEL Format: Couldn't delete element from PT %s

Explanation: IGMP failed to delete the local snooping-db entry.

Recommended Action: No user action is required.

IGMP-3-BF_CREATE Format: Couldn't create bitfield for %s

Explanation: IGMP failed to create bitfield resource.

Recommended Action: Dump core, then restart component.

IGMP-3-VLAN_EXISTS Format: SNOOP: Couldn't create %s, already esists

Explanation: IGMP failed to create vlan resource.

Recommended Action: No user action is required.

IGMP-3-IGMP_INIT Format: IGMP init failed: %s

Explanation: IGMP process initialization failed.

Recommended Action: Dump core, then restart component.

IGMP-3-VLAN_DEL Format: Couldn't delete vlan entry for %s due to %s from snooping database

Explanation: IGMP failed to delete the snooping-db vlan entry.

Recommended Action: No user action is required.

IGMP-3-GROUP_DEL Format: Couldn't delete group entry for %s (%s) due to %s from snooping database

Explanation: IGMP failed to delete the snooping-db group entry.

Recommended Action: No user action is required.

IGMP-3-ENCAP_DEL Format: Couldn't delete encap entry for %d (*, %s) (%s) due to %s from snooping database

Explanation: IGMP failed to delete the snooping-db encap entry.

Recommended Action: No user action is required.

IGMP-3-SOURCE_DEL Format: Couldn't delete source entry for (%s, %s) (%s) due to %s from snooping database

Explanation: IGMP failed to delete the snooping-db source entry.

Recommended Action: No user action is required.

IGMP-3-SNOOP_CONFIG_ERROR Format: SNOOP: Couldn't configure %s, please configure %s first.

Explanation: IGMP snooping could not configure a parameter because of dependencies

Recommended Action: No user action is required.

IGMP-3-FEX_QUERY_ERROR Format: Router behind FEX port %s is not supported by the hardware

Explanation: IGMP snooping could not process query from the fex port since it is not supported

Recommended Action: No user action is required.

IGMP-3-FEX_MRD_ERROR Format: Router behind FEX port %s is not supported by the hardware

Explanation: IGMP snooping could not process PIM hello from the fex port since it is not supported

Recommended Action: No user action is required.

IGMP-3-GROUP_LIMIT Format: Exceeded multicast group limit (%d), ignoring new reports

Explanation: Exceeded the multicast group limit

Recommended Action: No user action is required.

IGMP-3-GROUP_LOW_THRESH Format: Multicast group count below %d, group joins re-enabled

Explanation: Multicast group count below threshold

Recommended Action: No user action is required.

IGMP-3-TXLIST_CREATE Format: Couldn't create txlist for %s

Explanation: IGMP failed to create txlist resource.

Recommended Action: Dump core, then restart component.

IGMP-3-MUTEX_INIT Format: Couldn't init mutex %s

Explanation: IGMP process failed to initialize mutex system resource.

Recommended Action: Dump core, then restart component.

IGMP-3-CV_INIT Format: Couldn't init cond var %s

Explanation: IGMP process failed to initialize conditional-variable resource.

Recommended Action: Dump core, then restart component.

IGMP-3-QUERIER_START_FAILED Format: %s failed in %s

Explanation: IGMP snoop failed to start the querier.

Recommended Action: No user action is required.

IGMP-3-RPORT_UPDATE Format: Router-port update failed for %s (%s)

Explanation: IGMP-SNOOP called an API which returned an error.

Recommended Action:

IGMP-3-RCOUNT_UPDATE Format: Route count update failed for %s

Explanation: IGMP called an API which returned an error.

Recommended Action:

IGMP-3-RCOUNT_DELETE Format: Route count delete failed for %s

Explanation: IGMP called an API which returned an error.

Recommended Action:

IGMP-3-LVPORT_CREATE Format: IGMP Snooping couldn't create an leave-port in %s for group %s

Explanation: IGMP-SNOOP called an API which returned an error.

Recommended Action:

IGMP-3-INVALID_OIF_LIST Format: IGMP Snooping invalid OIF list %s with %d iods in %s

Explanation: IGMP-SNOOP has invalid number of iods.

Recommended Action:

IGMP-3-SYSMGR_DISPATCH Format: Error returned from sysmgr_dispatch(), errno: %s

Explanation: IGMP called a System Manager API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-MTS_BIND Format: Error returned from mts_bind() for %s mts-q, errno: %s

Explanation: IGMP called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-MTS_SEND Format: Error returned from mts_send() for %s queue, errno: %s

Explanation: IGMP called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-MTS_RECV Format: Error returned from mts_recv() for %s queue, errno: %s

Explanation: IGMP called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-MTS_DROP Format: Error returned from mts_drop() for %s queue, errno: %s

Explanation: IGMP called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-MTS_INIT Format: Error returned from mts_callback_handler_set() for %s queue, errno: %s

Explanation: IGMP called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

IGMP-3-BAD_MSG Format: Invalid %s message received from %s

Explanation: IGMP received an invalid MTS message.

Recommended Action: Dump core, then restart component.

IGMP-3-LIB_MTS_FAILED Format: %s failed in %s, errno: %s

Explanation: Process failed to access the IGMP MTS-queue.

Recommended Action: No user action is required.

IGMP-3-LIB_API_FAILED Format: %s failed in %s

Explanation: Process failed in invoking IGMP API.

Recommended Action: No user action is required.

IFMGR-5-IM_UNKNOWN_INTERFACE Format: %s

Explanation: Interface is not supported or not found

Recommended Action: No action is required.

IFMGR-5-IM_INTERNAL_ERROR Format: %s

Explanation: Internal error occurred

Recommended Action: No action is required.

IFMGR-5-IM_DEMUX_ERROR Format: %s

Explanation: Demux function returned error

Recommended Action: No action is required.

IFMGR-5-IM_INTF_STATE Format: %s %s in vdc %d

Explanation: Management interface state changed.

Recommended Action: No action is required.

IFMGR-3-IM_SEQ_ERROR Format: Error (%s) while communicating with component %s opcode:%s (for:%s)

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

Recommended Action: No action is required.

IFMGR-3-IM_RESP_ERROR Format: Component %s opcode:%s in vdc:%d returned error:%s

Explanation: Some component returned an error.

Recommended Action: No action is required.

IFMGR-3-IM_LC_OFFLINE_ERROR Format: LC Offline could not be sent to vdc:%d\n

Explanation: LC Offline was not relayed to some vdc, so applications may not behave correctly.

Recommended Action: No action is required.

IFMGR-3-IM_IF_FEATURE_BIND_FAILURE Format: Interface feature bind failed %s\n

Explanation: interface feature bind failed, so applications in that feature set may not behave correctly.

Recommended Action: No action is required.

IPFIB-LC-4-IPFIB_PSS_RUNNING_OUT_OF_SPACE Format: PSS Global buffer running out of space

ISIS-2-STARTUP_FAILURE Format: Startup failure: Failed to %s

Explanation: An unrecoverable software error has occurred during startup.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

ISIS-2-RUNTIME_INIT_FAILURE Format: Unexpected runtime initialization failure. Failed to %s

Explanation: An unexpected software error has occurred while initializing a sub-component.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-RUNTIME_CLEANUP_FAILURE Format: Unexpected runtime cleanup failure. Failed to %s

Explanation: An unexpected software error has occurred while cleaning up a sub-component.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-TLV_MIGRATE Format: L%d %s still has TLV during migration

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-HOLDDOWN Format: Failed to enable process after sequence number wrap holddown.

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-MQRCVD Format: %s thread - message queue receive failure \

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-URIB_UPDATE Format: Failed to notify SPF thread about route update buffer availability

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-ROUTE_NOTIFY Format: Route notifications to the RIB are not possible. This will result in stale state in the FIB.

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-MEM_ERR Format: Insufficient memory for %s

Explanation: Memory is not avialable for adding SNP entries

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-AVL_FAIL Format: Add to CSNP cache failed: %s - %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-URIB_ADD_RNH_FAILURE Format: Cannot add RNH to %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-ROUTE_BUF_OVERFLOW Format: %s route buffer overflow at entry %lu\n

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-REDIST_PIB_SHM Format: Failed to attach to redistributing PIB's SHM %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-LSP_FREE_LINK Format: L%d %s is already on free list

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-LSP_FREE_DELINK Format: L%d %s is not on free list

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-IM_DEL Format: Delete msg for %s (%d) iib %p - iib iod %d mismatched

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-IIB_EXT Format: %s extension msg for %s (%d) - %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-SUM_DIST Format: sum-addr %s/%d has zero route-dist candidate count

Explanation: An unexpected but handleable event has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-2-MCAST_ADD Format: Failed to add L%d multicast address

Explanation: Was unable to join to the appropriate multicast group on an interface.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-3-AVL_LOOKUP Format: Can't locate CSNP fragment for %s

Explanation: SNP cache may get cleaned up during normal operation

Recommended Action: No user action is required.

ISIS-3-PT_ADD Format: Couldn't add entry to %s PT

Explanation: ISIS failed to update a local database entry.

Recommended Action: No user action is required.

ISIS-3-PT_DEL Format: Couldn't delete entry for %s from %s PT

Explanation: ISIS failed to delete an entry from a local database.

Recommended Action: No user action is required.

ISIS-3-SLAB_ALLOC Format: Slab alloc of type %s failed for %s

Explanation: ISIS process failed to allocate Slab memory.

Recommended Action: Configure the network or router to decrease the number of routes.

ISIS-3-SWID_UPDATE Format: Switch-ID table update failed for %s

Explanation: ISIS process failed to update Switch-ID database.

Recommended Action: Configure the network or router to decrease the number of routes.

ISIS-3-WEIRD_CACHE Format: Inconsistent cache %x %s %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-SELF_LSP_CLEANUP Format: Cleanup L%d LSP %s with non-null TLV list

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-NO_HELPER_IIB Format: No helper iib for %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-LSP_REFRESH Format: Refresh non-self-originated level-%d LSP %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-NOTIFY_THREAD Format: Failed to notify %s thread - Reschedule

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-MTS Format: Error returned from MTS operation %s, errno: %s

Explanation: ISIS called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

ISIS-3-MTS_RECV Format: Error returned from mts_recv(), errno: %s

Explanation: ISIS called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

ISIS-3-MTS_DROP Format: Error returned from mts_drop(), errno: %s

Explanation: ISIS called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

ISIS-3-BAD_PKT Format: Unexpected packet received by thread %s.

Explanation: ISIS received an unexpected packet.

Recommended Action: No user action is required.

ISIS-3-UNK_MTS_OPC Format: %s thread - Unrecognized MTS opcode %d

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-UNK_MSG_MAJOR Format: %s thread - Unrecognized message major type %d

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-UNK_MSG_MINOR Format: Unrecognized %s message minor type %d

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-UNK_LSP_TIMER Format: Unrecognized LSP timer type %d for level-%d LSP %s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-UNK_DEB_FLAG Format: Ignore unrecognized debug flag \%s\""

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-UNK_IP_NOTIF Format: Unrecognized IP address change notification type %lu

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-SPF_ADJ_DEL Format: Deleting SPF adj with refcount %lu\n

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-5-NH_DEL Format: Cleanup L%d route %s/%d has %s next hop

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-MBUF_COPY Format: Error 0x%08x copy %hu bytes packet from %s%s

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-MCAST_DEL Format: Failed to remove L%d multicast address

Explanation: Was unable to leave from the appropriate multicast group on an interface.

Recommended Action: No user action is required.

ISIS-3-PIB_UP Format: Failed to bring up protocol

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-RPM_CALLBACK Format: RPM Callback handle and/or user data missing

Explanation: An attempt to obtain RPM Keychain information failed.

Recommended Action: No user action is required.

ISIS-3-VLAN_MGR Format: Error in parsing %s message from VLAN Manager

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-ISIS_HA_PSS Format: HA Persistent-store failure for %s %s: %s

Explanation: A software error has occurred during HA. Stateful HA recovery will be disabled

Recommended Action: No user action is required.

ISIS-3-UNK_SYSMGR_NOTIFY Format: Unexpected registration received from process %u

Explanation: An unexpected but handleable event has occurred.

Recommended Action: No user action is required.

ISIS-3-BFD_SESSION_REMOVE Format: Failed to remove BFD session, error %s

Explanation: Unable to remove BFD sessions.

Recommended Action: No user action is required.

ISIS-3-OTV_SITE_CAP Format: Failed to add/remove otv site/net-id capability conf check, error %s

Explanation: Unable to add conf check.

Recommended Action: No user action is required.

ISIS-3-OTV_INFO Format: Failed to retrieve OTV %s info %s

Explanation: Unable to retrieve OTV information

Recommended Action: No user action is required.

ISIS-3-CONFIG_ERROR Format: Error In Configuration: %s

Explanation: Unsupported configuration

Recommended Action: No user action is required.

ISIS-5-PROC_SEQWRAP Format: Handle sequence number wraparound - disabling process for %d secs

Explanation: An LSP's sequence number has wrapped, and the process will be disabled for the correct length of time.

Recommended Action: No user action is required.

ISIS-5-ADJCHANGE Format: %s adj L%s %s over %s - %s on MT-%d

Explanation: The indicated adjacency has changed state.

Recommended Action: No user action is required.

ISIS-4-LSPFULL Format: L%d %s LSP space is full

Explanation: There is no storage space left for routing information in the router's LSP

Recommended Action: Configure IS-IS so that less information will be distributed in the router's LSP, for example by reducing redistributed prefixes.

ISIS-4-SEQWRAP Format: Sequence number wraparound event detected

Explanation: IS-IS has detected that an LSP's sequence number has wrapped. IS-IS will shut down and restart

Recommended Action: No user action is required.

ISIS-4-PROC_NO_MEM Format: No memory event, shutting down process

Explanation: Previously an allocation failed due to no available memory. IS-IS will shut down and wait for user to restart it.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-4-NO_MEM Format: No memory event detected

Explanation: An attempt to allocate from free memory 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.

ISIS-4-LSPFULL_FORCED_DROP Format: L%d %s LSP is full, removed lower priority TLVs to make room for type %d TLV

Explanation: There was no storage space left for important routing information in the router\'s LSP, and so lower priority information (e.g., redistributed prefixes) has been dropped to make room.

Recommended Action: Configure IS-IS so that less information will be distributed in the router's LSP, for example by reducing redistributed prefixes.

ISIS-4-LSPFULL_FAILED_DROP Format: L%d %s LSP is full and couldn't remove lower priority TLVs to make room for type %d TLV

Explanation: There is no storage space left for routing information in the router\'s LSP, and an attempt to drop lower priority information has failed.

Recommended Action: Configure IS-IS so that less information will be distributed in the router's LSP, for example by reducing redistributed prefixes.

ISIS-4-NO_CID Format: Cannot allocate CID for %s\n - Over 255 LANs limit

Explanation: IS-IS has been enabled on more than 255 broadcast interfaces and thus exceeded the protocol mandated limitation. Interfaces that are enabled beyond 255 will be ignored internally until the total count drops below 255.

Recommended Action: Disable IS-IS on one or more broadcast interfaces using the CLI command 'no ip router isis', or convert the interface to point-to-point mode using the CLI command 'medium p2p' followed by 'ip router isis'.

ISIS-4-ADJ_ADVT Format: Failed to advertise level %d adjacency %s

Explanation: IS-IS was unable to advertise the indicated adjacency.

Recommended Action: No user action is required.

ISIS-4-LAN_DUP_SYSID Format: L%d LAN IIH - Duplicate system ID %s detected over %s from %s

Explanation: IS-IS has detected another system on the indicated LAN that is reusing the local system ID

Recommended Action: Configure either the local or remote router with a different system ID using the CLI command 'net'.

ISIS-4-P2P_DUP_SYSID Format: P2P IIH - Duplicate system ID %s detected over %s

Explanation: IS-IS has detected another system on the indicated P2P that is reusing the local system ID.

Recommended Action: Configure either the local or remote router with a different system ID using the CLI command 'net'.

ISIS-4-LSP_DUP_SYSID Format: L%d LSP - Possible duplicate system ID %s detected

Explanation: IS-IS has detected another non-directly connected system that is reusing the local system ID.

Recommended Action: Configure either the local or remote router with a different system ID using the CLI command 'net'.

ISIS-4-ADD_UNK_NH_ADDR Format: Attempt to add for L%d %s/%d on %s with unknown (zero) NH address

Explanation: IS-IS has detected one or more routers at the same level to have a different set of address families enabled.

Recommended Action: Configure all IS-IS routers at the same level to have the same address families enabled using the CLI command 'address-family ip/ipv6 unicast'.

ISIS-4-ILLEGAL_PREFIX Format: Ignore internal L%d route %s/%d with external metric from %s

Explanation: IS-IS has detected an internal route advertised with external metric, which is an illegal combination, by a router within the network

Recommended Action: You must correct the remote system that is generating the incorrect information. Either reconfigure the remote system or update the system software to a version that does not originate incorrect information.

ISIS-4-ADD_DEL_URIB_ERR Format: Failed to %s %lu %s route(s) xid %lu to URIB

Explanation: IS-IS failed to update route information into URIB

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

ISIS-4-REDIST_MAX_ROUTE Format: Redistribution route limit has been reached - %d routes

Explanation: ISIS redistribution: Max limit

Recommended Action: No user action is required.

ISIS-4-REDIST_THR_ROUTE Format: Redistribution threshold has been reached - %d routes

Explanation: ISIS redistribution: Threshold limit

Recommended Action: No user action is required.

ISIS-6-START Format: Process start. Reason - %s

Explanation: ISIS process start with specified reason

Recommended Action: No user action is required.

ISIS-6-STOP Format: Process stop. Reason - %s

Explanation: ISIS procss stop with specified reason

Recommended Action: No user action is required.

ISIS-6-SEQWRAP_HOLDDOWN Format: Sequence number wraparound holddown timer expired - enable process

Explanation: The correct amount of time has elapsed after an LSP's sequence number wrapped so that IS-IS can resume normal operation.

Recommended Action: No user action is required.

ISIS-6-SYSMAN_CLEANUP Format: Terminated by SYSMAN cleanup signal

Explanation: IS-IS has been signaled to exit.

Recommended Action: No user action is required.

ISIS-6-SHUTDOWN_FAILURE Format: Shutdown failure. Failed to %s - %s

Explanation: IS-IS request to system manager for permission to shutdown was declined.

Recommended Action: No user action is required.

ISIS-6-UNK_PDU Format: Unrecognized PDU type %d from %s%s

Explanation: IS-IS has received a packet of a type which it does not recognize. The packet will be dropped.

Recommended Action: No user action is required.

ISIS-6-JUMBO_PDU Format: Drop %hu bytes jumbo PDU with %hu bytes buffer from %s%s

Explanation: IS-IS has received a packet that exceeds the maximum supported size. The packet will be dropped.

Recommended Action: No user action is required.

ISIS-6-UNK_NLPID Format: Unrecognized NLP ID %02X from %s%s

Explanation: IS-IS has received a packet with an NLPID which it does not recognize. The packet will be dropped.

Recommended Action: No user action is required.

ISIS-6-MODE_NO_FUNC Format: No callback function registered for %s in %s mode

Explanation: IS-IS encountered a problem where no callback function has been registered in the given mode

Recommended Action: No user action is required.

L2MCAST-LC-6-L2MCAST_INITIALIZED Format: Internal state created %s

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

Recommended Action: No action is required.

L2MCAST-LC-6-L2MCAST_VDC_CREATED Format: VDC %d created

Explanation: Request to create VDC [dec] in L2MCAST was successful.

Recommended Action: No action is required.

L2MCAST-LC-6-L2MCAST_VDC_REMOVED Format: VDC %d Removed

Explanation: L2MCAST has successfully removed VDC [dec] from its databases.

Recommended Action: No action is required.

L2MCAST-LC-6-L2MCAST_VDC_VLAN_CREATED Format: VLAN %d created

Explanation: L2MCAST has added VLAN [dec].

Recommended Action: No action is required.

L2MCAST-LC-6-L2MCAST_VDC_VLAN_REMOVED Format: VLAN %d removed from VDC %d

Explanation: L2MCAST has successfully removed VLAN [dec] from VDC [dec].

Recommended Action: No action is required.

L2MCAST-LC-2-L2MCAST_VLAN_NOT_FOUND Format: VLAN %d not found in L2MCAST database!

Explanation: L2MCAST failed to find VLAN [dec] in its database. L2 MAC learning and aging on VLAN [dec] may be affected.

Recommended Action: No action is required.

L2MCAST-LC-3-L2MCAST_HW_INSTALL_FAIL Format: Hw install failed for vlan %d (%d, %s, %s) 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.

L2MCAST-LC-2-L2MCAST Format: Memory allocation failed. %s

Explanation: Memory allocation failed. This is a critical failure

Explanation: SYSLOGDOC_NO_ACTION

Recommended Action:

L2MCAST-LC-0-L2MCAST_TIMER_INIT_FAILED Format: Timer subsystem initialization failed!

Explanation: L2MCAST failed to initialize timer library. This is a fatal error.

Recommended Action: No action is required.

L2MCAST-LC-0-L2MCAST_CLI_INIT_FAILED Format: 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.

L2MCAST-LC-2-L2MCAST_HW_OMF_INSTALL_FAIL_TCAM_FULL Format: Failed to insert entry in OMF table for BD %d OMF cannot be configured on New BDs

Explanation: Failed to program the OMF entries for BD. New BD's cannot have omf mode

Recommended Action: No action is required.

LACP-5-LACP_ENABLED Format: LACP Enabled

Explanation: LACP Service Enabled

Recommended Action: No action is required.

LACP-5-LACP_DISABLED Format: LACP Disabled

Explanation: LACP Service Disabled

Recommended Action: No action is required.

LACP-3-GENERAL_ERROR Format: %s

Explanation: general error

Recommended Action: No action is required.

LACP-5-SYSTEM_PRIORITY_CHANGED Format: LACP system priority changed from 0x%x to 0x%x

Explanation: LACP system priority has been changed

Recommended Action: No action is required.

LACP-5-PORT_PRIORITY_CHANGED Format: %s: LACP port priority changed from %d to %d

Explanation: LACP port priority has been changed

Recommended Action: No action is required.

LACP-3-PACKET_TRANSMIT_ERR Format: %s: Could not send LACP packet err=%d

Explanation: There was an error in sending LACP packet

Recommended Action: No action is required.

LACP-3-SYSTEM_MAC_ERR Format: %s: Could not get system mac[%s]

Explanation: There was an error in acquiring system mac from VDC Mgr

Recommended Action: No action is required.

LACP-3-SYN_COLL_DIS_EN Format: %s [%s]: 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.

LACP-3-LACP_SUSPEND_HALF_DUPLEX_PORT Format: Port %s is in half duplex mode. suspend port

Explanation: LACP is not supported in half duplex mode. Suspend port

Recommended Action: No action is required.

LACP-5-LACP_SUSPEND_INDIVIDUAL Format: LACP port %s of port-channel %s not receiving any LACP BPDUs suspending (individual) port

Explanation: LACP suspend individual ports

Recommended Action: No action is required.

LACP-3-LACP_SUSPEND_MINLINK Format: LACP port %s of port-channel %s is suspended as min-link requirement not met.

Explanation: LACP suspend ports due to min-link

Recommended Action: No action is required.

LACP-5-LACP_DOES_NOT_MEET_MINLINK_REQ Format: LACP port-channel %s 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.

LACP-5-LACP_MEETS_MINLINK_REQ Format: LACP port-channel %s meets min-link requirement. Reint port-channel

Explanation: LACP port-channel meets min-link requirement

Recommended Action: No action is required.

LACP-5-LACP_UPGRADE_READY_SUCCESS Format: Upgrade ready successful.

Explanation: Upgrade ready event is successful as all port channel members are in steady state.

Recommended Action: No action is required.

LACP-3-LACP_UPGRADE_READY_FAILED Format: Upgrade ready failed.

Explanation: Upgrade ready event failed because atleast one port channel member is in intermediate state.

Recommended Action: No action is required.

LACP-5-LACP_REMOTE_NOTIFY_SUCCESS Format: Remote notify event.

Explanation: Remote notify event was successful.

Recommended Action: No action is required.

LACP-3-ALLOCFAIL Format: Failed to allocate memory in %s[%d] for size %d

Explanation: LACP is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action: No action is required.

LACP-3-LACP_INTERNAL_ERROR Format: LACP internal error: %s

Explanation: Internal error is encountered

Recommended Action: No action is required.

LACP-3-ISTACKREGISTER Format: Failed to register istack - %s

Explanation: Failed to register istack. [char] identifies the reason.

Recommended Action: No action is required.

LLDP-6-DETECT_REMOTE_CHANGE Format: Remote change detected on %s

Explanation: Remote change detected on an interface

Recommended Action: No action is required.

LLDP-3-DETECT_MULTIPLE_PEERS Format: Multiple peers detected on %s

Explanation: Multiple peers detected on an interface

Recommended Action: No action is required.

LLDP-3-INVALID_LLDP_RECEIVED Format: Received an invalid LLDP on %s

Explanation: Received an invalid LLDP on an interface

Recommended Action: No action is required.

LLDP-3-LLDP_INTERNAL_ERROR Format: LLDP internal error: %s

Explanation: Internal error is encountered

Recommended Action: No action is required.

LLDP-5-LLDP_ENABLED Format: LLDP Enabled

Explanation: LLDP Service Enabled

Recommended Action: No action is required.

LLDP-5-LLDP_DISABLED Format: LLDP Disabled

Explanation: LLDP Service Disabled

Recommended Action: No action is required.

LLDP-5-SERVER_ADDED Format: Server with Chassis ID %s Port ID %s management address %s discovered on local port %s in vlan %d with enabled capability %s

Explanation: A new peer is discovered

Recommended Action: No action is required.

LLDP-5-SERVER_REMOVED Format: Server with Chassis ID %s Port ID %s on local port %s has been removed

Explanation: A peer is removed

Recommended Action: No action is required.

LLDP-3-ALLOCFAIL Format: Failed to allocate memory in %s[%d] for size %d

Explanation: LLDP is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action: No action is required.

LLDP-3-ISTACKREGISTER Format: Failed to register istack - %s

Explanation: Failed to register istack. [char] identifies the reason.

Recommended Action: No action is required.

MCECM-3-VPCM_INIT_FAIL Format: vPC Manager Initialization Failed (%s)

Explanation: vPCM Initialization failed. due to [chars]

Recommended Action: No action is required.

MCECM-3-VPCM_MTS_ERR Format: %s

Explanation: vPCM encountered an MTS error due to [chars]

Recommended Action: No action is required.

MCECM-3-VPCM_INTERNAL_ERR Format: %s

Explanation: vPCM encountered an internal error due to [chars]

Recommended Action: No action is required.

MCECM-6-VPCM_INTERNAL_INFO Format: %s

Explanation: vPCM got an internal info [chars]

Recommended Action: No action is required.

MCECM-3-PEER_UNREACHABLE Format: Remote Switch Unreachable

Explanation: Peer unreachable

Recommended Action: No action is required.

MCECM-6-VPC_CFGD Format: vPC %d is configured

Explanation: vPC is configured

Recommended Action: No action is required.

MCECM-6-PEER_VPC_CFGD Format: peer vPC %d is configured

Explanation: vPC is configured

Recommended Action: No action is required.

MCECM-4-VPC_DELETED Format: vPC %d is deleted

Explanation: vPC configuration deleted

Recommended Action: No action is required.

MCECM-4-PEER_VPC_DELETED Format: Peer vPC %d deleted

Explanation: Peer vPC configuration deleted

Recommended Action: No action is required.

MCECM-3-VPC_PEER_LINK_BRINGUP_FAILED Format: vPC peer-link bringup failed (%s)

Explanation: vPC Peer-link bringup failed

Recommended Action: No action is required.

MCECM-3-VPC_BRINGUP_FAILED Format: vPC %d bringup failed (%s)

Explanation: vPC bringup failed

Recommended Action: No action is required.

MCECM-5-VPC_PEER_LINK_UP Format: vPC Peer-link is up

Explanation: vPC Peer-link is up

Recommended Action: No action is required.

MCECM-5-VPC_UP Format: vPC %d is up

Explanation: MCEC is UP

Recommended Action: No action is required.

MCECM-6-PEER_VPC_UP Format: Peer vPC %d is up

Explanation: Peer vPC is up

Recommended Action: No action is required.

MCECM-3-VPC_PEER_LINK_DOWN Format: VPC Peer-link is down

Explanation: vPC Peer link is down

Recommended Action: No action is required.

MCECM-5-VPC_DOWN Format: vPC %d is down (%s)

Explanation: vPC is down (reason)

Recommended Action: No action is required.

MCECM-6-PEER_VPC_DOWN Format: Peer vPC %d is down (%s)

Explanation: Peer vPC is down

Recommended Action: No action is required.

MCECM-6-PEER_VPC_CFGD_VLANS_CHANGED Format: Peer vPC %d configured vlans changed

Explanation: Remote MCEC configured vlans Changed

Recommended Action: No action is required.

MCECM-4-VPC_ROLE_CHANGE Format: In domain %d, VPC role status has changed to %s

Explanation: vPC role status changed to (Primary/Secondary

Recommended Action: No action is required.

MCECM-6-VPC_DOMAIN_ID_CFGD Format: vPC domain-id configured to %d

Explanation: vPC domain-id configured

Recommended Action: No action is required.

MCECM-5-ROLE_PRIORITY_CFGD Format: In domain %d, vPC role priority changed to %d

Explanation: role priority configured

Recommended Action: No action is required.

MCECM-5-SYSTEM_MAC_CFGD Format: In domain %d, vPC system-mac changed to %s

Explanation: system mac configured

Recommended Action: No action is required.

MCECM-5-SYSTEM_PRIO_CFGD Format: In domain %d, vPC system priority changed to %d

Explanation: system priority changed

Recommended Action: No action is required.

MCECM-5-GLOBAL_CONSISTENCY_SUCCESS Format: In domain %d, global configuration is consistent

Explanation: global compat-check passed

Recommended Action: No action is required.

MCECM-3-GLOBAL_CONSISTENCY_FAILED Format: In domain %d, global configuration is not consistent (%s)

Explanation: global compat-check failed

Recommended Action: No action is required.

MCECM-5-INTF_CONSISTENCY_SUCCESS Format: In domain %d, vPC %d configuration is consistent

Explanation: vPC configuration is consistent

Recommended Action: No action is required.

MCECM-3-INTF_CONSISTENCY_FAILED Format: In domain %d, VPC %d configuration is not consistent (%s)

Explanation: MCEC compat-check failed

Recommended Action: No action is required.

MCECM-2-VPC_SUSP_ALL_VPC Format: Peer-link going down, suspending all vPCs on secondary

Explanation: peer link down suspend vPCs

Recommended Action: No action is required.

MCECM-2-PEER_VPC_RESP_TIMEDOUT Format: Failed to receive response from peer for vPC: %d

Explanation: vPC bringup failed

Recommended Action: No action is required.

MCECM-5-VPC_RESTORE_TIMER_START Format: vPC restore timer started to reinit vPCs

Explanation: vPC restore timer start

Recommended Action: No action is required.

MCECM-5-VPC_RESTORE_TIMER_EXPIRED Format: vPC restore timer expired, reinitiating vPCs

Explanation: vPC restore timer expired

Recommended Action: No action is required.

MCECM-5-VPC_DELAY_SVI_BUP_TIMER_START Format: vPC restore, delay interface-vlan bringup timer started

Explanation: vPC delay interface-vlan restore timer start

Recommended Action: No action is required.

MCECM-5-VPC_DELAY_SVI_BUP_TIMER_EXPIRED Format: 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.

MCECM-4-VPC_REINITIALIZED Format: Reinitializing vpcs assuming peer dead

Explanation: Initializing vpcs assuming peer dead

Recommended Action: No action is required.

MCECM-6-VPC_CONSISTENCY_CHECK_BYPASS Format: Bypassing consistency check for vPC: %d

Explanation: Bypassing consistency check for vpcs

Recommended Action: No action is required.

MCECM-6-VPC_CONSISTENCY_NEW_VLAN_PASS Format: 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.

MCECM-4-VPC_CONSISTENCY_NEW_VLAN_FAIL Format: 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.

MCECM-6-VPC_PER_VLAN_CONSISTENCY_PASSED Format: 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.

MCECM-4-VPC_PER_VLAN_CONSISTENCY_FAILED Format: 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.

MCECM-2-VPC_GRACEFUL_SUSP_ALL_VPC Format: Operational graceful type-1 check state changed, reinitiating all vPCs

Explanation: graceful state change,reinit vPCs

Recommended Action: No action is required.

MCECM-2-VPC_PSS_ERROR Format: %s, 0x(%x) 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.

MCP-3-MCP_MSTP_REGION_MISCONFIG Format: MCP MSTP Region with Name [%s], Revision [%d] not found

Explanation: MCP MSTP region misconfiguration

Recommended Action: No action is required.

MCP-3-MCP_RSTP_MISCONFIG Format: MCP intf 0x%x native vlan unset

Explanation: MCP RSTP misconfiguration

Recommended Action: No action is required.

MCP-3-ALLOCFAIL Format: Failed to allocate memory in %s[%d] for size %d

Explanation: MCP is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action: No action is required.

MCP-3-MCP_INTERNAL_ERROR Format: MCP internal error: %s

Explanation: Internal error is encountered

Recommended Action: No action is required.

MCP-3-ISTACKREGISTER Format: Failed to register istack - %s

Explanation: Failed to register istack. [char] identifies the reason.

Recommended Action: No action is required.

MFDM-2-INTERNAL_ERROR Format: MFDM-%s 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.

MFDM-2-DOWNLOAD_TIMEOUT Format: Download of L2/L3 route databases timed out : download_in_progress_slots 0x%x for database %s %s %s

Explanation: Download of L2/L3 route databases timed out. Download triggered by VMM insert request.

Recommended Action: No action is required.

MFDM-2-DI_REUSE Format: LTL node exists with DI %d oiflist_index %d type %d and same DI returned for oiflist_index %d type %d Please collect show tech-support forwarding distribution l2/l3 multicast and show tech-support pixm.

Explanation: PIXM returned duplicate DI.

Recommended Action: No action is required.

MFDM-2-REF_OUTOFSYNC Format: In Decrement ltl_node ref_count: %d is less than count: %d passed in for DI: 0x%x, oiflist_index: %d, type: %d. Possible PI/PD refcount out-of-sync. Please collect show tech-support forwarding distribution l2/l3 multicast and show tech-support pixm.

Explanation: MFDM PI/PD refcount out-of-sync

Recommended Action: No action is required.

MRIB-6-USAGE Format: Usage: mrib [-h] [-d] [-m \]

Explanation: Usage for starting MRIB process.

Recommended Action: No user action is required.

MRIB-6-MEMORY_OPTION Format: memory size must be \>= 16MB and \

Explanation: Invalid memory size specified for MRIB process.

Recommended Action: No user action is required.

MRIB-6-SHUTDOWN Format: Shutting down MRIB process

Explanation: MRIB process is shutting itself down.

Recommended Action: No user action is required.

MRIB-6-SHUTDOWN_FAILED Format: Shutting down of MRIB process failed: %s

Explanation: MRIB process is shutting itself down.

Recommended Action: No user action is required.

MRIB-2-STARTUP_FAILURE Format: Startup failure: %s

Explanation: An unrecoverable software error has occurred during MRIB startup.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

MRIB-2-RES_MGR Format: Error returned from %s for %d keys, errno: 0x%08x (%s) in %s(). Current reservation is %d, new size is %d

Explanation: The resource manager returned an error to MRIB, while MRIB was performing an action relating to its shared memory

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

MRIB-2-API_INIT_SEM Format: Failed to init the client API semaphore: %s, create: %s

Explanation: MRIB could not create the semaphore that protects access to the shared memory between MRIB and its clients.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

MRIB-3-NO_SET_PRIORITY Format: Failed to set policy or priority

Explanation: MRIB process could not set itself process priority, exiting.

Recommended Action: No user action is required.

MRIB-3-INIT_SDB Format: %s Return Code: 0x%x Error String: %s

Explanation: SDB initialization failed

Recommended Action: No user action is required.

MRIB-3-OPCODE_REGISTER Format: %s opcode: 0x%x ErrorString: %s

Explanation: Opcdoe registration failed

Recommended Action: No user action is required.

MRIB-3-UNKNOWN_URIB Format: Received unknown URIB message type: %d

Explanation: MRIB process received unknown message from URIB, dropped.

Recommended Action: No user action is required.

MRIB-3-UNKNOWN_MRIB_MINOR Format: mrib_main(): unknown minor mtype: %d

Explanation: MRIB process received unknown Interprocess message, dropped.

Recommended Action: No user action is required.

MRIB-3-UNKNOWN_MRIB_MAJOR Format: mrib_main(): unknown major mtype: %d

Explanation: MRIB process received unknown Interprocess message, dropped.

Recommended Action: No user action is required.

MRIB-3-UNKNOWN_MFDM_OPC Format: mrib_mfdm_main(): reeceived unknown opcode %d

Explanation: MRIB process received unknown Interprocess message from MFDM, dropped.

Recommended Action: No user action is required.

MRIB-3-MALLOC_FAILED Format: %s failed for %s

Explanation: MRIB process is out of free memory.

Recommended Action: Configure the network or router to decrease the number of routes.

MRIB-3-BITFIELD_FAILED Format: %s failed in %s

Explanation: MRIB process could not execute the bitfield operation.

Recommended Action: Dump core, then reload the stack.

MRIB-3-NO_MPIB Format: Unable to get mpib index in mrib_register_internal()

Explanation: MRIB process cannot register the protocol as it has run out of PIB indices.

Recommended Action: Dump core, then reload the stack.

MRIB-3-NO_TIMER Format: Could not create stale timer for \%s\""

Explanation: MRIB process cannot stale the routes for this procotol.

Recommended Action: Dump core, then reload the stack.

MRIB-3-PT_FAILED Format: %s failed in %s

Explanation: MRIB process failed to update route-table for this event.

Recommended Action: Dump core, then reload the stack.

MRIB-3-INHERIT_FAILED Format: mrib_inherit_oifs(): bitfield is set but oif doesn't exist

Explanation: MRIB process failed in inheriting OIFs for the (S,G) from (*,G).

Recommended Action: No user action is required.

MRIB-3-NO_GROUP Format: Unable to create group entry for %s

Explanation: MRIB process unable to create the route entry in its route-table.

Recommended Action: No user action is required.

MRIB-3-NO_SOURCE Format: Unable to create source entry for %s

Explanation: MRIB process unable to create the route entry in its route-table.

Recommended Action: No user action is required.

MRIB-3-NO_MPIB_FOR_ROUTE Format: Unable to creates mpib entry for %s for mpib %s in VRF %s

Explanation: MRIB process unable to create the route entry in its route-table.

Recommended Action: No user action is required.

MRIB-3-NO_FREE_SOURCE Format: Unable to free source entry for %s

Explanation: MRIB process unable to delete a route-table entry.

Recommended Action: No user action is required.

MRIB-3-NO_FREE_GROUP Format: Unable to free group entry for %s

Explanation: MRIB process unable to delete a route-table entry.

Recommended Action: No user action is required.

MRIB-3-MQ_FAILED Format: %s failed in %s, errno: %s, for %s

Explanation: MRIB process failed to access the message-queue.

Recommended Action: No user action is required.

MRIB-3-MTS_FAILED Format: %s failed in %s, errno: %s, for %s

Explanation: MRIB process failed to access the mts-queue.

Recommended Action: No user action is required.

MRIB-3-SM_FAILED Format: %s failed in %s for segment %s, errno: %s

Explanation: MRIB process failed to access the System shared memory resource.

Recommended Action: No user action is required.

MRIB-3-API_FAILED Format: %s failed

Explanation: MRIB process failed in invoking an API.

Recommended Action: No user action is required.

MRIB-3-MDT_API_FAILED Format: %s failed in %s

Explanation: MRIB process failed in invoking an API.

Recommended Action: No user action is required.

MRIB-3-INVALID_GROUP Format: Operation for invalid group %s received in %s

Explanation: MRIB process received invalid group.

Recommended Action: No user action is required.

MRIB-3-RDLOCK_ASSERT Format: %s:%d: Assert, read-lock not acquired

Explanation: Caller Failed to get MRIB Shared Memory read lock

Recommended Action: No user action is required.

MRIB-3-WRLOCK_ASSERT Format: %s:%d: Assert, write-lock not acquired

Explanation: Caller Failed to get MRIB Shared Memory write lock

Recommended Action: No user action is required.

MRIB-3-MUTEX_INIT Format: Couldn't init mutex %s

Explanation: MRIB process failed to initialize mutex system resource.

Recommended Action: Dump core, then restart component.

MRIB-3-CV_INIT Format: Couldn't init cond var %s

Explanation: MRIB process failed to initialize conditional-variable resource.

Recommended Action: Dump core, then restart component.

MRIB-3-FTM_NO_XID Format: Cannot find FTM buffer, xid: %d

Explanation: MRIB process could not match the sequence number for FTM message, ignored.

Recommended Action: No user action is required.

MRIB-3-MFDM_NO_BUF Format: Cannot find MFDM buffer from route-ack for context %s, table-id 0x%08lx

Explanation: MRIB process could not find a route buffer in it's queue from the MFDM message, ignored.

Recommended Action: No user action is required.

MRIB-3-FTM_BAD_MINOR Format: Unknown FTM mtype: 0x%4x

Explanation: MRIB process received unsupported message type from FTM, ignored.

Recommended Action: No user action is required.

MRIB-3-FTM_BAD_METER Format: %s failed for meter %s in %s

Explanation: MRIB process failed to configure the multicast meter.

Recommended Action: No user action is required.

MRIB-3-MRIB_ALREADY_UP Format: mrib already running, exiting

Explanation: Another MRIB process is already running, this process will shutdown.

Recommended Action: No user action is required.

MRIB-3-TIMER_FAILED Format: could not %s

Explanation: MRIB process failed to configure a timer event.

Recommended Action: Dump core, then reload the stack.

MRIB-3-ACTIVE_TIMER_FAILED Format: active_timer_create() failed for mrib_main()

Explanation: MRIB process failed to create a timer.

Recommended Action: Dump core, then reload the stack.

MRIB-3-PTHREAD_FAILED Format: pthread_create() failed for mrib_main()

Explanation: MRIB process failed to create a task thread.

Recommended Action: Dump core, then reload the stack.

MRIB-3-CONTEXT_BF_FAILED Format: bitfield_create() failed for context %s

Explanation: MRIB process failed to create a bitfield for mrib_ cibtype.

Recommended Action: Dump core, then reload the stack.

MRIB-3-PSS Format: Error returned from %s, errno: 0x%08x (%s) in %s()

Explanation: MRIB called a PSS API which returned an error. The error reported should be examined for the cause.

Recommended Action: ERRMSG

MRIB-3-KSINK_LIB_ERROR Format: %s %s

Explanation: A severe error was encountered during ksink operations.

Recommended Action: No action is required.

MRIB-5-RES_MGR_CHANGE Format: Changed m4route-mem from (%d, %d) to (%d, %d)

Explanation: The requested limit-resource command was adapted to fit the limits in this version.

Recommended Action: No user action is required.

MRIB-5-API_INIT_SEM_CLEAR Format: Cleared the API semaphore from %d

Explanation: The API semaphore was in an unexpected state, and was restored to a correct value.

Recommended Action: No user action is required.

MRIB-3-MTS_SHORT_MSG_ERROR Format: Received short (%d \

Explanation: MRIB recieved an unknown message. The message is dropped

Recommended Action: No user action is required.

MRIB-3-MTS_NO_PAYLOAD_ERROR Format: Received MTS message with no payload on %s queue with opcode %d, dropping it

Explanation: MRIB recieved an unknown message. The message is dropped

Recommended Action: No user action is required.

MRIB-3-TXLIST_CREATE Format: Couldn't create txlist for %s in VRF:%s

Explanation: MRIB failed to create txlist resource.

Recommended Action: No user action is required.

MRIB-3-NO_MARKER Format: Unable to find the txlist marker for VRF:%s for the client: %s

Explanation: MRIB failed to find txlist resource.

Recommended Action: No user action is required.

MRIB-3-NOTIFY_BUF_FAILED Format: Unable to create notification buffer's for client %s, aborting registration.

Explanation: MRIB failed to create notification buffer for a client

Recommended Action: No user action is required.

MRIB-3-CONF_CHECK Format: Failed to %s MRIB confcheck capability with error: %s

Explanation: MRIB failed to update config check capability in the system

Recommended Action: No user action is required.

MRIB-3-SYSMGR_DISPATCH Format: Error returned from sysmgr_dispatch(), errno: %s

Explanation: MRIB called a System Manager API which returned an error.

Recommended Action: Dump core, then restart component.

MRIB-3-MTS_BIND Format: Error returned from mts_bind() for %s mts queue, errno: %s

Explanation: MRIB called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

MRIB-3-MTS_RECV Format: Error returned from mts_recv(), errno: %s

Explanation: MRIB called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

MRIB-3-MTS_DROP Format: Error returned from mts_drop(), errno: %s

Explanation: MRIB called a MTS API which returned an error.

Recommended Action: Dump core, then restart component.

MRIB-3-LIB_MTS_FAILED Format: %s failed in %s, errno: %s, for %s

Explanation: Failure in MRIB library to access mts-queue

Recommended Action: No user action is required.

MRIB-3-LIB_SM_FAILED Format: %s failed to access MRIB shared memory in %s, errno: %s

Explanation: Process failed to access the System shared memory resource.

Recommended Action: No user action is required.

MRIB-3-LIB_API_FAILED Format: %s failed in %s

Explanation: Process failed in invoking an API.

Recommended Action: No user action is required.

MRIB-3-LIB_DUP_REGISTER Format: mrib_register(): duplicate register by \%s\""

Explanation: Dupilcate registration request to the MRIB process, ignored.

Recommended Action: No user action is required.

MRIB-3-LIB_SEM_OP Format: %s:%d: semaphore operation %s failed

Explanation: Caller failed to get perform an operation on the MRIB semaphore

Recommended Action: No user action is required.

MRIB-3-LIB_SEM_INVALID Format: %s:%d: semaphore invalid in %s

Explanation: MRIB semaphore was found to be invalid when performing a semaphore operation

Recommended Action: No user action is required.

BCM_USD-5-BUFFER_THRESHOLD_EXCEEDED Format: Port %2d buffer threshold %d cells[%2.1f%% - ~%1.1fMB] exceeded %d[%d%%]

Explanation: Buffer usage exceeded threshold

Recommended Action: No action is required.

INSTALLER-5-UPGRADE_INITIATED Format: System upgrade initiated.

Explanation: System wide upgrade has been initiated by the user.

Recommended Action: No action is required.

INSTALLER-5-UPGRADE_COMPLETED Format: System upgrade completed.

Explanation: This message indicates system wide upgrade has completed.

Recommended Action: No action is required.

INSTALLER-5-UPGRADE_ABORTED Format: System upgrade aborted.

Explanation: This message indicates that system wide upgrade has aborted.

Recommended Action: No action is required.

INSTALLER-5-UPGRADE_STOPPED Format: System upgrade stopped.

Explanation: This message indicates that system wide upgrade has been stopped by the user.

Recommended Action: No action is required.

INSTALLER-1-UPGRADE_EXCEEDED_DOWNTIME Format: 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.

OSPF-6-START Format: Starting OSPF %s, %s

Explanation: OSPF process is starting due to the specified reason.

Recommended Action: No user action is required.

OSPF-5-ADJCHANGE Format: Nbr %s on %s went %s

Explanation: An OSPF neighborship has just been established. Or a neighborship has just been shutdown.

Recommended Action: No user action is required.

OSPF-5-NBRSTATE Format: Process %s, Nbr %s on %s from %s to %s, %s

Explanation: An OSPF neighbor has just changed state.

Recommended Action: No user action is required.

OSPF-4-CLEANUP Format: OSPF is exiting, reason %s(0x%x)

Explanation: OSPF has been deconfigured or restarted.

Recommended Action: No user action is required.

OSPF-6-SHUTDOWN_REQUEST_FAIL Format: OSPF shutdown request failed, %s

Explanation: OSPF request to system mananger for permission to shutdown was turned down.

Recommended Action: No user action is required.

OSPF-6-DECONFIG_SHUTDOWN Format: OSPF shutting self down via deconfiguration

Explanation: OSPF process is shutting itself down due to the deconfiguration command.

Recommended Action: No user action is required.

OSPF-4-RESTART_SHUTDOWN Format: OSPF shutting self down via restart command

Explanation: OSPF process is shutting itself down due to the restart command.

Recommended Action: No user action is required.

OSPF-6-UNKNOWN_SHUTDOWN Format: OSPF shutting self down due to unknown reason

Explanation: OSPF process is shutting itself down due to unknown reason.

Recommended Action: No user action is required.

OSPF-4-DUPRID Format: Router %s on interface %s is using our routerid, packet dropped

Explanation: Two routers are configured with the same router ID.

Recommended Action: Check all routers on the indicated interface for misconfigurations.

OSPF-4-SELF_LSA Format: context %s: %s

Explanation: Router received an newer copy of an LSA generated by itself. Two routers may be configured with the same router ID or a router which was disconnected from the network has come back.

Recommended Action: Verify if the router ID for the router is unique in the network.

OSPF-1-LOWMEM Format: Low memory condition: %s

Explanation: The router did not have enough memory to store certain data structures.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

OSPF-1-NOMEM Format: Malloc (%ld bytes) failed for: %s

Explanation: The router did not have enough memory to store mentioned data structures.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

OSPF-1-SLABS Format: Could not create %s slabs

Explanation: The router did not have enough memory to reserve space in advance for certain slab data structures.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

OSPF-3-SMALLBUF Format: %s packet doesn't fit in buffer (packet %d/ buffer %d)

Explanation: The router has allocated a packet buffer that was too small.

Recommended Action: No user action is required.

OSPF-3-ROUTEDEL Format: Route deletion %s/%d failed

Explanation: Internal Error.

Recommended Action: No user action is required.

OSPF-3-INVALID_TLV Format: Found corrupted TLV, LSA %s

Explanation: Error while parsing TLV.

Recommended Action: No user action is required.

OSPF-3-MIB_FAIL Format: Failed to %s the MIB with status as %s

Explanation: Error while loading or unloading the MIB.

Recommended Action: No user action is required.

OSPF-3-SNMP_FAIL Format: Failed to %s the SNMP with status as %s

Explanation: Error while registering or deregistering with SNMP.

Recommended Action: No user action is required.

OSPF-3-SNMP_SAP_FAIL Format: Failed to %s the SNMP SAP with status as %s

Explanation: Error while registering or deregistering with SNMP SAP.

Recommended Action: No user action is required.

OSPF-3-MAXLSAS Format: Maximum number of LSAs in domain has been reached

Explanation: The OSPF domain contains more LSAs than this router can store.

Recommended Action: Redesign the network to redistribute less external routes into the OSPF domain.

OSPF-3-MAXIFS Format: Exceeded the limit on interfaces per area [i.e %d]

Explanation: Restricting the number of interfaces per area to avoid problems during lsa generation.

Recommended Action: Reduce the number of interfaces per area.

OSPF-1-INIT Format: Unable to %s %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-1-STARTTHREAD Format: Unable to start thread %s (%d), error %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-1-MCASTJOIN Format: Unable to join %s group on interface %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-1-MCASTLEAVE Format: Unable to leave %s group on interface %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-1-TIMER Format: Unable to create %s timer on interface %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-1-MQSEND Format: Unable to send message %s to %s

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-3-HEAPSIZE Format: Error increasing heap size to %d, error %d

Explanation: Reduced heap size will limit the LSDB size.

Recommended Action: No user action is required.

OSPF-1-TAG Format: Unable to retrieve service tag on %s supervisor

Explanation: An internal software error has occurred.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

OSPF-3-UNKNOWNSIG Format: Received unknown signal: %d

Explanation: An unexpected software interrupts was received.

Recommended Action: No user action is required.

OSPF-4-INVALIDOUT Format: Trying to send packet with packettype %d to %s on %s

Explanation: The router tried to send unknown OSPF packet.

Recommended Action: No user action is required.

OSPF-3-UNAWAKABLE Format: Trying to awake unawakable thread %s

Explanation: Thread cannot be wokenup at this time

Recommended Action: No user action is required.

OSPF-4-WRONGQ Format: Found wrong type of packet (%d) on internal %s queue

Explanation: Did not expect the specified packet type on the given incoming message queue

Recommended Action: No user action is required.

OSPF-4-AF_NO_FUNC Format: Function %s not supported by OSPF version %s

Explanation: Function is not specified for the current address family

Recommended Action: No user action is required.

OSPF-3-CTX Format: Error in subrouter context %s: %s

Explanation: Error related to multiple subrouters and contexts

Recommended Action: No action is required.

OSPF-3-CTX_IF Format: Error in subrouter context for interface %s: %s

Explanation: Error related to interface context

Recommended Action: No action is required.

OSPF-3-MTS_BIND Format: Error returned from mts_bind(), errno: %s

Explanation: OSPF called a MTS API which returned an error.

Recommended Action: No action is required.

OSPF-6-MTS_UNKNOWN_MSG Format: Received unknown MTS message with opcode %d, dropping it

Explanation: OSPF recieved an unknown MTS message. The message will be dropped

Recommended Action: No action is required.

OSPF-3-MTS_RECV Format: Error returned from tsp_mts_recv(), errno: %s

Explanation: OSPF called a MTS API which returned an error.

Recommended Action: No action is required.

OSPF-3-MTS_DROP Format: Error returned from mts_drop(), errno: %s

Explanation: OSPF called a MTS API which returned an error.

Recommended Action: No action is required.

OSPF-3-PSS_READ Format: PSS read for %s information failed

Explanation: OSPF called an PSS API which returned an error.

Recommended Action: No action is required.

OSPF-3-TLV_INTF Format: Failed to convert to %s for %s

Explanation: OSPF called an TLV intf which returned an error.

Recommended Action: No action is required.

OSPF-3-MTS_NOTIFY Format: Error returned from mts_send_notify(), errno: %s

Explanation: OSPF called a MTS API which returned an error.

Recommended Action: No action is required.

OSPF-3-CMI_ERR Format: CMI error: %s.

Explanation: CMI returned an error

Recommended Action: No user action is required.

OSPF-3-CMI_NO_VRF_ERR Format: CMI error: No %s VRF information found

Explanation: CMI returned an error

Recommended Action: No user action is required.

OSPF-4-IF_ERR Format: Packet from %s received on %s interface %s

Explanation: A OSPF packet not belonging to this interface was received

Recommended Action: No action is required.

OSPF-4-PKTLEN_ERR Format: Packet received from %s on %s has length %d which is less than %s %d

Explanation: A OSPF packet with invalid length was received

Recommended Action: No action is required.

OSPF-4-AREA_ERR Format: Packet from %s on %s received for wrong area %s

Explanation: A OSPF packet not belonging to this area was received

Recommended Action: No action is required.

OSPF-4-PKTTYPE_ERR Format: Unknown type %d received from %s on %s

Explanation: A OSPF packet with incorrect packet type was received

Recommended Action: No action is required.

OSPF-4-VERSION_ERR Format: Bad ospf version %d received from %s on %s

Explanation: A OSPF packet with incorrect version number was received

Recommended Action: No action is required.

OSPF-4-SOURCE_ERR Format: Bad source address %s - ours on %s

Explanation: A OSPF packet with our own source address was received

Recommended Action: No action is required.

OSPF-4-SRC_INVALID Format: Invalid src address %s, should not be seen on %s

Explanation: A OSPF packet packet with source address not on this network was received

Recommended Action: No action is required.

OSPF-4-CKSM_ERR Format: Bad OSPF checksum in packet %hx computed %hx from %s on %s

Explanation: A OSPF packet with invalid checksum was received

Recommended Action: No action is required.

OSPF-4-AUTH_ERR Format: Received packet from %s on %s with bad authentication %hx

Explanation: A OSPF packet with mismatched authentication type was received

Recommended Action: No action is required.

OSPF-4-NEIGH_ERR Format: Neighbor %s not found, packet dropped

Explanation: A non-hello OSPF packet with no neighbor was received

Recommended Action: No action is required.

OSPF-4-SRC_MCAST Format: Bad source address %s - multicast on %s

Explanation: A OSPFv3 packet with muticast source address was received

Recommended Action: No action is required.

OSPF-4-DEST_INVALID Format: Bad destination address %s

Explanation: A OSPFv3 packet with muticast source address was received

Recommended Action: No action is required.

OSPF-4-REDIST_MAX_PFX Format: Redistribution prefix limit has been reached - %d prefixes

Explanation: Check if redistribution of large number of prefixes is desired and has not been configured by mistake

Recommended Action: No action is required.

OSPF-4-REDIST_THR_PFX Format: Redistribution prefix threshold has been reached - %d prefixes

Explanation: Check if redistribution of large number of prefixes is desired and has not been configured by mistake

Recommended Action: No action is required.

OSPF-2-REDIST_VPN Format: Received VPN routes without extended community for %s/%d

Explanation: An internal error

Recommended Action: No action is required.

OSPF-3-IF_INVALID Format: Unable to find interface %s

Explanation: OSPF could not find an interface

Recommended Action: No action is required.

OSPF-3-SET_OVERLOAD Format: Setting overload state for %s

Explanation: OSPF sets the configuration to sends the LSAs with max-metric cost

Recommended Action: No action is required.

OSPF-3-CLEAR_OVERLOAD Format: Clearing overload state for %s

Explanation: OSPF resets the configuration to sends the LSAs with normal cost

Recommended Action: No action is required.

PIXM-2-PIXM_SYSLOG_MESSAGE_TYPE_CRIT Format: %s

Explanation: PIXM has encountered a critical error

Recommended Action: Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'

PIXM-3-PIXM_SYSLOG_MESSAGE_TYPE_ERR Format: %s

Explanation: PIXM has encountered a error

Recommended Action: Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'

PIXM-4-PIXM_SYSLOG_MESSAGE_TYPE_WARNING Format: %s

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'

PIXM-7-PIXM_SYSLOG_MESSAGE_TYPE_DEBUG Format: %s

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'

PLATFORM-0-SUP_WRONGSLOTNUM Format: Supervisor powered up in WRONG SLOT:%d (Serial number %s)

Explanation: The supervisor is comming up in wrong slot [decimal digit].

Recommended Action: No action is required.

PLATFORM-2-SYS_IDPROMBAD_RECOVER_PASS Format: Chassis IDPROM %d 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.

PLATFORM-2-SYS_IDPROMBAD_RECOVER_FAIL Format: Chassis IDPROM %d 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.

PLATFORM-5-PS_FOUND Format: Power supply %d found (Serial number %s)

Explanation: Power Supply is detected.

Recommended Action: No action is required.

PLATFORM-2-PS_DETECT Format: Power supply %d detected but shutdown (Serial number %s)

Explanation: Power Supply is detected but shutdown.

Recommended Action: Please perform a 'show environment power' and 'show platform internal info' to collect more information.

PLATFORM-5-PS_STATUS Format: PowerSupply %d current-status is %s %s

Explanation: module in slot [decimal digit] changed status.

Recommended Action: No action is required.

PLATFORM-2-PS_REMOVE Format: Power supply %d removed (Serial number %s)

Explanation: Power Supply is removed.

Recommended Action: No action is required.

PLATFORM-2-PS_OK Format: Power supply %d ok (Serial number %s)

Explanation: Power Supply is ok.

Recommended Action: No action is required.

PLATFORM-2-PS_UNSUPPORTED Format: Detected an unsupported power supply %d %s for CISCO Multilayer Switch (Serial number %s)

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.

PLATFORM-5-FAN_DETECT Format: Fan module %d (Serial number %s) %s detected

Explanation: Fan module is detected

Recommended Action: No action is required.

PLATFORM-5-FAN_STATUS Format: Fan module %d (Serial number %s) %s current-status is %s

Explanation: Fan module changed status

Recommended Action: No action is required.

PLATFORM-2-FAN_REMOVED Format: Fan module %d (Serial number %s) %s removed

Explanation: Fan module is removed

Recommended Action: No action is required.

PLATFORM-0-SYS_SHUTDOWN Format: System shutdown in %d 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.

PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED Format: Failed to load linecard module drivers

Explanation: failed to load drivers.

Recommended Action: Image is possibly corrupt. Try to load a different image.

PLATFORM-2-PFM_SYSTEM_SHUTDOWN_TRIGGER Format: System shutdown due to %s policy trigger)msgdef_explanation("Policy/trigger initiated a system shutdown "

Recommended Action: None

PLATFORM-2-PFM_SYSTEM_RESET Format: Manual system restart from Command Line Interface)msgdef_explanation("User initiated a system reload from the CLI"

Recommended Action: None

PLATFORM-2-PFM_MODULE_POWER_OFF Format: Manual power-off of %s from Command Line Interface)msgdef_explanation("User initiated a module power-off from the CLI"

Recommended Action: None

PLATFORM-2-PFM_MODULE_POWER_ON Format: Manual power-on of %s from Command Line Interface)msgdef_explanation("User initiated a module power-on from the CLI"

Recommended Action: None

PLATFORM-2-PFM_MODULE_POWER_OFF_TRIGGER Format: Power-off %s due to %s policy trigger )msgdef_explanation("Policy trigger initiated a module poweroff"

Recommended Action: None

PLATFORM-2-PFM_MODULE_RESET Format: Manual restart of Module %d from Command Line Interface)msgdef_explanation("User initiated a module reload from the CLI"

Recommended Action: None

PLATFORM-2-PFM_XBAR_RESET Format: Manual restart of Xbar %d from Command Line Interface)msgdef_explanation("User initiated a xbar reload from the CLI"

Recommended Action: None

PLATFORM-3-EJECTOR_STAT_CHANGED Format: Ejectors' status in slot %d has changed, %s Ejector is %s, %s Ejector is %s)msgdef_explanation("Ejector status has changed"

Recommended Action: None

PLATFORM-2-PFM_PREP_DEEP_SLEEP Format: Supervisor module in slot %d 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.

PLATFORM-2-MEMORY_ALERT_RECOVERED Format: Memory Status Alert : %s)msgdef_explanation("Memory alert event received "

Recommended Action: None

PLATFORM-2-MEMORY_ALERT Format: Memory Status Alert : %s. Usage %s%% of Available Memory)msgdef_explanation("Memory alert event received "

Recommended Action: None

PLATFORM-1-PFM_ALERT Format: %s

Explanation: Platform Alert

Recommended Action: No action is required.

PLATFORM-5-FEX_FAN_DETECT Format: Fex %d Fan Module %d detected

Explanation: Fex Fan module is detected

Recommended Action: No action is required.

PLATFORM-5-FEX_FAN_REMOVE Format: Fex %d Fan Module %d removed

Explanation: Fex Fan module is removed

Recommended Action: No action is required.

PLATFORM-5-FEX_PS_FOUND Format: Fex %d Power Supply %d found (Serial number %s)

Explanation: Fex power supply is found

Recommended Action: No action is required.

PLATFORM-5-FEX_PS_REMOVE Format: Fex %d Power Supply %d removed (Serial number %s)

Explanation: Fex power supply is removed

Recommended Action: No action is required.

PLATFORM-2-SUP_UNSUPPORTED Format: Unsupported card detected in supervisor slot %d powered down

Explanation: The module in slot [decimal digit] has been powered down.

Recommended Action: No action is required.

POLICY_MGR-6-POLICY_MGR_PPF_NOTIF Format: PPF notification: %s

Explanation: The PPF generated notification

Recommended Action: No action is required.

POLICY_MGR-4-POLICY_MGR_PPF_WARNING Format: PPF warning: %s

Explanation: The PPF generated warning

Recommended Action: No action is required.

POLICY_MGR-3-POLICY_MGR_PPF_ERROR Format: PPF error: %s

Explanation: The PPF generated error

Recommended Action: No action is required.

RPM-3-INT_ERROR Format: %s in %s()

Explanation: RPM encountered an error during internal processing

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-7-INFRA_SYSERR Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: RPM called an infra API which returned 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.

RPM-2-PTHREAD Format: %s failed with error - %d in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-2-PSS_SYNC_BUFFER Format: Crossed pss sync buffer size limit of %d with payload size %d - in %s()

Explanation: RPM tried to PSS sync a message exceeding the maximum allowed size

Recommended Action: No action is required.

RPM-6-RESTART_SHUTDOWN Format: RPM shutting self down via restart command in %s()

Explanation: RPM process is shutting itself down due to the restart command.

Recommended Action: No user action is required.

RPM-6-MTS_UNKNOWN_MSG Format: Received unknown MTS message with opcode %d, dropping it in %s()

Explanation: RPM received an unknown message. The message is dropped

Recommended Action: No user action is required.

RPM-3-MTS_RECV Format: Error returned from tsp_mts_recv(), errno: %s (0x%08x) in %s()

Explanation: An MTS API returned an error while RPM was receiving on an MTS queue

Recommended Action: No user action is required.

RPM-3-MTS_SEND Format: Error returned from mts_send(), errno: %s (0x%08x) in %s()

Explanation: An MTS API returned an error while RPM was sending an MTS message

Recommended Action: No user action is required.

RPM-3-MTS_DROP Format: Error returned from mts_drop(), errno: %s (0x%08x) in %s()

Explanation: An MTS API returned an error when RPM tried to drop a message

Recommended Action: No user action is required.

RPM-3-ISSU_PREUPG_FAILED Format: ISSU Preupgrade failed

Explanation: Please remove the incompatible RPM/PBR config and restart ISSU.

Recommended Action: No user action is required.

RPM-2-SRV_INIT_API_FAIL Format: %s failed during initialization in %s()

Explanation: RPM called a server API during initialization which returned an error.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-2-PPF_SES_VERIFY Format: PPF session verify failed in client %s with an error 0x%08x(%s)

Explanation: RPM encountered an error while pushing PBR policy changes during the verify stage to PBR clients

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-2-PPF_SES_COMMIT Format: PPF session commit failed in client %s with an error 0x%08x(%s)

Explanation: RPM encountered a serious error while committing the verified PBR policy changes to PBR clients

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-2-PPF_SES_ABORT Format: PPF session abort failed in client %s with an error 0x%08x(%s)

Explanation: RPM encountered an error during PPF abort operation.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-2-PPF_SES_RQST Format: PPF session request failed in client %s with an error 0x%08x(%s)

Explanation: RPM encountered an error while requesting PBR statistics from PBR clients

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-2-MALLOC_FAILED Format: malloc() failed for allocating %s in %s()

Explanation: RPM process is out of heap memory

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-2-SMALLOC_FAILED Format: smalloc() failed for allocating %s in %s()

Explanation: RPM process is out of shared memory. This could be due to temporary increase in the number of policies configured to a very high value

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-7-API_FAILED Format: %s - failed in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-API_FAILED_STR_NUM Format: %s - failed for %s %d in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-API_FAILED_STR_STR Format: %s - failed for %s %s in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-API_FAILED_STR Format: %s - failed for %s in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-API_FAILED_NUM Format: %s - failed for %d in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-3-LIC_REG_FAILED Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: Licensing API failed while registering for license change notifications.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-3-LIC_CHECKIN_FAILED Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: Licensing API failed to check in a license.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-3-LIC_CHECKOUT_FAILED Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: Licensing API failed to check out a license.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-3-LOAD_PARSE_TREE Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: API failed to load parse tree for PBR 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.

RPM-3-UNLOAD_PARSE_TREE Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: API failed to unload parse tree for PBR 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.

RPM-3-BUILD_LIC_REQ Format: %s failed with error - %s (0x%08x) - in %s()

Explanation: API failed to build a license request to recheckout a license.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-7-LIB_API_FAILED Format: %s - failed in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-2-LIB_MALLOC_FAILED Format: malloc() failed for allocating %s in %s()

Explanation: RPM API library is out of heap memory

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

RPM-7-LIB_INT_ERROR Format: %s in %s()

Explanation: RPM API encountered an error during internal processing

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RPM-7-LIB_MTS_SEND Format: Error returned from mts_send(), errno: %s in %s()

Explanation: An MTS API returned an error while RPM was sending an MTS message.

Recommended Action: No user action is required.

RPM-7-LIB_API_FAILED_STR Format: %s - failed for %s in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-LIB_API_FAILED_NUM Format: %s - failed for %d in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-7-LIB_API_FAILED_NUM_NUM Format: %s - failed for %d %d in %s()

Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.

Recommended Action: No user action is required.

RPM-6-LIB_MATCH_IGNORED Format: The command %s in seq. %u of route-map %s is ignored in %s()

Explanation: A route-map match command has been ignored.

Recommended Action: No user action is required.

RPM-7-LIB_KEYCHAIN Format: Unexpected keychain result :%s

Explanation: Unexpected result during RPM keychain API processing

Recommended Action: No user action is required.

SATMGR-5-FEX_PORT_STATUS_NOTI Format: Uplink-ID %d of Fex %d that is connected with %s changed its status from %s to %s

Explanation: Fex [decimal-digit] changed port status

Recommended Action: No action is required.

SATMGR-2-FEX_PORT_STATUS_CRIT Format: Uplink-ID %d of Fex %d that is connected with %s changed its status from %s to %s

Explanation: Fex [decimal-digit] changed port status

Recommended Action: No action is required.

SATMGR-5-PINNING_CHANGED Format: Fex %d pinning information is changed

Explanation: Fex pinning information changed

Recommended Action: No action is required.

SATMGR-5-FEX_ENABLED Format: FEX Enabled

Explanation: FEX Service Enabled

Recommended Action: No action is required.

SATMGR-5-FEX_DISABLED Format: FEX Disabled

Explanation: FEX Service Disabled

Recommended Action: No action is required.

SATMGR-5-SATMGR_DISABLE_FAILED Format: Disabling of feature FEX failed. Please remove FEX related configs from interfaces

Explanation: Disabling of FEX feature failed

Recommended Action: No action is required.

SATMGR-2-FEX_NOT_ONLINE_SUP_ISSU Format: FEX %d did not come online after SUP ISSU

Explanation: FEX did not come online after sup ISSU

Recommended Action: No action is required.

SATMGR-2-FEX_ONLINE Format: FEX %d has come ONLINE

Explanation: FEX has come ONLINE

Recommended Action: No action is required.

SATMGR-2-FEX_OFFLINE Format: FEX %d has gone OFFLINE

Explanation: FEX has gone OFFLINE

Recommended Action: No action is required.

SATMGR-2-NOHMS_ENV_FEX_ONLINE Format: %s

Explanation: Fex on-line

Recommended Action: show inventory

SATMGR-2-NOHMS_ENV_FEX_OFFLINE Format: %s

Explanation: Fex off-line

Recommended Action: show inventory

SATMGR-2-FEX_OFFLINE_WITH_REASON Format: FEX %d has gone OFFLINE because %s.

Explanation: FEX has gone OFFLINE because of the specified reason.

Recommended Action: No action is required.

COOP-2-COOP_INIT_FAILURE Format: %s(%d): %s

Explanation: COOP initialization failure

Recommended Action: No action is required.

COOP-2-COOP_FU_INIT_FAILURE Format: %s %s

Explanation: COOP fu initialization failure

Recommended Action: No action is required.

COOP-6-COOP_INIT_INFO Format: %s(%d): %s

Explanation: COOP initialization information

Recommended Action: No action is required.

COOP-6-COOP_MTS_INIT_INFO Format: %d: %s

Explanation: COOP MTS initialization information

Recommended Action: No action is required.

COOP-2-COOP_MTS_INIT_FAILURE Format: %d: %s

Explanation: COOP MTS initialization failure

Recommended Action: No action is required.

TM-5-TM_ENABLED Format: Tunnel Enabled

Explanation: Tunnel Service Enabled

Recommended Action: No action is required.

TM-5-TM_DISABLED Format: Tunnel Disabled

Explanation: Tunnel Service Disabled

Recommended Action: No action is required.

TM-7-TM_INFO Format: %s

Explanation: Tunnel Service info

Recommended Action: No action is required.

TM-3-HW_PROGRAMMING_FAILED Format: for %s, reason %s

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

TM-4-TM_MTU_PROGRAMMING Format: Programming %s mtu %d...

Explanation: Programming [chars] mtu [int]

Recommended Action: No action is required.

TM-4-TM_MTU_PROGRAMMING_FAILED Format: %s mtu %d programming failed! status 0x%x

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

TM-4-TM_DF_PROGRAMMING Format: Programming %s DF(dont fragment) df.sel %d df.val %d

Explanation: Programming [chars] DF df.sel [int] df.val [int]

Recommended Action: No action is required.

TM-4-TM_DF_PROGRAMMING_FAILED Format: %s DF(dont fragment) programming failed! status 0x%x

Explanation: [chars] DF programming failed! status [int]

Recommended Action: capture \show tech-support tunnel \ to identify why df flag programing failed

TM-5-IF_STATE_UPDATE Format: Interface %s is %s reason %s

Explanation: Interface [char] is [char] reason [char]

Recommended Action: No action is required.

TM-5-IF_CREATED Format: Interface %s is created

Explanation: Interface [char] is created

Recommended Action: No action is required.

TM-5-IF_CREATE_FAILED Format: Interface %s creation failed due to [0x%x] %s

Explanation: Interface [char] is creation failed due to [int] [char]

Recommended Action: No action is required.

TM-5-IF_DELETED Format: Interface %s is deleted

Explanation: Interface [char] is deleted

Recommended Action: No action is required.

TM-5-IF_CLEAR_COUNTER Format: Interface %s counters is cleared

Explanation: Interface [char] counters is cleared

Recommended Action: No action is required.

TM-5-PPF_SESSION_FAILED Format: session id %llx type %s for %s failed error %x %s

Explanation: session id [int] type [char] for [char] failed error [int] [char]

Recommended Action: No action is required.

TM-2-FEATURE_ENABLE_FAILED Format: failed to enable feature tunnel, reason %s (0x%x)

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\

TM-2-TM_F2_ONLY_VDC Format: 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\

UFDM-2-INTERNAL_ERROR Format: Internal error: %s, 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.

UFDM-2-DNLD_TIMEDOUT Format: Download timer expired: %s

Explanation: UFDM download timer expired. Collect show tech-support forwarding l3 unicast for futher analysis.

Recommended Action: No action is required.

UFDM-2-FIB_ROUTE_UPDATE_ERR Format: Route update error from slot %d FIB

Explanation: FIB returned route update error. Collect show tech-support forwarding l3 unicast for futher analysis.

Recommended Action: No action is required.

URIB-2-STARTUP_FAILURE Format: Startup failure: %s

Explanation: An unrecoverable software error has occurred during URIB startup.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-2-BAD_PT Format: Possible Patricia tree corruption in %s

Explanation: An unrecoverable software error has occurred because of a bad route table.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-2-TOO_MANY_CLIENTS Format: %s client \%s\""

Explanation: URIB cannot add this client because the URIB client limit has already been reached.

Recommended Action: Kill component and don't restart it.

URIB-2-TIMER_LIB Format: %s %s

Explanation: The timer library returned an error, causing an unrecoverable problem for URIB.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-2-RES_MGR Format: Error returned from %s, errno: 0x%08x (%s) in %s()

Explanation: The resource manager returned an error to URIB, while URIB was performing an action relating to its shared memory

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-2-API_INIT_SEM Format: Failed to init the client API semaphore: open: %s, create: %s

Explanation: URIB could not create the semaphore that protects access to the shared memory between URIB and its clients.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-2-NOSMEM Format: Failed to allocate shared memory for %s

Explanation: URIB has run out of shared memory to store routes and related information. This condition can be caused by a temporary increase in the number of routes in the network, or a general network or router misconfiguration.

Recommended Action: Configure the network or router to decrease the number of routes, or reconfigure the shared memory through the following vdc mode commands: 'limit-resource u4route-mem min \ max \' or 'limit-resource u6route-mem min \ max \'

URIB-2-NOPMEM Format: Failed to allocate private memory for %s

Explanation: URIB has run out of private memory. This condition can be caused by a temporary increase in the number of routes in the network, or a general network or router misconfiguration.

Recommended Action: Configure the network or router to decrease the number of routes, or add additional memory to the router.

URIB-3-PTADD_ERROR Format: Could not add %s/%d to the %s pt, error code %d

Explanation: A severe route table error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-PTDEL_ERROR Format: Could not delete %s/%d from the URIB pt, error code %d

Explanation: A severe route table error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-CCMARKERERROR Format: Mismatch in marker_elem = %u and urib_cc_end_download_marker = %u for tib: %s

Explanation: An severe error was enountered during Consistency Checker

Recommended Action: No action is required.

URIB-3-CCPENDING Format: Previous Consistency Check has not yet completed

Explanation: Previous Consistency Check has not yet completed

Recommended Action: No action is required.

URIB-3-AVLINIT_ERROR Format: Could not init %s avl for VRF %s

Explanation: URIB was unable to correctly initialise an AVL data structure.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-3-AVLADD_ERROR Format: Could not add %s (0x%08x) to the %s avl

Explanation: URIB was unable to add a piece of data to an AVL data structure.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-3-QADD_ERROR Format: Could not add %s to the %s queue

Explanation: A severe queue error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-HTADD_ERROR Format: Could not add %s to the %s hash table

Explanation: A severe hash table error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-ADD_ERROR Format: Client \%s\" could not add %s/%d to the %s"

Explanation: A severe error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-MOD_ERROR Format: Client \%s\" could not modify %s/%d: %s"

Explanation: A severe error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-DEL_ERROR Format: Could not delete %s/%d from %s

Explanation: A severe error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-NH_RESOLV_ADD_ERROR Format: Could not add %s/%d to the %s (%d) resolve buffer

Explanation: A severe error was encountered. The system may run into more errors because of this problem.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-COPY_ERROR Format: Could not copy %s for %s/%d

Explanation: A severe error was encountered during route optimisation. The system may run into more errors because of this problem.

Recommended Action: No action is required.

URIB-3-KSINK_LIB_ERROR Format: %s %s

Explanation: A severe error was encountered during ksink operations. The system may run into more errors because of this problem.

Recommended Action: No action is required.

URIB-3-RPM_LIB_ERROR Format: %s %d

Explanation: An RPM library function returned an error.

Recommended Action: No action is required.

URIB-3-SDWRAP_LIB_ERROR Format: %s %s

Explanation: A SDWrap library function returned an error.

Recommended Action: No action is required.

URIB-3-ADD_PATH_ERROR Format: %s: could not add path for client \%s\"."

Explanation: A route add operation has failed for the given client. There may be a previous error message that further explains the problem.

Recommended Action: No action is required.

URIB-3-ADD_RPATH Format: Client \%s\" added %s/%u via not found rnh %s/%u%%%s"

Explanation: A route add operation has failed for the given client. This may be a transient 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.

URIB-3-ADD_TPATH Format: Client \%s\" added %s/%u via tableid 0x%08x : %s"

Explanation: A route add operation has failed for the given client. This was because the tableid could not be found. This may be a transient 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.

URIB-3-DEL_PATH_ERROR Format: %s: could not del path for client \%s\"."

Explanation: A route add operation has failed for the given client. There may be a previous error message that further explains the problem.

Recommended Action: No action is required.

URIB-3-NOT_INIT_L3VM_ERROR Format: L3VM info for table id 0x%08x from client \%s\" not available - URIB not initialised with L3VM"

Explanation: A client tried to add some information to the URIB, before URIB has registered for the table information. The client should be restarted.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-NO_L3VM_INFO_ERROR Format: no L3VM info for table id 0x%08x from client \%s\" - unknown to L3VM"

Explanation: A client tried to add some information to URIB and provided a Table-Id that is unknown in the system. The client should be restarted.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-NO_L3VM_LIMITS Format: Could not get routing table limits from L3VM

Explanation: URIB could not pull the routing limits for the table. L3VM should be restarted.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-TABLE_CREATE_ERROR Format: Failed to create table info for VRF %s for client \%s\""

Explanation: URIB could not create its table data structure for the VRF being created. There may be further errors that indicate the failure in more detail. The shown VRF should be reconfigured in the system. i.e. in global configuration, 'no vrf context \'

Recommended Action: Requires operator to intervene.

URIB-3-TABLE_STATE_ERROR Format: Table state %s for VRF %s for client \%s\""

Explanation: URIB received a request from a client for a given VRF, but the given VRF was in a state where that request is not permitted

Recommended Action: Requires operator to intervene.

URIB-3-INSTANCE_CREATE_ERROR Format: ERRMSG_LIMIT_DEF

Explanation: URIB could not create its data structures for a client in the shown VRF. There may be further errors to indicate the failure in more detail. The shown VRF should be reconfigured in the client. i.e. in router sub-mode configuration, 'no vrf \'

Recommended Action: Requires operator to intervene.

URIB-3-GET_INSTANCE_ERROR Format: instance not found for client \%s\" in VRF %s"

Explanation: URIB could not find its data structures for a client in the shown VRF. The shown VRF should be reconfigured in the client. i.e. in router sub-mode configuration, 'no vrf \'

Recommended Action: Requires operator to intervene.

URIB-3-GENERAL_PTHREAD_ERROR Format: Thread %d: %s

Explanation: The POSIX pthread library returned an error to URIB.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-EPID_MIS_MATCH_ERROR Format: \%s\" epid (%u) does not match known epid (%u)"

Explanation: The id a client provided does not match the id that URIB currently has stored for the client. The client probably restarted ungracefully and URIB has the old id.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-GENERAL_UI_ERROR Format: %s

Explanation: The shown error occured while the user interface was processing a request. The request should be tried again.

Recommended Action: Requires operator to retry the request.

URIB-3-ASSERT_ERROR Format: "%s:%d: Assertion \"%s\" failed."

Explanation: An internal software error has occured. An assertion held to be true 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.

URIB-3-FILE_OPEN_ERROR Format: File open error: %s

Explanation: This message is for internal debugging only.

Recommended Action: No action is required.

URIB-3-FILE_WRITE_ERROR Format: File write error: %s

Explanation: This message is for internal debugging only.

Recommended Action: No action is required.

URIB-3-OPEN_CLIENT_SHM_ERROR Format: "Failed to open client shared memory \"%s\": %s"

Explanation: The calling process failed with the shown error while trying to open the named URIB shared memory region. The status of the memory is shown in 'show process memory shared'.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-SEND_TO_ERROR Format: "Send to URIB failed: %s"

Explanation: The calling process was unable to send a message to URIB.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-SEND_FROM_ERROR Format: Send from URIB to client \%s\" failed: %s"

Explanation: URIB was unable to send a message to the shown client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-SEND_NOTIF_ERROR Format: Failed to send %s notification buffer to client \%s\"; retried %lu times"

Explanation: URIB was unable to send a notification to a client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-RNH_LOOP_ERROR Format: Number of prefixes forming rnh loop exceeds %d\n Flagging route %s/%d from client \%s\" with rnh %s/%d\n as causing rnh loop"

Explanation: URIB detected a loop between routes installed in the RIB. The message shows which client caused the loop.

Recommended Action: Requires operator to intervene.

URIB-3-XRI_TYPE_ERROR Format: Unknown XRI type %u

Explanation: URIB detected unknown eXtended route information while displaying a next-hop address.

Recommended Action: No user action is required.

URIB-3-INCONSISTENT_STRUCTURE Format: %s

Explanation: Unexpected remaining state removed during RIB cleanup.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-INCONSISTENT_ROUTE Format: %s: %s/%d via %s

Explanation: Unexpected remaining route removed during RIB cleanup.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-INCONSISTENT_RNH Format: %s: %s/%d

Explanation: Unexpected remaining recursive next-hop removed during RIB cleanup

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-INCONSISTENT_SUMMARY Format: %s: routes %d, rnh's %d

Explanation: Unexpected remaining state for client during RIB cleanup. Use the 'show routing ipv4 unicast internal event-history errors' CLI command for more information.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-RANGE_CHECK_ERR Format: "Range check of %s failed from %s (0x%08x)"

Explanation: The value provided is outside of the acceptable range.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-MORE_INFO_ERROR Format: Client \%s\": %s"

Explanation: This error provides further information about the previous error. Action should be taken depending on the previous error logged.

Recommended Action: No user action is required.

URIB-3-MORE_MTS_INFO_ERROR Format: source SAP is: %d dest SAP is: %d

Explanation: This error provides further information about the previous MTS error. Action should be taken depending on the previous MTS error logged.

Recommended Action: No user action is required.

URIB-3-PSS Format: Error returned from %s, errno: 0x%08x (%s) in %s()

Explanation: URIB called a PSS API which returned an error. The error reported should be examined for the cause.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-3-UFDM_MTSSEND_FAILURE Format: MTS send; to UFDM failed with unexpected error %d

Explanation: URIB was unable to send a route update to UFDM. This means there will be a route missing from the FIB.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-4-ROUTELIMIT_EXCEEDED Format: Number of routes (%llu) reached or exceeds configured limit (%lu); dropped (%llu)

Explanation: The number of routes in the named routing table has reached the configured limit. No further routes will be added to the table

Recommended Action: Reduce the number of routes in the table, or reconfigure the limit

URIB-4-ROUTELIMIT_NOT_ENFORCED Format: Number of routes (%llu) already exceeds newly configured limit (%lu); dropped (%llu)

Explanation: The number of routes in the named routing table is already more than the newly configured limit. No further routes will be added to the table, but the new limit has not been enforced.

Recommended Action: To enforce the new limit, clear the table, or transistion the table though the administrative shutdown state. Then reduce the number of routes in the table, or reconfigure the limit

URIB-4-ROUTELIMIT_WARNING Format: Number of routes (%llu) exceeds warning limit (%lu)

Explanation: The number of routes in the named routing table has reached the configured warning limit.

Recommended Action: Reduce the number of routes in the table, or reconfigure the limit

URIB-3-RNH_REFCOUNT Format: Client \%s\" deleting RNH %s/%u with refcount %u"

Explanation: A client tried to delete a Recursive Next-hop while that RNH was still in use.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-4-ZERO_NEXTHOP Format: Client \%s\" added 0.0.0.0 next hop and interface %s is not point-to-point"

Explanation: The client protocol added a 0.0.0.0 next-hop address on a non point-to-point interface

Recommended Action: No user action is required.

URIB-4-RTDEL_ERROR Format: Could not find prefix %s/%d, client \%s\"'s delete request"

Explanation: Route delete request was received for a non-existing route.

Recommended Action: No user action is required.

URIB-3-UNEXPECTED_MESSAGE Format: %s %d. src SAP: %d dst SAP: %d

Explanation: An unexpected interprocess message was received.

Recommended Action: No user action is required.

URIB-4-UNEXPECTED_VALUE Format: Unexpected value for %s

Explanation: An unexpected value was encountered for the logged event.

Recommended Action: No user action is required.

URIB-4-INVALID_PIB Format: %s %s

Explanation: A bad protocol information block was encountered in the given situation.

Recommended Action: No user action is required.

URIB-4-NH_RESOLV_LUKUP Format: Could not find %s/%d while processing %s (%d) resolve buffer

Explanation: Unresolved nexthop not cleaned up properly.

Recommended Action: No action is required.

URIB-4-UFDM_ACKNOT_FOUND Format: Could not find UFDM buffer with ptr 0x%08x

Explanation: Ack received for a UFDM buffer that URIB does not know about.

Recommended Action: No user action is required.

URIB-5-GENERAL_FAILURE Format: Failed to %s

Explanation: The logged action failed, causing an unrecoverable error.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-5-BOGUS_RNH Format: \%s\" tried to add %s/%d with RNH %s/%d"

Explanation: A bogus update with unexpected RNH was received from the client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-5-BOGUS_PREFIX Format: \%s\" tried to add %s/%d"

Explanation: A bogus prefix was received from the client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-5-BOGUS_MASK Format: Client \%s\" tried to add %s/%d"

Explanation: A bogus mask was received from the client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-5-BOGUS_INTF Format: Client \%s\" tried to add %s/%d via %s with invalid iod %d"

Explanation: A bad interface was received in a path add from the client.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-5-PATH_DELETE Format: ERRMSG_LIMIT_DEF

Explanation: URIB could not find the path that a client tried to delete.

Recommended Action: No user action is required.

URIB-5-RPATH_DELETE Format: ERRMSG_LIMIT_DEF

Explanation: URIB could not find the recursive path that a client tried to delete.

Recommended Action: No user action is required.

URIB-5-API_INIT_SEM_CLEAR Format: Cleared the API semaphore from %d

Explanation: The API semaphore was in an unexpected state, and was restored to a correct value.

Recommended Action: No user action is required.

URIB-5-RES_MGR_CHANGE Format: Changed u4route-mem from (%d, %d) to (%d, %d)

Explanation: The requested limit-resource command was adapted to fit the limits in this version.

Recommended Action: No user action is required.

URIB-6-NH_DELETED_NIB_INFO Format: Found hidden rnh %s/%d for client \%s\" in deleted NIB"

Explanation: URIB found a hidden next-hop for a client while the client was deregistering for a table.

Recommended Action: No user action is required.

URIB-6-UFDM_MGMT Format: Route %s/%d in VRF management not sent to ufdm

Explanation: URIB tried to give a route in the management VRF to UFDM

Recommended Action: No user action is required.

URIB-6-GENERAL_INFO Format: %s

Explanation: Informational message only.

Recommended Action: No user action is required.

URIB-6-TRACE_OVERFLOW Format: Trace buffer %s overflowed

Explanation: The given event trace overflowed. This is normal behaviour.

Recommended Action: No user action is required.

URIB-6-ROUTELIMIT_RECOVERED Format: Number of routes (%llu) is below the configured limit (%lu)

Explanation: The number of routes in the named routing table has fallen below the configured limit. The routing table has recovered

Recommended Action: No user action is required.

URIB-6-ROUTELIMIT_REINSTALL Format: Routing table was reinstalled

Explanation: The routing table was automatically reloaded to allow the new routing limit or because the reinstall threshold was crossed.

Recommended Action: No user action is required.

URIB-6-ROUTELIMIT_OVERFLOWED Format: Routing table statistic \%s\" overflowed 32 bits"

Explanation: The routing table statistic is returned in a MIB which only supports 32 bit values. The statistic just past the maximum value for 32 bits.

Recommended Action: No user action is required.

URIB-3-ROUTECOUNT_UNDERFLOW Format: Routing table statistic current tried to underflow deleting %s/%d

Explanation: The system tried to decrement the current number of routes in the table, but the statistic was already zero.

Recommended Action: Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

URIB-3-MTS_BIND Format: "mts_bind failed for %s: %s"

Explanation: URIB was unable to bind to an MTS queue SAP, causing an unrecoverable error.

Recommended Action: Use 'reload' CLI command to reload the system. Be aware that this affects all VDCs on the system.

URIB-3-MTS_OPTIONS Format: MTS option set failed for opcode %s: %s (%d)

Explanation: URIB was unable to set options for an MTS opcode

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-CMI_MTSSEND_FAILURE Format: mts_send failure for client %s: %s

Explanation: URIB was unable to send MTS message to a particular client

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-CMI_PAYLOAD_CONV_ERR Format: CMI payload conversion error failure from %s order to %s order

Explanation: The cmi payload conversion did not occur successfully.

Recommended Action: No user action is required.

URIB-3-MTS_UBIND Format: mts_unbind failed for %s: %s

Explanation: URIB was unable to unbind from an MTS queue SAP, causing an unrecoverable error.

Recommended Action: Use the 'system switchover' CLI command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command.

URIB-3-MTS_UNK_OPC Format: Received unknown MTS message on %s queue with opcode %d, dropping it. src SAP: %d dst SAP: %d

Explanation: URIB recieved an unknown message. The message is dropped

Recommended Action: No user action is required.

URIB-3-MTS_RECV Format: Error returned from mts_recv(%s), errno: %s

Explanation: An MTS API returned an error while URIB was receiving on an MTS queue.

Recommended Action: No user action is required.

URIB-3-MTS_DROP Format: Error returned from mts_drop(), error: %s

Explanation: An MTS API returned an error when URIB tried to drop a message.

Recommended Action: No user action is required.

URIB-3-MTS_SHORT_MSG_ERROR Format: Received short (%d \

Explanation: URIB recieved an unknown message. The message is dropped

Recommended Action: No user action is required.

URIB-3-MTS_NO_PAYLOAD_ERROR Format: Received MTS message with no payload on %s queue with opcode %d, dropping it. src SAP: %d dst SAP: %d

Explanation: URIB recieved an unknown message. The message is dropped

Recommended Action: No user action is required.

URIB-3-MTS_SIZE_ERROR Format: %s: incorrect %s message size from client %s: %d (should be %d)

Explanation: The size of a URIB message is incorrect for the type of message. The message is dropped.

Recommended Action: No user action is required.

URIB-3-MTS_NO_CLIENT_SAP Format: %s: client \%s\" has not provided a SAP for ack"

Explanation: A client registered with URIB, but did not provide a SAP for URIB to send reply messages to. This caused an unrecoverable error.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-MTS_REGISTER Format: "mts_register failed for urib: %s"

Explanation: URIB was unable to register client for URIB notifications, causing an unrecoverable error.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

URIB-3-MTS_DEREGISTER Format: "mts_deregister failed for urib: %s"

Explanation: URIB was unable to deregister client from URIB notifications, causing an unrecoverable error.

Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.

VLAN_MGR-3-ERROR_MSG Format: %s

Explanation: VLAN manager error

Recommended Action: No action is required.

VLAN_MGR-4-WARN_MSG Format: %s

Explanation: VLAN manager warning

Recommended Action: No action is required.

VLAN_MGR-6-INFO_MSG Format: %s

Explanation: VLAN manager info

Recommended Action: No action is required.

VLAN_MGR-5-NOTIF_MSG Format: %s

Explanation: VLAN Manager Notification Message

Recommended Action: No action is required.

VLAN_MGR-2-CRITICAL_MSG Format: %s

Explanation: VLAN Manager Critical Message

Recommended Action: No action is required.

VLAN_MGR-6-VLAN_OPER_STATUS_CHG Format: VLAN %d, status changed to %s

Explanation: VLAN operational state change

Recommended Action: No action is required.

VLAN_MGR-6-VLAN_CREATED Format: VLAN %d, created

Explanation: VLAN created

Recommended Action: No action is required.

VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART Format: VLAN Manager stateless restart

Explanation: VLAN Manager stateless restart

Recommended Action: No action is required.

VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART Format: VLAN Manager statefull restart

Explanation: VLAN Manager statefull restart

Recommended Action: No action is required.

VLAN_MGR-5-RESERVED_VLAN_RANGE_CHANGED Format: New Reserved VLAN Range Configured From VLAN %d to VLAN %d

Explanation: VLAN Manager Reserved VLAN Reconfiguration Message

Recommended Action: No action is required.

VNTAG_MGR-5-VNTAG_MGR_GENERIC_SYSLOG Format: %s

Explanation: VNTag Manager Generic Syslog

Recommended Action: No action is required.

VNTAG_MGR-5-VNTAG_MGR_ENABLED Format: VNTag Manager Enabled

Explanation: VNTag Manager Service Enabled

Recommended Action: No action is required.

VNTAG_MGR-5-VNTAG_MGR_DISABLED Format: VNTag Manager Disabled

Explanation: VNTag Manager Service Disabled

Recommended Action: No action is required.

VNTAG_MGR-5-VNTAG_SEQ_ERROR Format: %s

Explanation: Some step in an event sequence has failed

Recommended Action: No action is required.

VNTAG_MGR-2-VNTAG_SEQ_TIMEOUT Format: %s

Explanation: Event sequence timeout

Recommended Action: No action is required.

VNTAG_MGR-2-VNTAG_DVIF_LIMIT_REACHED Format: %s

Explanation: Event DVIF Limit of 4k Reached

Recommended Action: No action is required.

SVI-5-UPDOWN Format: Line Protocol on Interface %s, changed state to %s

Explanation: Line protocol status changed for an interface

Recommended Action: No action is required.

SVI-5-IF_DOWN_ADMIN_DOWN Format: Interface %s is down(Administratively Down)

Explanation: Interface has been configured to be administratively down

Recommended Action: No action is required.

SVI-5-IF_DOWN_ERROR_DISABLED Format: Interface %s is down. Reason %d

Explanation: The interface encountered an error while configuring it

Recommended Action: No action is required.

SVI-5-IF_DOWN_INACTIVE Format: Interface %s is down (Inactive)

Explanation: Interface VLAN has been suspended or deleted

Recommended Action: No action is required.

SVI-5-SVI_INIT Format: SVI intialization failed with error 0x%x

Explanation: SVI initialziation error

Recommended Action: No action is required.

SVI-5-SVI_SDB_UPDATE_FAILED Format: sdb update failed with ret_val %d

Explanation: SDB updated failed for SVI

Recommended Action: No action is required.

SVI-5-SVI_MTS_SEND_FAILURE Format: MTS send failure for opcode %d, error 0x%x

Explanation: SVI encountered an error in with MTS message

Recommended Action: No action is required.

SVI-5-SVI_MTS_TIME_OUT Format: MTS send timed out

Explanation: SVI did not recieve response for mts message

Recommended Action: No action is required.

SVI-5-SVI_RSRVD_VLAN_FAILED Format: Failed to get list of reserved vlans 0x%x

Explanation: SVI failed to get the list reserved vlans

Recommended Action: No action is required.

SVI-4-SVI_VLAN_DOES_NOT_EXIST Format: Vlan %d does not exist

Explanation: Vlan not created before assignment

Recommended Action:

SVI-5-SVI_IOD_RELEASE_ERROR_RESPONSE Format: IM failed to release SVI IOD error 0x%x

Explanation: IM failed to release SVI IOD

Recommended Action: No action is required.

SVI-4-SVI_IF_CONFIG_DELETED_NOTIF_DELAYED_DROPPED Format: Interface VLAN Delete Notification Not Processed on Time by SAP %d (%s)

Explanation: This SAP took long time in processing Interface VLAN delete notification and caused timeout

Recommended Action: No action is required.

SVI-4-SVI_IF_CONFIG_REMOVED_NOTIF_DELAYED_DROPPED Format: Interface VLAN Remove Notification Not Processed on Time by SAP %d (%s)

Explanation: This SAP took long time in processing Interface VLAN remove notification and caused timeout

Recommended Action: No action is required.