ACLLOG Messages
ACLLOG-5-ACLLOG_PKTLOG Format: %s
Explanation: New Acllog Packet Log: [chars]
Recommended Action: No action is required.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter lists the system messages generated by the underlying NX-OS operating system of the ACI-mode switches.
Explanation: New Acllog Packet Log: [chars]
Recommended Action: No action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
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.
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.
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.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
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.
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.
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.
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.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
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.
Explanation: Due to this failure, packet forwarding will continue to use the existing ARP adjacency entry values.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: There may be a connected router sending packets with a bogus IP address.
Recommended Action: Check all routers on the interface for misconfiguration.
Explanation: There may be a connected router sending packets with a bogus MAC address.
Recommended Action: Check all routers on the interface for misconfiguration.
Explanation: There may be a connected router sending packets with local MAC address.
Recommended Action: Check all routers on the interface for misconfiguration.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
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.
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.
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.
Explanation: PM's message queue may be temporarily full.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but recoverable error has occurred.
Recommended Action: No user action is required.
Explanation: ARP process failed to set IM extension.
Recommended Action: No user action is required.
Explanation: The indicated BGP process has started.
Recommended Action: No user action is required.
Explanation: A BGP session has just been established. Or a session has just been shutdown.
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
Explanation: The indicated BGP process has been deconfigured.
Recommended Action: No user action is required.
Explanation: The indicated BGP process is being restarted.
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
Explanation: BGP protocol was administratively shutdown.
Recommended Action: No user action is required.
Explanation: RD deconfigured from VRF.
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
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.
Explanation: Session can be brought up due to maximum-peer limit
Recommended Action: No user action is required.
Explanation: The peer has sent AS4_PATH with confed based path segments which would be discarded.
Recommended Action: No user action is required.
Explanation: The peer has sent AS4_PATH with zero path segment length which would be discarded.
Recommended Action: No user action is required.
Explanation: The peer has sent AS4_PATH with invalid path segment type which would be discarded.
Recommended Action: No user action is required.
Explanation: The peer has sent AS4_AGGREGATOR with invalid attr length which would be discarded.
Recommended Action: No user action is required.
Explanation:
Recommended Action: No user action is required.
Explanation: BGP received an IF notification from IM with zero or invalid iod
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: BGP has hit the limit of the number of peers that can. be configured.
Explanation: ACTION_KEEP_RUNNING
Recommended Action:
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: BGP was not able to create an entry for an outbound policy.
Explanation: ACTION_SW_RESTART_COMP
Recommended Action:
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.
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.
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.
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.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
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.
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.
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.
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.
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.
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.
Explanation: An unexpected but handleable event has occured.
Recommended Action: No user action is required.
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.
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.
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.
Explanation: An unexpected but handleable event has occured.
Recommended Action: No user action is required.
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.
Explanation: An unexpected but handleable event has occured.
Recommended Action: No user action is required.
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.
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.
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.
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.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
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.
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.
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.
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.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
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.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: An unexpected fatal error has occured.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected fatal error has occured.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected fatal error has occured.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occured.
Recommended Action: No user action is required.
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.
Explanation: The system may be low on memory.ORY
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
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.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
Explanation: An unrecoverable error has occured during BGP initialization.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
Explanation: An unexpected but handleable event has occured.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: BGP Update message reached the maximum limit
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
Explanation: The router is unable to do soft refresh for the indicated peer.
Recommended Action: If necessary, reset the connection with the peer.
Explanation: SNMP message does not have memory to store data.
Recommended Action: No user action is required.
Explanation: Sysmgr rejected BGP's request to shut down.
Recommended Action: No user action is required.
Explanation: MIB registration failed during startup.
Recommended Action: No user action is required.
Explanation: MIB deregistration failed during shutdown.
Recommended Action: No user action is required.
Explanation: FM get feature status failed
Recommended Action: No user action is required.
Explanation: URIB API had failed
Recommended Action: No user action is required.
Explanation: confcheck API has failed
Recommended Action: No user action is required.
Explanation: Objstore API has failed
Recommended Action: No user action is required.
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.
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.
Explanation: BIOS CHIP NOT SUPPORTED
Recommended Action: No action is required.
Explanation: Boot from Alternate
Recommended Action: No action is required.
Explanation: Boot from Primary
Recommended Action: No action is required.
Explanation: Boot from Alternate
Recommended Action: No action is required.
Explanation: Boot from Primary
Recommended Action: No action is required.
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.
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.
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.
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.
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.
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.
Explanation: CDP Daemon Initialization failed. [chars] explains the reason for the failure.
Recommended Action: No action is required.
Explanation: CDP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action: No action is required.
Explanation: CDP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action: No action is required.
Explanation: CDP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.
Recommended Action: No action is required.
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.
Explanation: Failed to receive packet. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Failed to send packet. [dec] identifies the interface [char] identifies the reason.
Recommended Action: No action is required.
Explanation: CDP Daemon was created successfully and is up and running. This is an informational message.
Recommended Action: No action is required.
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.
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.
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.
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.
Explanation: CDP Daemon is shutting down gracefully. This is an informational message.
Recommended Action: No action is required.
Explanation: CDP is enabled on the device.
Recommended Action: No action is required.
Explanation: CDP is disabled on the device.
Recommended Action: No action is required.
Explanation: Discovered a neighbor device. This is an informational message.
Recommended Action: No action is required.
Explanation: Deleted a neighbor device. This is an informational message.
Recommended Action: No action is required.
Explanation: duplex mismatch discovered from the received cdp packet This is a warning message.
Recommended Action: No action is required.
Explanation: Native VLAN mismatch discovered This is a warning message.
Recommended Action: No action is required.
Explanation: Internal error is encountered
Recommended Action: No action is required.
Explanation: Failed to register istack. [char] identifies the reason.
Recommended Action: No action is required.
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.
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.
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.
Explanation: SENSOR log message
Recommended Action: No action is required.
Explanation: Device Test process could not allocate memory
Recommended Action: No action is required.
Explanation: Device Test process could not create threads
Recommended Action: No action is required.
Recommended Action: No action is required.
Recommended Action: No action is required.
Recommended Action: No action is required.
Recommended Action: No action is required.
Recommended Action: No action is required.
Explanation: Test on this particular LineCard completed successfully
Recommended Action: No action is required.
Explanation: Test on this particular LineCard failed
Recommended Action: No action is required.
Explanation: A test has failed more than configured allowed limit
Recommended Action: No action is required.
Recommended Action: No action is required.
Explanation: Online diagnostics ASICRegisterCheck test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics USB test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics NVRAM test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics RealTimeClock test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics PrimaryBootROM test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics SpineControlBus test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics SystemMgmtBus test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics SystemMgmtBus test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics Status bus test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics StandbyFabricLoopback test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics ManagementPort test is skipped
Recommended Action: No action is required.
Explanation:
Recommended Action:
Explanation: Online diagnostics EOBC test has failed
Recommended Action: No action is required.
Explanation: Online diagnostics OBFL test has failed
Recommended Action: No action is required.
Explanation: Bootup diagnostics test on EPC/EOBC switch failed
Recommended Action: No action is required.
Explanation: DHCP Daemon Initialization failed. [chars] explains the reason for the failure.
Recommended Action: No action is required.
Explanation: Could not register par tree. [chars] explains the reason for the failure.
Recommended Action: No action is required.
Explanation: DHCP snoop process did an abnormal exit
Recommended Action: No action is required.
Explanation: DHCP client Discover phase started
Recommended Action: No action is required.
Explanation: DHCP client discover phase started list of interfaces
Recommended Action: No action is required.
Explanation: DHCP client request phase started list of interfaces
Recommended Action: No action is required.
Explanation: DHCP client starts from Request phase directly
Recommended Action: No action is required.
Explanation: DHCP client failed
Recommended Action: No action is required.
Explanation: DHCP client info
Recommended Action: No action is required.
Explanation: Received DHCP NAK
Recommended Action: No action is required.
Explanation: DHCP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.
Recommended Action: No action is required.
Explanation: An attempt to open a socket for receiving DHCP packets failed. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Failed to bind to socket. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Failed to receive packet. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Dropping the packet. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Failed to send packet. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Validation errors DHCP packet receieved on the interface [chars] vlan [%d]. Reason:[chars]
Recommended Action: No action is required.
Explanation: DHCP Daemon was created successfully and is up and running. This is an informational message.
Recommended Action: No action is required.
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.
Explanation: DHCP Daemon is shutting down gracefully. This is an informational message.
Recommended Action: No action is required.
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.
Explanation: Gracefully forwarding DHCP packet. reason [chars]
Recommended Action: No action is required.
Explanation: DHCP Snoop process has hit an assert condition at file [chars] line number [dec]
Recommended Action: No action is required.
Explanation: DiagClient process could not allocate memory
Recommended Action: No action is required.
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
Explanation: The specified test has reported SUCCESS in this Iteration
Recommended Action: No action is required.
Explanation: The specified test has reported FAILURE in this Iteration
Recommended Action: No action is required.
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.
Explanation: Per Port Test has failed on the above all ports
Recommended Action: No action is required.
Explanation: MTS send reports failure
Recommended Action: No action is required.
Explanation: Write operation on PSS store failed
Recommended Action: No action is required.
Explanation: Read operation from PSS store failed
Recommended Action: No action is required.
Explanation: Informational Syslog
Recommended Action: No action is required.
Explanation: Informational Syslog
Recommended Action: No action is required.
Explanation: Informational Syslog
Recommended Action: No action is required.
Explanation: Informational Syslog
Recommended Action: No action is required.
Explanation: Memory allocation in a call to malloc/calloc has failed
Recommended Action: No action is required.
Explanation: Current Diagnostic BootUp Level being configure or changed
Recommended Action: No action is required.
Explanation: MTS send reports failure
Recommended Action: No action is required.
Explanation: DIAG_PORT_LB Service nabled
Recommended Action: No action is required.
Explanation: DIAG_PORT_LB Service Disabled
Recommended Action: No action is required.
Explanation: Port Loopback test process could not allocate memory
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to convert port ifindex \ port index.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in Port Client API.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in MTS API.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in MTS API.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in stats infra lib API.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to send loopback packets.
Recommended Action: No action is required.
Explanation: Port Loopback test process timer handling failure.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to get test request info.
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to get the current test run information
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to add the port test result
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in if_index library API
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in process initialization
Recommended Action: No action is required.
Explanation: Port Loopback test process failed in socket operations
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to get Diagnostic LIF id
Recommended Action: No action is required.
Explanation: Port Loopback test process failed to get Diagnostic VLAN info
Recommended Action: No action is required.
Explanation: PortLoopback test failed on the module consecutively
Recommended Action: No action is required.
Explanation: Rewrite Engine Loopback test failed on the module consecutively
Recommended Action: No action is required.
Explanation: Failed to configure/restore the port to do/cleanup port loopback testing
Recommended Action: No action is required.
Explanation: Rewrite Engine Loopback test failed to get the Diag VQi from XBAR Mgr
Recommended Action: No action is required.
Explanation: Rewrite Engine Loopback test failed on the spine path consecutively
Recommended Action: No action is required.
Explanation: The port loopback test was not able to send the test results
Recommended Action: No action is required.
Explanation: The port loopback test was not able to get chassis info
Recommended Action: No action is required.
Explanation: Forwarding path setup for port loopback tests failed
Recommended Action: No action is required.
Explanation: Failed to send the response for LC insertion to Module Manager.
Recommended Action: No action is required.
Explanation: Random Number genration failed in FIPS module
Recommended Action: No action is required.
Explanation: Snake test failed on the module consecutively
Recommended Action: No action is required.
Explanation: a port-channel is created
Recommended Action: No action is required.
Explanation: a port-channel is deleted
Recommended Action: No action is required.
Explanation: ports are added to a port-channel
Recommended Action: No action is required.
Explanation: ports are removed from a port-channel
Recommended Action: No action is required.
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.
Explanation: port comes up in a port-channel
Recommended Action: No action is required.
Explanation: port goes down in a port-channel
Recommended Action: No action is required.
Explanation: port is suspended in a port-channel
Recommended Action: No action is required.
Explanation: port goes to hot-standby in a port-channel
Recommended Action: No action is required.
Explanation: port-channel hot-standby member goes down
Recommended Action: No action is required.
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
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
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
Explanation: no enough memory
Recommended Action: No action is required.
Explanation: failed to send a message
Recommended Action: No action is required.
Explanation: the first operational port in a port-channel is changed
Recommended Action: No action is required.
Explanation: cannot find port-channel in its database, which indicates an inconsistency with an external component
Recommended Action: No action is required.
Explanation: warning of possible race condition
Recommended Action: No action is required.
Explanation: general error
Recommended Action: No action is required.
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
Explanation: port-channel member operating in individual mode goes down
Recommended Action: No action is required.
Explanation: Some component did not respond to a request in stipulated time.
Recommended Action: None
Explanation: Some component did not respond to a request in stipulated time.
Recommended Action: None
Explanation: Port-channel num active ports error
Recommended Action: None
Explanation: Port-channel hwcfg fail error
Recommended Action: None
Explanation: Port-channel port down in pc_up. No bundle member down
Recommended Action: None
Explanation: Some service(s) failed to add or remove ports to port-channel
Recommended Action: None
Explanation: Port-channel port del in pc_up. Shut resp recvd before bundle member down
Recommended Action: None
Explanation: port-channel deleted from running config
Recommended Action: may need to re-configure the port-channel and its members
Explanation: Interface is up in mode specified, if applicable
Recommended Action: No action is required.
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
Explanation: The module's hardware has failed
Recommended Action: Collect more information about failed module using command 'show module internal all module'
Explanation: Diag failed on the interface
Recommended Action: Collect more information about failed interface using command 'attach module' to connect to module
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.
Explanation: The software servicing the data path on the port has failed
Recommended Action: No action is required.
Explanation: The physical link has gone down
Recommended Action: Ensure that the cable is connected and the remote end is not shut down
Explanation: The interface has been placed into the offline state
Recommended Action: No action is required.
Explanation: The loop port has been put into non participating mode
Recommended Action: No action is required.
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
Explanation: The port VSAN has been suspended or deleted
Recommended Action: Assign a new active port VSAN to the interface
Explanation: Interface has been configured to be administratively down
Recommended Action: Perform 'no shutdown'
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
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
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
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
Explanation: Parent interface is down
Recommended Action: No action is required.
Explanation: Tunnel port source interface unbound
Recommended Action: No action is required.
Explanation: Interface removed
Recommended Action: No action is required.
Explanation: The FCOT has been removed
Recommended Action: Insert an FCOT
Explanation: Fcot inserted is not a supported one
Recommended Action: Please contact customer support for a list of authorized transceiver vendors
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
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
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
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
Explanation: Remote end domain manager not responding
Recommended Action: No action is required.
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
Explanation: Upgrade of the linecard software is in progress
Recommended Action: No action is required.
Explanation: This is a PortChannel interface and all its members are operationally down
Recommended Action: Enable at least one of the PortChannel's members
Explanation: Interface is down because the module was removed
Recommended Action: No action is required.
Explanation: Operational duplex mode has changed when link came up
Recommended Action: No action is required.
Explanation: Operational speed has changed when link came up
Recommended Action: No action is required.
Explanation: Operational receive flow control has changed when link came up
Recommended Action: No action is required.
Explanation: Operational transmit flow control has changed when link came up
Recommended Action: No action is required.
Explanation: Interface [chars] is trunking, VLANs [chars] are up
Recommended Action: No action is required.
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
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
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
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
Explanation: FCIP interface temporarily down due to reconfiguration
Recommended Action: No action is required.
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
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
Explanation: The vrf for which this interface is a member is removed
Recommended Action: No action is required.
Explanation: Some component did not respond to a request in stipulated time.
Recommended Action: None
Explanation: Some component returned system error as a response to one of the port event sequence.
Recommended Action: None
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
Explanation: Traffic on specified port has returned to within configured storm-control threshold
Recommended Action: No action is required.
Explanation: Bandwidth of the interface (port channel) has changed and this change is updated
Recommended Action: No action is required.
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.
Explanation: The VLANs on an interface are being suspended due to some protocol action
Recommended Action: No action is required.
Explanation: The VLANs on an interface are being removed from the suspended state
Recommended Action: No action is required.
Explanation: There was an warning on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: There was an alarm on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: There was an error on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: The l2mp-mode on the port has changed
Recommended Action: No action is required.
Explanation: There was a critical failure in the component.
Recommended Action: Please follow instructions on the syslog.)msgdef_ddts_component(SRVNAME_ETH_PORT_MGR
Explanation: There was a critical failure in the component.
Recommended Action: Please collect system tech-support)msgdef_ddts_component(SRVNAME_ETH_PORT_MGR
Explanation: There was an warning on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: There was an alarm on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: There was an error on the transceiver module
Recommended Action: Please do show interface transceiver details to obtain more information
Explanation: Interface is admin up
Recommended Action: No action is required.
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
Explanation: Interface is being recovered from error disabled state
Recommended Action: No action is required.
Explanation: The physical link on the parent interface has gone down
Recommended Action: No action is required.
Explanation: IGMP process is shutting itself down.
Recommended Action: No user action is required.
Explanation: IGMP version mismatch, query still processed.
Recommended Action: No user action is required.
Explanation: IGMP process is shutting itself down due to the restart command.
Recommended Action: No user action is required.
Explanation: IGMP is restoring the routes it had added in previous instance.
Recommended Action: No user action is required.
Explanation: Exceeded 80% of the state-limit for interface
Recommended Action: No user action is required.
Explanation: Exceeded 80% of the reserve-limit for interface
Recommended Action: No user action is required.
Explanation: IGMP process incremented AS memory resource limit
Recommended Action: No user action is required.
Explanation: IGMP entries reached 84% of Threshold.
Recommended Action: No user action is required.
Explanation: Exceeded the state-limit for interface
Recommended Action: No user action is required.
Explanation: Exceeded the reserve-limit for interface
Recommended Action: No user action is required.
Explanation: GPrefix yiels too many Groups
Recommended Action: No user action is required.
Explanation: Group Range yields too many Groups
Recommended Action: No user action is required.
Explanation: IGMP process received unknown Interprocess message, dropped.
Recommended Action: No user action is required.
Explanation: IGMP process received unknown Interprocess message, dropped.
Recommended Action: No user action is required.
Explanation: IGMP process is out of free memory.
Recommended Action: Configure the network or router to decrease the number of routes.
Explanation: IGMP process could not execute the bitfield operation.
Recommended Action: Dump core, then reload the stack.
Explanation: IGMP process could not create the VRF context.
Recommended Action: Dump core, then reload the stack.
Explanation: IGMP process failed in invoking an API.
Recommended Action: No user action is required.
Explanation: IGMP process failed in getting mac addr
Recommended Action: No user action is required.
Explanation: IM API failed in MCEC IGMP Snoop.
Recommended Action: No user action is required.
Explanation: API failed in vPC IGMP snoop module.
Recommended Action: No user action is required.
Explanation: vPC related messages.
Recommended Action: No user action is required.
Explanation: vPC related messages.
Recommended Action: No user action is required.
Explanation: IGMP process failed to create a task thread.
Recommended Action: Dump core, then restart component.
Explanation: IGMP process failed to configure a timer event.
Recommended Action: Dump core, then restart component.
Explanation: IGMP process failed to process the packet, dropping it.
Recommended Action: No user action is required.
Explanation: IGMP process unable to shut itself down.
Recommended Action: Dump core, then restart component.
Explanation: Another IGMP process is already running, this process will shutdown.
Recommended Action: No user action is required.
Explanation: IGMP process could not set itself process priority, exiting.
Recommended Action: No user action is required.
Explanation: IGMP process could not set itself memory resource limit
Recommended Action: No user action is required.
Explanation: IGMP process could not retrieve memory resource limit
Recommended Action: No user action is required.
Explanation: An unrecoverable software error has occurred during igmp startup.
Recommended Action: No user action is required.
Explanation: An unrecoverable software error has occurred during igmp startup.
Recommended Action: No user action is required.
Explanation: IGMP process failed in an AVL-tree manipulation.
Recommended Action: No user action is required.
Explanation: IGMP failed to update the local snooping-db entry.
Recommended Action: No user action is required.
Explanation: IGMP failed to delete the local snooping-db entry.
Recommended Action: No user action is required.
Explanation: IGMP failed to create bitfield resource.
Recommended Action: Dump core, then restart component.
Explanation: IGMP failed to create vlan resource.
Recommended Action: No user action is required.
Explanation: IGMP process initialization failed.
Recommended Action: Dump core, then restart component.
Explanation: IGMP failed to delete the snooping-db vlan entry.
Recommended Action: No user action is required.
Explanation: IGMP failed to delete the snooping-db group entry.
Recommended Action: No user action is required.
Explanation: IGMP failed to delete the snooping-db encap entry.
Recommended Action: No user action is required.
Explanation: IGMP failed to delete the snooping-db source entry.
Recommended Action: No user action is required.
Explanation: IGMP snooping could not configure a parameter because of dependencies
Recommended Action: No user action is required.
Explanation: IGMP snooping could not process query from the fex port since it is not supported
Recommended Action: No user action is required.
Explanation: IGMP snooping could not process PIM hello from the fex port since it is not supported
Recommended Action: No user action is required.
Explanation: Exceeded the multicast group limit
Recommended Action: No user action is required.
Explanation: Multicast group count below threshold
Recommended Action: No user action is required.
Explanation: IGMP failed to create txlist resource.
Recommended Action: Dump core, then restart component.
Explanation: IGMP process failed to initialize mutex system resource.
Recommended Action: Dump core, then restart component.
Explanation: IGMP process failed to initialize conditional-variable resource.
Recommended Action: Dump core, then restart component.
Explanation: IGMP snoop failed to start the querier.
Recommended Action: No user action is required.
Explanation: IGMP-SNOOP called an API which returned an error.
Recommended Action:
Explanation: IGMP called an API which returned an error.
Recommended Action:
Explanation: IGMP called an API which returned an error.
Recommended Action:
Explanation: IGMP-SNOOP called an API which returned an error.
Recommended Action:
Explanation: IGMP-SNOOP has invalid number of iods.
Recommended Action:
Explanation: IGMP called a System Manager API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: IGMP received an invalid MTS message.
Recommended Action: Dump core, then restart component.
Explanation: Process failed to access the IGMP MTS-queue.
Recommended Action: No user action is required.
Explanation: Process failed in invoking IGMP API.
Recommended Action: No user action is required.
Explanation: Interface is not supported or not found
Recommended Action: No action is required.
Explanation: Internal error occurred
Recommended Action: No action is required.
Explanation: Demux function returned error
Recommended Action: No action is required.
Explanation: Management interface state changed.
Recommended Action: No action is required.
Explanation: Some component did not respond to a request in stipulated time.
Recommended Action: No action is required.
Explanation: Some component returned an error.
Recommended Action: No action is required.
Explanation: LC Offline was not relayed to some vdc, so applications may not behave correctly.
Recommended Action: No action is required.
Explanation: interface feature bind failed, so applications in that feature set may not behave correctly.
Recommended Action: No action is required.
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.
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.
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.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: Memory is not avialable for adding SNP entries
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
Explanation: SNP cache may get cleaned up during normal operation
Recommended Action: No user action is required.
Explanation: ISIS failed to update a local database entry.
Recommended Action: No user action is required.
Explanation: ISIS failed to delete an entry from a local database.
Recommended Action: No user action is required.
Explanation: ISIS process failed to allocate Slab memory.
Recommended Action: Configure the network or router to decrease the number of routes.
Explanation: ISIS process failed to update Switch-ID database.
Recommended Action: Configure the network or router to decrease the number of routes.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: ISIS called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: ISIS called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: ISIS called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: ISIS received an unexpected packet.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: Was unable to leave from the appropriate multicast group on an interface.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: An attempt to obtain RPM Keychain information failed.
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: A software error has occurred during HA. Stateful HA recovery will be disabled
Recommended Action: No user action is required.
Explanation: An unexpected but handleable event has occurred.
Recommended Action: No user action is required.
Explanation: Unable to remove BFD sessions.
Recommended Action: No user action is required.
Explanation: Unable to add conf check.
Recommended Action: No user action is required.
Explanation: Unable to retrieve OTV information
Recommended Action: No user action is required.
Explanation: Unsupported configuration
Recommended Action: No user action is required.
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.
Explanation: The indicated adjacency has changed state.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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'.
Explanation: IS-IS was unable to advertise the indicated adjacency.
Recommended Action: No user action is required.
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'.
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'.
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'.
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'.
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.
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.
Explanation: ISIS redistribution: Max limit
Recommended Action: No user action is required.
Explanation: ISIS redistribution: Threshold limit
Recommended Action: No user action is required.
Explanation: ISIS process start with specified reason
Recommended Action: No user action is required.
Explanation: ISIS procss stop with specified reason
Recommended Action: No user action is required.
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.
Explanation: IS-IS has been signaled to exit.
Recommended Action: No user action is required.
Explanation: IS-IS request to system manager for permission to shutdown was declined.
Recommended Action: No user action is required.
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.
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.
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.
Explanation: IS-IS encountered a problem where no callback function has been registered in the given mode
Recommended Action: No user action is required.
Explanation: L2MCAST has created its internal state stateless/stateful [chars].
Recommended Action: No action is required.
Explanation: Request to create VDC [dec] in L2MCAST was successful.
Recommended Action: No action is required.
Explanation: L2MCAST has successfully removed VDC [dec] from its databases.
Recommended Action: No action is required.
Explanation: L2MCAST has added VLAN [dec].
Recommended Action: No action is required.
Explanation: L2MCAST has successfully removed VLAN [dec] from VDC [dec].
Recommended Action: No action is required.
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.
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.
Explanation: Memory allocation failed. This is a critical failure
Explanation: SYSLOGDOC_NO_ACTION
Recommended Action:
Explanation: L2MCAST failed to initialize timer library. This is a fatal error.
Recommended Action: No action is required.
Explanation: L2MCAST failed to initialize CLI infrastructure\'s backend library. This is a fatal error.
Recommended Action: No action is required.
Explanation: Failed to program the OMF entries for BD. New BD's cannot have omf mode
Recommended Action: No action is required.
Explanation: LACP Service Enabled
Recommended Action: No action is required.
Explanation: LACP Service Disabled
Recommended Action: No action is required.
Explanation: general error
Recommended Action: No action is required.
Explanation: LACP system priority has been changed
Recommended Action: No action is required.
Explanation: LACP port priority has been changed
Recommended Action: No action is required.
Explanation: There was an error in sending LACP packet
Recommended Action: No action is required.
Explanation: There was an error in acquiring system mac from VDC Mgr
Recommended Action: No action is required.
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.
Explanation: LACP is not supported in half duplex mode. Suspend port
Recommended Action: No action is required.
Explanation: LACP suspend individual ports
Recommended Action: No action is required.
Explanation: LACP suspend ports due to min-link
Recommended Action: No action is required.
Explanation: LACP port-channel down as min-link requirement not met
Recommended Action: No action is required.
Explanation: LACP port-channel meets min-link requirement
Recommended Action: No action is required.
Explanation: Upgrade ready event is successful as all port channel members are in steady state.
Recommended Action: No action is required.
Explanation: Upgrade ready event failed because atleast one port channel member is in intermediate state.
Recommended Action: No action is required.
Explanation: Remote notify event was successful.
Recommended Action: No action is required.
Explanation: LACP is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action: No action is required.
Explanation: Internal error is encountered
Recommended Action: No action is required.
Explanation: Failed to register istack. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: Remote change detected on an interface
Recommended Action: No action is required.
Explanation: Multiple peers detected on an interface
Recommended Action: No action is required.
Explanation: Received an invalid LLDP on an interface
Recommended Action: No action is required.
Explanation: Internal error is encountered
Recommended Action: No action is required.
Explanation: LLDP Service Enabled
Recommended Action: No action is required.
Explanation: LLDP Service Disabled
Recommended Action: No action is required.
Explanation: A new peer is discovered
Recommended Action: No action is required.
Explanation: A peer is removed
Recommended Action: No action is required.
Explanation: LLDP is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action: No action is required.
Explanation: Failed to register istack. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: vPCM Initialization failed. due to [chars]
Recommended Action: No action is required.
Explanation: vPCM encountered an MTS error due to [chars]
Recommended Action: No action is required.
Explanation: vPCM encountered an internal error due to [chars]
Recommended Action: No action is required.
Explanation: vPCM got an internal info [chars]
Recommended Action: No action is required.
Explanation: Peer unreachable
Recommended Action: No action is required.
Explanation: vPC is configured
Recommended Action: No action is required.
Explanation: vPC is configured
Recommended Action: No action is required.
Explanation: vPC configuration deleted
Recommended Action: No action is required.
Explanation: Peer vPC configuration deleted
Recommended Action: No action is required.
Explanation: vPC Peer-link bringup failed
Recommended Action: No action is required.
Explanation: vPC bringup failed
Recommended Action: No action is required.
Explanation: vPC Peer-link is up
Recommended Action: No action is required.
Explanation: MCEC is UP
Recommended Action: No action is required.
Explanation: Peer vPC is up
Recommended Action: No action is required.
Explanation: vPC Peer link is down
Recommended Action: No action is required.
Explanation: vPC is down (reason)
Recommended Action: No action is required.
Explanation: Peer vPC is down
Recommended Action: No action is required.
Explanation: Remote MCEC configured vlans Changed
Recommended Action: No action is required.
Explanation: vPC role status changed to (Primary/Secondary
Recommended Action: No action is required.
Explanation: vPC domain-id configured
Recommended Action: No action is required.
Explanation: role priority configured
Recommended Action: No action is required.
Explanation: system mac configured
Recommended Action: No action is required.
Explanation: system priority changed
Recommended Action: No action is required.
Explanation: global compat-check passed
Recommended Action: No action is required.
Explanation: global compat-check failed
Recommended Action: No action is required.
Explanation: vPC configuration is consistent
Recommended Action: No action is required.
Explanation: MCEC compat-check failed
Recommended Action: No action is required.
Explanation: peer link down suspend vPCs
Recommended Action: No action is required.
Explanation: vPC bringup failed
Recommended Action: No action is required.
Explanation: vPC restore timer start
Recommended Action: No action is required.
Explanation: vPC restore timer expired
Recommended Action: No action is required.
Explanation: vPC delay interface-vlan restore timer start
Recommended Action: No action is required.
Explanation: vPC delay interface-vlan restore timer expired
Recommended Action: No action is required.
Explanation: Initializing vpcs assuming peer dead
Recommended Action: No action is required.
Explanation: Bypassing consistency check for vpcs
Recommended Action: No action is required.
Explanation: Global Consistency check for vPC passed for new vlans
Recommended Action: No action is required.
Explanation: Global Consistency check for vPC failed for new vlans
Recommended Action: No action is required.
Explanation: Global Consistency check for vPC passed for all vlans
Recommended Action: No action is required.
Explanation: Global Consistency check for vPC failed for few vlans
Recommended Action: No action is required.
Explanation: graceful state change,reinit vPCs
Recommended Action: No action is required.
Explanation: Triggered when vpc DB and IM SDB are inconsistent
Recommended Action: No action is required.
Explanation: MCP MSTP region misconfiguration
Recommended Action: No action is required.
Explanation: MCP RSTP misconfiguration
Recommended Action: No action is required.
Explanation: MCP is out of dynamic memory. [chars] specifies the context where the failure occurred.
Recommended Action: No action is required.
Explanation: Internal error is encountered
Recommended Action: No action is required.
Explanation: Failed to register istack. [char] identifies the reason.
Recommended Action: No action is required.
Explanation: MFDM PD hit a internal error. show system internal mfdm errors for futher analysis.
Recommended Action: No action is required.
Explanation: Download of L2/L3 route databases timed out. Download triggered by VMM insert request.
Recommended Action: No action is required.
Explanation: PIXM returned duplicate DI.
Recommended Action: No action is required.
Explanation: MFDM PI/PD refcount out-of-sync
Recommended Action: No action is required.
Explanation: Usage for starting MRIB process.
Recommended Action: No user action is required.
Explanation: Invalid memory size specified for MRIB process.
Recommended Action: No user action is required.
Explanation: MRIB process is shutting itself down.
Recommended Action: No user action is required.
Explanation: MRIB process is shutting itself down.
Recommended Action: No user action is required.
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.
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.
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.
Explanation: MRIB process could not set itself process priority, exiting.
Recommended Action: No user action is required.
Explanation: SDB initialization failed
Recommended Action: No user action is required.
Explanation: Opcdoe registration failed
Recommended Action: No user action is required.
Explanation: MRIB process received unknown message from URIB, dropped.
Recommended Action: No user action is required.
Explanation: MRIB process received unknown Interprocess message, dropped.
Recommended Action: No user action is required.
Explanation: MRIB process received unknown Interprocess message, dropped.
Recommended Action: No user action is required.
Explanation: MRIB process received unknown Interprocess message from MFDM, dropped.
Recommended Action: No user action is required.
Explanation: MRIB process is out of free memory.
Recommended Action: Configure the network or router to decrease the number of routes.
Explanation: MRIB process could not execute the bitfield operation.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process cannot register the protocol as it has run out of PIB indices.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process cannot stale the routes for this procotol.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process failed to update route-table for this event.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process failed in inheriting OIFs for the (S,G) from (*,G).
Recommended Action: No user action is required.
Explanation: MRIB process unable to create the route entry in its route-table.
Recommended Action: No user action is required.
Explanation: MRIB process unable to create the route entry in its route-table.
Recommended Action: No user action is required.
Explanation: MRIB process unable to create the route entry in its route-table.
Recommended Action: No user action is required.
Explanation: MRIB process unable to delete a route-table entry.
Recommended Action: No user action is required.
Explanation: MRIB process unable to delete a route-table entry.
Recommended Action: No user action is required.
Explanation: MRIB process failed to access the message-queue.
Recommended Action: No user action is required.
Explanation: MRIB process failed to access the mts-queue.
Recommended Action: No user action is required.
Explanation: MRIB process failed to access the System shared memory resource.
Recommended Action: No user action is required.
Explanation: MRIB process failed in invoking an API.
Recommended Action: No user action is required.
Explanation: MRIB process failed in invoking an API.
Recommended Action: No user action is required.
Explanation: MRIB process received invalid group.
Recommended Action: No user action is required.
Explanation: Caller Failed to get MRIB Shared Memory read lock
Recommended Action: No user action is required.
Explanation: Caller Failed to get MRIB Shared Memory write lock
Recommended Action: No user action is required.
Explanation: MRIB process failed to initialize mutex system resource.
Recommended Action: Dump core, then restart component.
Explanation: MRIB process failed to initialize conditional-variable resource.
Recommended Action: Dump core, then restart component.
Explanation: MRIB process could not match the sequence number for FTM message, ignored.
Recommended Action: No user action is required.
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.
Explanation: MRIB process received unsupported message type from FTM, ignored.
Recommended Action: No user action is required.
Explanation: MRIB process failed to configure the multicast meter.
Recommended Action: No user action is required.
Explanation: Another MRIB process is already running, this process will shutdown.
Recommended Action: No user action is required.
Explanation: MRIB process failed to configure a timer event.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process failed to create a timer.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process failed to create a task thread.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB process failed to create a bitfield for mrib_ cibtype.
Recommended Action: Dump core, then reload the stack.
Explanation: MRIB called a PSS API which returned an error. The error reported should be examined for the cause.
Recommended Action: ERRMSG
Explanation: A severe error was encountered during ksink operations.
Recommended Action: No action is required.
Explanation: The requested limit-resource command was adapted to fit the limits in this version.
Recommended Action: No user action is required.
Explanation: The API semaphore was in an unexpected state, and was restored to a correct value.
Recommended Action: No user action is required.
Explanation: MRIB recieved an unknown message. The message is dropped
Recommended Action: No user action is required.
Explanation: MRIB recieved an unknown message. The message is dropped
Recommended Action: No user action is required.
Explanation: MRIB failed to create txlist resource.
Recommended Action: No user action is required.
Explanation: MRIB failed to find txlist resource.
Recommended Action: No user action is required.
Explanation: MRIB failed to create notification buffer for a client
Recommended Action: No user action is required.
Explanation: MRIB failed to update config check capability in the system
Recommended Action: No user action is required.
Explanation: MRIB called a System Manager API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: MRIB called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: MRIB called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: MRIB called a MTS API which returned an error.
Recommended Action: Dump core, then restart component.
Explanation: Failure in MRIB library to access mts-queue
Recommended Action: No user action is required.
Explanation: Process failed to access the System shared memory resource.
Recommended Action: No user action is required.
Explanation: Process failed in invoking an API.
Recommended Action: No user action is required.
Explanation: Dupilcate registration request to the MRIB process, ignored.
Recommended Action: No user action is required.
Explanation: Caller failed to get perform an operation on the MRIB semaphore
Recommended Action: No user action is required.
Explanation: MRIB semaphore was found to be invalid when performing a semaphore operation
Recommended Action: No user action is required.
Explanation: Buffer usage exceeded threshold
Recommended Action: No action is required.
Explanation: System wide upgrade has been initiated by the user.
Recommended Action: No action is required.
Explanation: This message indicates system wide upgrade has completed.
Recommended Action: No action is required.
Explanation: This message indicates that system wide upgrade has aborted.
Recommended Action: No action is required.
Explanation: This message indicates that system wide upgrade has been stopped by the user.
Recommended Action: No action is required.
Explanation: This message indicates that control plane was down for more than 80 seconds.
Recommended Action: No action is required.
Explanation: OSPF process is starting due to the specified reason.
Recommended Action: No user action is required.
Explanation: An OSPF neighborship has just been established. Or a neighborship has just been shutdown.
Recommended Action: No user action is required.
Explanation: An OSPF neighbor has just changed state.
Recommended Action: No user action is required.
Explanation: OSPF has been deconfigured or restarted.
Recommended Action: No user action is required.
Explanation: OSPF request to system mananger for permission to shutdown was turned down.
Recommended Action: No user action is required.
Explanation: OSPF process is shutting itself down due to the deconfiguration command.
Recommended Action: No user action is required.
Explanation: OSPF process is shutting itself down due to the restart command.
Recommended Action: No user action is required.
Explanation: OSPF process is shutting itself down due to unknown reason.
Recommended Action: No user action is required.
Explanation: Two routers are configured with the same router ID.
Recommended Action: Check all routers on the indicated interface for misconfigurations.
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.
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.
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.
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.
Explanation: The router has allocated a packet buffer that was too small.
Recommended Action: No user action is required.
Explanation: Internal Error.
Recommended Action: No user action is required.
Explanation: Error while parsing TLV.
Recommended Action: No user action is required.
Explanation: Error while loading or unloading the MIB.
Recommended Action: No user action is required.
Explanation: Error while registering or deregistering with SNMP.
Recommended Action: No user action is required.
Explanation: Error while registering or deregistering with SNMP SAP.
Recommended Action: No user action is required.
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.
Explanation: Restricting the number of interfaces per area to avoid problems during lsa generation.
Recommended Action: Reduce the number of interfaces per area.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: Reduced heap size will limit the LSDB size.
Recommended Action: No user action is required.
Explanation: An internal software error has occurred.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: An unexpected software interrupts was received.
Recommended Action: No user action is required.
Explanation: The router tried to send unknown OSPF packet.
Recommended Action: No user action is required.
Explanation: Thread cannot be wokenup at this time
Recommended Action: No user action is required.
Explanation: Did not expect the specified packet type on the given incoming message queue
Recommended Action: No user action is required.
Explanation: Function is not specified for the current address family
Recommended Action: No user action is required.
Explanation: Error related to multiple subrouters and contexts
Recommended Action: No action is required.
Explanation: Error related to interface context
Recommended Action: No action is required.
Explanation: OSPF called a MTS API which returned an error.
Recommended Action: No action is required.
Explanation: OSPF recieved an unknown MTS message. The message will be dropped
Recommended Action: No action is required.
Explanation: OSPF called a MTS API which returned an error.
Recommended Action: No action is required.
Explanation: OSPF called a MTS API which returned an error.
Recommended Action: No action is required.
Explanation: OSPF called an PSS API which returned an error.
Recommended Action: No action is required.
Explanation: OSPF called an TLV intf which returned an error.
Recommended Action: No action is required.
Explanation: OSPF called a MTS API which returned an error.
Recommended Action: No action is required.
Explanation: CMI returned an error
Recommended Action: No user action is required.
Explanation: CMI returned an error
Recommended Action: No user action is required.
Explanation: A OSPF packet not belonging to this interface was received
Recommended Action: No action is required.
Explanation: A OSPF packet with invalid length was received
Recommended Action: No action is required.
Explanation: A OSPF packet not belonging to this area was received
Recommended Action: No action is required.
Explanation: A OSPF packet with incorrect packet type was received
Recommended Action: No action is required.
Explanation: A OSPF packet with incorrect version number was received
Recommended Action: No action is required.
Explanation: A OSPF packet with our own source address was received
Recommended Action: No action is required.
Explanation: A OSPF packet packet with source address not on this network was received
Recommended Action: No action is required.
Explanation: A OSPF packet with invalid checksum was received
Recommended Action: No action is required.
Explanation: A OSPF packet with mismatched authentication type was received
Recommended Action: No action is required.
Explanation: A non-hello OSPF packet with no neighbor was received
Recommended Action: No action is required.
Explanation: A OSPFv3 packet with muticast source address was received
Recommended Action: No action is required.
Explanation: A OSPFv3 packet with muticast source address was received
Recommended Action: No action is required.
Explanation: Check if redistribution of large number of prefixes is desired and has not been configured by mistake
Recommended Action: No action is required.
Explanation: Check if redistribution of large number of prefixes is desired and has not been configured by mistake
Recommended Action: No action is required.
Explanation: An internal error
Recommended Action: No action is required.
Explanation: OSPF could not find an interface
Recommended Action: No action is required.
Explanation: OSPF sets the configuration to sends the LSAs with max-metric cost
Recommended Action: No action is required.
Explanation: OSPF resets the configuration to sends the LSAs with normal cost
Recommended Action: No action is required.
Explanation: PIXM has encountered a critical error
Recommended Action: Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
Explanation: PIXM has encountered a error
Recommended Action: Please collect PIXM tech support using 'show tech pixm-all' and 'show tech pixmc-all'
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'
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'
Explanation: The supervisor is comming up in wrong slot [decimal digit].
Recommended Action: No action is required.
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.
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.
Explanation: Power Supply is detected.
Recommended Action: No action is required.
Explanation: Power Supply is detected but shutdown.
Recommended Action: Please perform a 'show environment power' and 'show platform internal info' to collect more information.
Explanation: module in slot [decimal digit] changed status.
Recommended Action: No action is required.
Explanation: Power Supply is removed.
Recommended Action: No action is required.
Explanation: Power Supply is ok.
Recommended Action: No action is required.
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.
Explanation: Fan module is detected
Recommended Action: No action is required.
Explanation: Fan module changed status
Recommended Action: No action is required.
Explanation: Fan module is removed
Recommended Action: No action is required.
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.
Explanation: failed to load drivers.
Recommended Action: Image is possibly corrupt. Try to load a different image.
Recommended Action: None
Recommended Action: None
Recommended Action: None
Recommended Action: None
Recommended Action: None
Recommended Action: None
Recommended Action: None
Recommended Action: None
Explanation: Deep sleep mode initiated by the Connectivity Management Processor (CMP) for this supervisor
Recommended Action: No action is required.
Recommended Action: None
Recommended Action: None
Explanation: Platform Alert
Recommended Action: No action is required.
Explanation: Fex Fan module is detected
Recommended Action: No action is required.
Explanation: Fex Fan module is removed
Recommended Action: No action is required.
Explanation: Fex power supply is found
Recommended Action: No action is required.
Explanation: Fex power supply is removed
Recommended Action: No action is required.
Explanation: The module in slot [decimal digit] has been powered down.
Recommended Action: No action is required.
Explanation: The PPF generated notification
Recommended Action: No action is required.
Explanation: The PPF generated warning
Recommended Action: No action is required.
Explanation: The PPF generated error
Recommended Action: No action is required.
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.
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.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM tried to PSS sync a message exceeding the maximum allowed size
Recommended Action: No action is required.
Explanation: RPM process is shutting itself down due to the restart command.
Recommended Action: No user action is required.
Explanation: RPM received an unknown message. The message is dropped
Recommended Action: No user action is required.
Explanation: An MTS API returned an error while RPM was receiving on an MTS queue
Recommended Action: No user action is required.
Explanation: An MTS API returned an error while RPM was sending an MTS message
Recommended Action: No user action is required.
Explanation: An MTS API returned an error when RPM tried to drop a message
Recommended Action: No user action is required.
Explanation: Please remove the incompatible RPM/PBR config and restart ISSU.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
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.
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.
Explanation: An MTS API returned an error while RPM was sending an MTS message.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: RPM invoked an API which failed. This is an unexpected but manageable event.
Recommended Action: No user action is required.
Explanation: A route-map match command has been ignored.
Recommended Action: No user action is required.
Explanation: Unexpected result during RPM keychain API processing
Recommended Action: No user action is required.
Explanation: Fex [decimal-digit] changed port status
Recommended Action: No action is required.
Explanation: Fex [decimal-digit] changed port status
Recommended Action: No action is required.
Explanation: Fex pinning information changed
Recommended Action: No action is required.
Explanation: FEX Service Enabled
Recommended Action: No action is required.
Explanation: FEX Service Disabled
Recommended Action: No action is required.
Explanation: Disabling of FEX feature failed
Recommended Action: No action is required.
Explanation: FEX did not come online after sup ISSU
Recommended Action: No action is required.
Explanation: FEX has come ONLINE
Recommended Action: No action is required.
Explanation: FEX has gone OFFLINE
Recommended Action: No action is required.
Explanation: Fex on-line
Recommended Action: show inventory
Explanation: Fex off-line
Recommended Action: show inventory
Explanation: FEX has gone OFFLINE because of the specified reason.
Recommended Action: No action is required.
Explanation: COOP initialization failure
Recommended Action: No action is required.
Explanation: COOP fu initialization failure
Recommended Action: No action is required.
Explanation: COOP initialization information
Recommended Action: No action is required.
Explanation: COOP MTS initialization information
Recommended Action: No action is required.
Explanation: COOP MTS initialization failure
Recommended Action: No action is required.
Explanation: Tunnel Service Enabled
Recommended Action: No action is required.
Explanation: Tunnel Service Disabled
Recommended Action: No action is required.
Explanation: Tunnel Service info
Recommended Action: No action is required.
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
Explanation: Programming [chars] mtu [int]
Recommended Action: No action is required.
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
Explanation: Programming [chars] DF df.sel [int] df.val [int]
Recommended Action: No action is required.
Explanation: [chars] DF programming failed! status [int]
Recommended Action: capture \show tech-support tunnel \ to identify why df flag programing failed
Explanation: Interface [char] is [char] reason [char]
Recommended Action: No action is required.
Explanation: Interface [char] is created
Recommended Action: No action is required.
Explanation: Interface [char] is creation failed due to [int] [char]
Recommended Action: No action is required.
Explanation: Interface [char] is deleted
Recommended Action: No action is required.
Explanation: Interface [char] counters is cleared
Recommended Action: No action is required.
Explanation: session id [int] type [char] for [char] failed error [int] [char]
Recommended Action: No action is required.
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\
Explanation: Tunnel feature is not supported in F2 only VDC
Recommended Action: Disable the Tunnel feature by the CLI \no feature tunnel\
Explanation: UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action: No action is required.
Explanation: UFDM download timer expired. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action: No action is required.
Explanation: FIB returned route update error. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action: No action is required.
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.
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.
Explanation: URIB cannot add this client because the URIB client limit has already been reached.
Recommended Action: Kill component and don't restart it.
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.
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.
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.
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 \'
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.
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.
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.
Explanation: An severe error was enountered during Consistency Checker
Recommended Action: No action is required.
Explanation: Previous Consistency Check has not yet completed
Recommended Action: No action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: An RPM library function returned an error.
Recommended Action: No action is required.
Explanation: A SDWrap library function returned an error.
Recommended Action: No action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation: This message is for internal debugging only.
Recommended Action: No action is required.
Explanation: This message is for internal debugging only.
Recommended Action: No action is required.
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.
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.
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.
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.
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.
Explanation: URIB detected unknown eXtended route information while displaying a next-hop address.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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
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
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.
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.
Explanation: Route delete request was received for a non-existing route.
Recommended Action: No user action is required.
Explanation: An unexpected interprocess message was received.
Recommended Action: No user action is required.
Explanation: An unexpected value was encountered for the logged event.
Recommended Action: No user action is required.
Explanation: A bad protocol information block was encountered in the given situation.
Recommended Action: No user action is required.
Explanation: Unresolved nexthop not cleaned up properly.
Recommended Action: No action is required.
Explanation: Ack received for a UFDM buffer that URIB does not know about.
Recommended Action: No user action is required.
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.
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.
Explanation: A bogus prefix was received from the client.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
Explanation: A bogus mask was received from the client.
Recommended Action: Use the 'restart' CLI command to restart the feature and clear this issue.
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.
Explanation: URIB could not find the path that a client tried to delete.
Recommended Action: No user action is required.
Explanation: URIB could not find the recursive path that a client tried to delete.
Recommended Action: No user action is required.
Explanation: The API semaphore was in an unexpected state, and was restored to a correct value.
Recommended Action: No user action is required.
Explanation: The requested limit-resource command was adapted to fit the limits in this version.
Recommended Action: No user action is required.
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.
Explanation: URIB tried to give a route in the management VRF to UFDM
Recommended Action: No user action is required.
Explanation: Informational message only.
Recommended Action: No user action is required.
Explanation: The given event trace overflowed. This is normal behaviour.
Recommended Action: No user action is required.
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.
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.
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.
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.
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.
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.
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.
Explanation: The cmi payload conversion did not occur successfully.
Recommended Action: No user action is required.
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.
Explanation: URIB recieved an unknown message. The message is dropped
Recommended Action: No user action is required.
Explanation: An MTS API returned an error while URIB was receiving on an MTS queue.
Recommended Action: No user action is required.
Explanation: An MTS API returned an error when URIB tried to drop a message.
Recommended Action: No user action is required.
Explanation: URIB recieved an unknown message. The message is dropped
Recommended Action: No user action is required.
Explanation: URIB recieved an unknown message. The message is dropped
Recommended Action: No user action is required.
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.
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.
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.
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.
Explanation: VLAN manager error
Recommended Action: No action is required.
Explanation: VLAN manager warning
Recommended Action: No action is required.
Explanation: VLAN manager info
Recommended Action: No action is required.
Explanation: VLAN Manager Notification Message
Recommended Action: No action is required.
Explanation: VLAN Manager Critical Message
Recommended Action: No action is required.
Explanation: VLAN operational state change
Recommended Action: No action is required.
Explanation: VLAN created
Recommended Action: No action is required.
Explanation: VLAN Manager stateless restart
Recommended Action: No action is required.
Explanation: VLAN Manager statefull restart
Recommended Action: No action is required.
Explanation: VLAN Manager Reserved VLAN Reconfiguration Message
Recommended Action: No action is required.
Explanation: VNTag Manager Generic Syslog
Recommended Action: No action is required.
Explanation: VNTag Manager Service Enabled
Recommended Action: No action is required.
Explanation: VNTag Manager Service Disabled
Recommended Action: No action is required.
Explanation: Some step in an event sequence has failed
Recommended Action: No action is required.
Explanation: Event sequence timeout
Recommended Action: No action is required.
Explanation: Event DVIF Limit of 4k Reached
Recommended Action: No action is required.
Explanation: Line protocol status changed for an interface
Recommended Action: No action is required.
Explanation: Interface has been configured to be administratively down
Recommended Action: No action is required.
Explanation: The interface encountered an error while configuring it
Recommended Action: No action is required.
Explanation: Interface VLAN has been suspended or deleted
Recommended Action: No action is required.
Explanation: SVI initialziation error
Recommended Action: No action is required.
Explanation: SDB updated failed for SVI
Recommended Action: No action is required.
Explanation: SVI encountered an error in with MTS message
Recommended Action: No action is required.
Explanation: SVI did not recieve response for mts message
Recommended Action: No action is required.
Explanation: SVI failed to get the list reserved vlans
Recommended Action: No action is required.
Explanation: Vlan not created before assignment
Recommended Action:
Explanation: IM failed to release SVI IOD
Recommended Action: No action is required.
Explanation: This SAP took long time in processing Interface VLAN delete notification and caused timeout
Recommended Action: No action is required.
Explanation: This SAP took long time in processing Interface VLAN remove notification and caused timeout
Recommended Action: No action is required.